Date:	Mon, 2 Aug 1999 13:13:45 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Chris Verwey <cverwey AT iafrica DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: 'uname' weirdness & make binutils
In-Reply-To:	<37A45AA4.867716B@iafrica.com>
Message-ID:	<Pine.SUN.3.91.990802131239.4488H-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 1 Aug 1999, Chris Verwey wrote:

> D:\WORK>uname -a
> MS-DOS CHRIS DE 7 10 pc
> 
> This freaks out the configure script and I can get nothing done. After
> much pain and suffering, I managed to work out that my machine type
> should be i386-unknown-msdosdjgpp. I'm running this under a dos box in
> win95.
> 
> Does anybody know why my uname is behaving like this?

`uname' simply prints what function 5Eh of Int 21h returns.  The
string that this function returns is determined by the installed
network software and by your network setup in the Control Panel.  On
my Windows machine "uname -a" prints this:

   MS-DOS ELIZ 7 00 pc

I suggest to look in your network configuration and see what is the
name of the machine that it sets up.

If you want to investigate this further, download the library sources 
(v2/djlsr202.zip) and look at the source of the function gethostname().

> BTW: I had to manually link "alloca-norm.h" to "alloca-conf.h" in
> libiberty and comment the lines out of config.in because of the script
> couldn't do it for some reason.

You need to replace "ln -s" with "ln" at the beginning of the
configure script, in the line that begins with "symbolic_link=".  This
is a known problem, to be solved in the next release of Binutils.

- Raw text -