Re: Fwd: (Help Me!) Errors while Compiling NX Src on FREEBSD machine (5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0:)

[Ralf Wildenhues]

For everybody I just added to Cc (and all readers of bug-libtool):

All of you have, at one time in history, reported a bug against libtool
on FREEBSD 5.2.1, concerning this error:

| checking if libtool supports shared libraries... yes
| 
| *** Warning: the command libtool uses to detect shared libraries,
| *** /usr/bin/file, produces output that libtool cannot recognize.
| *** The result is that libtool may fail to recognize shared libraries
| *** as such.  This will affect the creation of libtool libraries that
| *** depend on shared libraries, but programs linked with such libtool
| *** libraries will work regardless of this problem.  Nevertheless, you
| *** may want to report the problem to your system manager and/or to
| *** address@hidden

Now I have set out to kill this bug.  But I need help (as I have no
access to a system exposing it).  Excuses for not looking earlier
(I have not even been involved in Libtool development that long),
but I have asked for this repeatedly and never gotten any feedback.


Please show output of these commands, replace $CC with the compiler
used to expose the problem, and $LIBTOOL to a `libtool' script generated
by the package you were configuring at that time:

$ uname -r
$ /usr/bin/file `echo /usr/lib/libc.so.*`
$ grep deplibs_check_method= $LIBTOOL
$ echo __ELF__ | $CC -E - | grep __ELF__ > /dev/null
$ $LIBTOOL --version

If you are able to go the effort, please take a recent Libtool and show
if the problem persists with it.  Report all your findings to this list.

Thank you very much.


* Peter O'Gorman wrote on Wed, Mar 02, 2005 at 03:22:41PM CET:
> Ralf Wildenhues wrote:
> >
> >Do *you* get the error message listed in the original post?
> >If not, your system doesn't apply for my wish.  :)
> 
> I do not, sorry.
> 
> As far as I know freebsd > 3, certainly > 4 uses ELF, so there shouldn't be 
> any problems like the one quoted, especially not on a 5.2 machine.

And still I remember seeing this kind of bug report before.
So, in an attempt to solve it, a cry for help.  :)

My guess is that all packages exposing this bug use a very old Libtool,
but I would like this confirmed.

Regards,
Ralf