uname(1) on UnixWare (Solaris)

Francois Gouget fgouget at free.fr
Tue Jun 5 02:18:00 CDT 2001

On Tue, 5 Jun 2001, Bang Jun-Young wrote:

> On Mon, Jun 04, 2001 at 08:06:44PM -0700, Alexandre Julliard wrote:
> > Why do you need that?  Using uname(1) in a configure script is almost
> > certainly the wrong thing to do.
> There are some reasons for that:
> 1. Configure message is wrong:
>    checking whether we can build a Linux dll... yes
>    I see this even on FreeBSD and NetBSD. :( It's not a Linux dll, 
>    but an FreeBSD/NetBSD dll.

   Maybe this message should be changed, yes. But I don't think you
should put a `uname` there.

> 2. Linux/FreeBSD/NetBSD running on x86 are all based on ELF, so
>    replacing 'Linux' with 'ELF' would be more appropriate. The 
>    problem is, however, they have slightly different linker flags 
>    for building shared libraries. For example, giving -Bsymbolic
>    when compiling sources on NetBSD causes an error even though 
>    compiler/linker toolchain is almost same as one used in Linux.
>    It's due to different startup code, but unfortunately, I
>    have no idea how to detect it during configure process without
>    help from uname. 

   If it gives an error then it should be easy to detect with autoconf:
Just use the flags that cause the command to fail. If it fails then we
must use other flags. Otherwise these are the ones to use.
   What kind of error is it btw?

> 3. IMHO, my modification is more readable than existing code. 

   Why don't you show us the new code, or an outline thereof?

Francois Gouget         fgouget at free.fr        http://fgouget.free.fr/
            "Lotto: A tax on people who are bad at math." -- unknown
          "Windows: Microsoft's tax on computer illiterates." -- WE7U

More information about the wine-devel mailing list