[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: libstdc++
From: |
Ralf Wildenhues |
Subject: |
Re: libstdc++ |
Date: |
Thu, 27 Oct 2005 18:58:43 +0200 |
User-agent: |
Mutt/1.5.11 |
Hi Ethan,
* Ethan A Burns wrote on Thu, Oct 27, 2005 at 06:14:16PM CEST:
>
> Sorry, I did not realize I didn't have the list CCed.
No problem at all. The reminder is also to avoid unpleasant surprises
on your side. ;-)
> I removed the sdl-config -libs from the configure script with the same
> results.
OK. It /could/ be that this may actually break things, but it looks
like it doesn't. (The underlying issue here is that `sdl-config -libs'
just should not output the /usr/lib part, the fact that you are using it
in general is quite alright.)
> I also ran the debug command that you requested the output should be
> attached as a .bz2.
Thanks. It confirms my suspicion: The file
/usr/lib/libSDL.la
contains a reference to
//usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130/libstdc++.la
and surely /home/eaburns/emf-0.9_1/src/libemf.la does, too, because it
links against the former and thus picked it up.
As I don't know gentoo too well, I'm not certain about who is the
culprit here. I *believe* libSDL does not contain C++ code, so it
should not have been linked against libstdc++, consequently
/usr/lib/libSDL.la should not reference it. Did you compile the
installed libSDL yourself? If not, I guess it would be best if you
filed a bug with the corresponding gentoo package, so it can be fixed
upstream.
If libSDL instead *does* contain C++ code, then instead there probably
should be a (developer) package dependency on the C++ library, I guess.
(I really don't know how gentoo does this stuff, so I'm extrapolating
Debian here, hand-wavingly :)
As a workaround, you could remove the libstdc++ part (not the rest!) in
the dependency_libs line from /usr/lib/libSDL.la, then relink your
package (be sure to recreate /home/eaburns/emf-0.9_1/src/libemf.la as
well!). Then everything should work, given that libstdc++ really isn't
needed.
Finally, if I may add a completely unrelated hint: there already exists
a package libEMF[1], which may or may not be related to your package.
If it's not, it may prove beneficial to both if they had distinct names.
:-)
Cheers,
Ralf
[1] See http://libemf.sf.net/. No, I don't have any affiliation with
it, I just happen to have used it before.