LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 08-04-2012, 08:16 AM   #1
_gin
LQ Newbie
 
Registered: Aug 2012
Posts: 20

Rep: Reputation: Disabled
problem linker slackware-current


I've been running slackware64-current since the beta 1 was announced and I get a lot of build error like this one:
Code:
'dlclose@@GLIBC_2.2.5' is defined in DSO /lib64/libdl.so.2 so try adding it to the linker command line
Is It a commun behaviour for a beta release ?
Since It' the first time that I run slackware-current, I'm asking you.

Most of the time (but not all the time...unfortunately) the fix is trivial. I export in the shell or I add the missing library to the Makefile, but It happens so often that It's getting on my nerves actually.

I read in on the mailing list for trinitydesktop that gcc-4.7 broke quite a bit of their code.
Are those linker troubles related to gcc itself ?
If so, I don't mind downgrading gcc, anyhow gcc-4.6.3 is running fine on current.

Is it due to binutils ?

I wonder where the proble lies, because I've been using Slackware fulltime since slackware64-13.0, and I never ran against such impediments before.
Usually compiling programs on Slackware is a play game.
 
Old 08-04-2012, 08:37 AM   #2
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,184

Rep: Reputation: 1022Reputation: 1022Reputation: 1022Reputation: 1022Reputation: 1022Reputation: 1022Reputation: 1022Reputation: 1022
I run the 32 bit version so I can't help that much, but I would first make sure that your your slackware64-current be fully and properly updated with the usual sequence:

slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg clean-system

with of course a proper mirror uncommented in /etc/slackpkg/mirrors and all .new files taken care of.

But I guess you did check that already

And maybe you could give an example of a program that someone can try to compile & link on his/her system to see if he/she gets the same results.

Last edited by Didier Spaier; 08-04-2012 at 08:47 AM. Reason: last line added
 
Old 08-04-2012, 09:06 AM   #3
_gin
LQ Newbie
 
Registered: Aug 2012
Posts: 20

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Didier Spaier View Post
...I would first make sure that your your slackware64-current be fully and properly updated with the usual sequence...
Well actually I didn't upgrade from 13.37, I made a fresh install with an iso taken from ftp.slackware.no.

I don't have kde installed at the moment otherwise all the libraries, including the new ones are installed. I don't think a missing prog is involved in here.

The code error I gave for instance comes from Juce, the c++ gui library.
I order to compile Juce, I not only added -ldl to the makefile but -lXext as well.
Afterwards, everything compiled fine.

If I'm the only one who experience these troubles, that mean that my install is corrupted, otherwise something goes wrong with the toolchain.
 
Old 08-04-2012, 09:21 AM   #4
ponce
Senior Member
 
Registered: Aug 2004
Location: Pisa, Italy
Distribution: Slackware
Posts: 2,434

Rep: Reputation: 867Reputation: 867Reputation: 867Reputation: 867Reputation: 867Reputation: 867Reputation: 867
I think nothing is going wrong, it's the new ld that needs those LDFLAGS because indirect linking isn't allowed anymore: many apps used it and they haven't been fixed yet, so the build scripts must be patched.
See here

http://fedoraproject.org/wiki/Unders...gDSOLinkChange

Last edited by ponce; 08-04-2012 at 09:25 AM.
 
Old 08-04-2012, 09:31 AM   #5
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad T61 6457-4XG
Posts: 4,184

Rep: Reputation: 1022Reputation: 1022Reputation: 1022Reputation: 1022Reputation: 1022Reputation: 1022Reputation: 1022Reputation: 1022
There is a (theoretical) possibility that the iso be corrupted or non complete then.

If you don't get a more valuable answer in some time I would try with another iso then.

Or you could keep a local mirror of -current, use an USB installer and (re) install the packages from your local mirror.

Or run "slackpkg install slackware" and see what it shows, beside KDE packages.

EDIT Sorry to be late, I guess that ponce's answer is a better one.

Last edited by Didier Spaier; 08-04-2012 at 09:33 AM.
 
Old 08-04-2012, 09:48 AM   #6
_gin
LQ Newbie
 
Registered: Aug 2012
Posts: 20

Original Poster
Rep: Reputation: Disabled
ponce eventually gave the answer.
The link from Fedora is quite clear on the topic.

Ponce, Didier thank you, both, for your help and from my part, sorry for the noise !
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Script to build always a current ISO image of Slackware (slackware-current) robertjinx Slackware 2 12-09-2010 02:00 AM
[SOLVED] cryptic linker error (i really dont like linker errors); smeezekitty Programming 2 09-19-2009 02:21 AM
slackware-current problem KenHan Slackware 19 07-31-2003 10:05 PM


All times are GMT -5. The time now is 01:36 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration