Date: Mon, 22 Mar 1999 10:10:13 -0600 From: "Tony" <tbrock@mail.phoenix.net> To: <freebsd-questions@FreeBSD.ORG> Subject: ldconfig, libs, elf, aout, ports, headaches, pains and sorrow Message-ID: <001501be747e$783da600$f548c58d@ho30032880.fdnet.com>
next in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
Greetings,
I'm having serious difficulties getting certain items to compile.
I'm using FreeBSD/3.1-RELEASE with the upgrade package installed.
Everything is pretty much standard issue release and portwise there. My goal was to install kde or gnome 1.0.1 so I began installing all of the required programs such as db, docbook, xpm, png, tiff, jpeg, gif, imlib, etc.
I like to stay current with source releases but if versions aren't too far off between a port and any source I can find I'll stick with the port. (Our proxy's methods are so obscure CVSuping seems a pipe dream). KDE comes with support libraries that work just great for KDE but aren't necessarily current.
The biggest problem I'm having is libraries. Specifically ones like -jpeg, -tiff, -gif etc. These libraries are ON my system. I've ported them, packaged them, compiled them, uninstalled them and repeated the above ad-nauseum. I've forced --with-extra-libs in configure scripts, I've rebuilt the hints files over and over. The libraries are THERE but these configure scripts don't see them! 8( ldconfig lists them as elf available libraries etc!
Let me see if I can toss some questions about to help clarify what might be happening.
1. How would I end up building aout libraries on an elf system with the OBJECT stuff set to elf?
2. Why would libraries not be seen by configure scripts even though they are quite obviously installed.
3. Are configure scripts (kdelibs-1.1) hard coded to REQUIRE older libraries?
4. Shouldn't I be able to force the building of shared libraries without fear that everything won't explode?
5. If a library is listed in ldconfig -r should it not be completely accessable by all of the tools used by configure scripts to determine what is available? If I have to specify where libraries are all the time what good is ldconfig??
6. Are these graphics libraries not backwards compatible? (e.g. would kdelibs-1.1 neglect a newer graphics library in preference for an older one?)
7. How can I check a libraries version anyway??
8. Thanks if you read this far!!
As an example I ran the configure for imlib and it could not see many of my graphics libraries so I had to modify all of the Makefiles to point to -L/usr/local/lib -jpeg... -tiff etc etc before it would compile. ldconfig had all of these listed.
I NEVER had problems like this under the 2.2.X branch. The most difficult problem I had prior to 3.1 was LD_LIBRARY_PATH not being set! Sorry if this is all a theoretical jumble but this whole mess is killing me!
If you have ANY idea please let me know!!
TIA,
Tony
[-- Attachment #2 --]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>
<META content=text/html;charset=iso-8859-1 http-equiv=Content-Type><!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<META content='"MSHTML 4.72.2106.6"' name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>Greetings, </FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2> I'm having serious difficulties getting
certain items to compile. </FONT></DIV>
<DIV><FONT size=2>I'm using FreeBSD/3.1-RELEASE with the upgrade package
installed.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Everything is pretty much standard issue release and portwise
there. My goal was to install kde or gnome 1.0.1 so I began installing all
of the required programs such as db, docbook, xpm, png, tiff, jpeg, gif, imlib,
etc.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I like to stay current with source releases but if versions
aren't too far off between a port and any source I can find I'll stick with the
port. (Our proxy's methods are so obscure CVSuping seems a pipe dream).
KDE comes with support libraries that work just great for KDE but aren't
necessarily current.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT color=#000000 size=2>The biggest problem I'm having is
libraries. Specifically ones like -jpeg, -tiff, -gif etc. These
libraries are ON my system. I've ported them, packaged them, compiled
them, uninstalled them and repeated the above ad-nauseum. I've forced
--with-extra-libs in configure scripts, I've rebuilt the hints files over and
over. The libraries are THERE but these configure scripts don't see them!
8( ldconfig lists them as elf available libraries etc!</FONT></DIV>
<DIV><FONT color=#000000 size=2></FONT> </DIV>
<DIV><FONT size=2>Let me see if I can toss some questions about to help clarify
what might be happening.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>1. How would I end up building aout libraries on an elf system
with the OBJECT stuff set to elf?</FONT></DIV>
<DIV><FONT color=#000000 size=2>2. Why would libraries not be seen by configure
scripts even though they are quite obviously installed.</FONT></DIV>
<DIV><FONT color=#000000 size=2></FONT><FONT size=2>3. Are configure scripts
(kdelibs-1.1) hard coded to REQUIRE older libraries?</FONT></DIV>
<DIV><FONT size=2>4. Shouldn't I be able to force the building of shared
libraries without fear that everything won't explode?</FONT></DIV>
<DIV><FONT color=#000000 size=2>5. If a library is listed in ldconfig -r should
it not be completely accessable by all of the tools used by configure scripts to
determine what is available? If I have to specify where libraries are all the
time what good is ldconfig??</FONT></DIV>
<DIV><FONT color=#000000 size=2></FONT><FONT size=2>6. Are these graphics
libraries not backwards compatible? (e.g. would kdelibs-1.1 neglect a
newer graphics library in preference for an older one?)</FONT></DIV>
<DIV><FONT size=2>7. How can I check a libraries version anyway??</FONT></DIV>
<DIV><FONT size=2>8. Thanks if you read this far!!</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT size=2>As an example I ran the configure for imlib and it could not
see many of my graphics libraries so I had to modify all of the Makefiles to
point to -L/usr/local/lib -jpeg... -tiff etc etc before it would compile.
ldconfig had all of these listed.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>I NEVER had problems like this under the 2.2.X branch.
The most difficult problem I had prior to 3.1 was LD_LIBRARY_PATH not
being set! Sorry if this is all a theoretical jumble but this whole mess
is killing me!</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2>If you have ANY idea please let me know!!</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>TIA,</FONT></DIV>
<DIV><FONT size=2> Tony</FONT></DIV></BODY></HTML>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001501be747e$783da600$f548c58d>