SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
when running ./configure Orbit2 i get the following error (and of course can't compile it then):
Code:
checking for popt.h... yes
checking whether byte ordering is bigendian... no
configure: error:
Linking is badly borked on your system. Please ensure your library
path is correct
Check config.log for details - check near the end of the log above
'failed program was'
i am running this on a clean slamd64 install (same slack config). since i do not have the logs here and before i do proceed, anyone has experienced this error before?
i've googled and linuxquestioned around but all the posts i find talk about finally getting the .tgz, the .rpm or whatever preconfigured package to solve it. not really what i'm looking for.
the only one i found that could be helpful states:
'try activating gettext'
do you know how i activate gettext and what it is?...
Originally posted by jong357 I was going to ask if your popt problem got resolved. It looks like it did. That should be something else. Never mind...
No actually! i think that's the whole thing, i found this post which could give me a clue:
Quote:
Activating gettext solved the problem, but there's a Catch 22 here;
Orbit 2 requires popt. popt fails to activate because gettext is activated.
Deactivating gettext and activating popt makes Orbit 2 fail it's configure phase.
Activating gettext again results in:
port activate gettext
---> Activating gettext
port activate failed: Image error: /opt/local/share/locale/locale.alias is being
used by the active popt port. Please deactivate this port first, or use the -f
flag to force the activation.
As it says, it can be forced, and that is what I did.
Thanks for all help, Orbit 2 is installed.
But if Orbit 2 requires both popt and gettext to be installed and activated,
there should be a better handling of the mentioned conflict they create. Or at
least some output suggesting to the user how to get around it.
however i sincerely do not understand what this person is talking about... what should i do?
What prefix did you use on popt and did you uninstall both popt versions and reinstall the new one? I would also still post the error from the config log plus a good 10-20 lines above it.
I don't know what he is talking about either. How can you activate popt? It's a library for command parsing... Don't know.. I have both gettext and popt on my system. I would ignore that for now.
I still haven't a clue as to what he's talking about. I don't have a binary named 'port' on my system. That doesn't mean much granted... I would back track to popt. configure and make it again but then do a make uninstall. reinstall the popt binary from slamd and then use pkgtool to remove it. ldconfig and then get back into your new popt and make clean, configure make install (DESTDIR).
You know, it's best to configure something when it's not on your system to begin with. Just my 2 cents. Are you building Gnome 2.10 or 2.8.3? Your earlier popt libs don't seem to come from 1.7... Besides a slew of locales and one man page, this is what popt 1.7-5 dumped on my sytem:
The first 2 being symlinks ofcourse. And even tho you may think the config.log for popt doesn't have anything useful, it ussually does. Post the last 30 lines of it right before the "borked" message. You'll find it in the top directory of popt after the configure bombs out.
Hold on.... Did you get these resolved? I would say no. Your error states there is a linking problem. All of those except for the first one come from glib... 10:1, libgthread is where your linking error is coming from. It might even say so in your config.log.
I know pango doesn't really have any deps but it seems you built it before popt. Thats why I gave you my build order a few days ago... Honestly, I wouldn't feel very good about getting a working gnome if I were you. I would stop right now before you get any further.
Uninstall glib,pango,popt and anything else you've done since your 'fresh' install of slamd... I firmly believe it's best to not have these libs on your system when your trying to compile newer versions of them. Again, just my 2 cents.
Orbit2 clearly links against glib as does every other Gnome package. Along with glib being borked (screwed up) so is pango as your ealier post implies. Well, good luck anyway...
i actually had to add a doinst.sh in the .tgz package:
Code:
( cd usr/lib64 ; rm -rf libglib-2.0.so.0 )
( cd usr/lib64 ; ln -sf libglib-2.0.so.0.600.0 libglib-2.0.so.0 )
( cd usr/lib64 ; rm -rf libglib-2.0.so )
( cd usr/lib64 ; ln -sf libglib-2.0.so.0.600.0 libglib-2.0.so )
( cd usr/lib64 ; rm -rf libgmodule-2.0.so.0 )
( cd usr/lib64 ; ln -sf libgmodule-2.0.so.0.600.0 libgmodule-2.0.so.0 )
( cd usr/lib64 ; rm -rf libgobject-2.0.so.0 )
( cd usr/lib64 ; ln -sf libgobject-2.0.so.0.600.0 libgobject-2.0.so.0 )
( cd usr/lib64 ; rm -rf libgmodule-2.0.so )
( cd usr/lib64 ; ln -sf libgmodule-2.0.so.0.600.0 libgmodule-2.0.so )
( cd usr/lib64 ; rm -rf libgthread-2.0.so )
( cd usr/lib64 ; ln -sf libgthread-2.0.so.0.600.0 libgthread-2.0.so )
( cd usr/lib64 ; rm -rf libgthread-2.0.so.0 )
( cd usr/lib64 ; ln -sf libgthread-2.0.so.0.600.0 libgthread-2.0.so.0 )
( cd usr/lib64 ; rm -rf libgobject-2.0.so )
( cd usr/lib64 ; ln -sf libgobject-2.0.so.0.600.0 libgobject-2.0.so )
and this plus some manual removal of old libraries did the trick. i will have to check this later on a clean slamd64 install to see if it works correctly. however, orbit2 did install without problems. i'll keep on going then. thanks.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.