make '***Warning:'
- From: Michael Hall <mhall riverside org>
- To: GNOME-List <gnome-list gnome org>
- Subject: make '***Warning:'
- Date: Sun, 14 Mar 1999 13:38:09 -0800
I remember seeing some messages about this but don't recall and fix but
I get the following compiling 'libgtop-1.0.1':
/bin/sh ../../libtool --mode=link gcc -g -O2 -Wall -Wno-unused -o libgtop_com
mon.la -rpath /usr/local/GNOME/lib -version-info 1:0:0 xmalloc.lo error.lo gnusl
ib.lo fsusage.lo mountlist.lo -L/usr/X11R6/lib -lXau -L/usr/local/lib -lglib -lm
mkdir .libs
*** Warning: This library needs some functionality provided by -lXau.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have.
gcc -shared -Wl,-soname -Wl,libgtop_common.so.1 -o .libs/libgtop_common.so.1.0.0
xmalloc.lo error.lo gnuslib.lo fsusage.lo mountlist.lo -L/usr/X11R6/lib -L/usr/
local/lib -lglib -lm -lc
And I get this compiling 'gnumeric-0.16':
/bin/sh ../../libtool --mode=link gcc -g -O2 -Wall -Wno-unused -o libgnumguil
e.la -rpath /usr/local/GNOME/lib/gnumeric/plugins plugin.lo -L/usr/local/lib -l
guile -ldl -lreadline -ltermcap -lm -lm
mkdir .libs
*** Warning: This library needs some functionality provided by -ltermcap.
*** I have the capability to make that library automatically link in when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have.
gcc -shared -Wl,-soname -Wl,libgnumguile.so.0 -o .libs/libgnumguile.so.0.0.0 plu
gin.lo -L/usr/local/lib -lguile -ldl -lreadline -lm -lm -lc
The '-lXau' is obvious as I don't have a shared lib, just have 'libXau.a'
But I do have 'libtermcap.so' (link to 'libncurses.so'), does libtool not
like it being a link ?
What I have been doing is after it finishes compiling is to go back and
manually recompile the lib using the same command line except adding in the
'-lXau' or '-ltermcap' (like the line above the warning) it compiles fine
and then I do the 'make install' is this kosher to do ? Or is there a better
way to fix it in the libtool setup.
PS: Using egcs-1.1.1, glibc-2.1, autoconf-2.13, automake-1.4 and libtool-1.2e.
--
Good news for Win95 users: the CD's a great frisbee.
Mike Hall <mhall@riverside.org>, (MH993) - http://www.riverside.org
System Administrator (*nix, Perl, CGI hacker, certified OS/2 Specialist)
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]