Taj Morton wrote:
> I was hoping for a solution that maybe involved sedding the libtool file, or
> something like that. If I can't acomplish it that was, I guess I can just
> modify
> Autopackage's wrapper around gcc/g++ to link the compilers libstdc++.so.
Can't you just build+install a private
On Mon, 09 Oct 2006 12:36:47 -0400, Mike Frysinger wrote:
> what you want to do just wont work regardless of the issue you raise below
> ...
> gcc 3.3 and gcc 3.4 have incompatible ABI's so you cannot mix things built
> with the two compilers as you'll just end up with some things using
> libst
Ralf Wildenhues gmx.de> writes:
>
> * Taj Morton wrote on Wed, Oct 11, 2006 at 12:43:36AM CEST:
> > My problem is that when I compile my GCC-3.3 RPM, libtool links
> > against /usr/lib/libstdc++.so, instead of /opt/gcc-3.3/lib/libstdc++.so.
>
> Yes, you already wrote that. And I already told yo
* Taj Morton wrote on Wed, Oct 11, 2006 at 12:43:36AM CEST:
> My problem is that when I compile my GCC-3.3 RPM, libtool links
> against /usr/lib/libstdc++.so, instead of /opt/gcc-3.3/lib/libstdc++.so.
Yes, you already wrote that. And I already told you possible ways out
of your trouble. Did you
Taj Morton gmail.com> writes:
> Yes, that would cause problems. I know that a C++ app must only have /one/
> libstdc+ linked into it (or linked because of dependencies, or dependencies of
> dependencies, etc). On my build machine (moria), I'm building Amarok, the KDE
> music player. Amarok is writ
Ralf Wildenhues gmx.de> writes:
>
> * Taj Morton wrote on Tue, Oct 10, 2006 at 06:59:31AM CEST:
>
> Now, while your libfoo may not be explicitly linked against version Y
> (i.e., 'objdump -p libfoo' shows only one libstdc++ as NEEDED), any
> program using your libfoo and the installed libkdecore
* Taj Morton wrote on Tue, Oct 10, 2006 at 06:59:31AM CEST:
>
> I'm trying to *not* build libraries that link to both libstdc++s.
But you will end up with such brokenness anyway.
Let me try to rephrase Mike's concern as I understand it:
libkdecore was created with some libstdc++ as dependency.
L
Mike Frysinger gentoo.org> writes:
> On Monday 09 October 2006 18:30, Taj Morton wrote:
> > Ralf Wildenhues gmx.de> writes:
> > > Generatlly, you should not link against libraries using two different,
> > > incompatible libstdc++ at the same time.
> >
> > Yeah, it's a bad idea. I'm not talking ab
On Monday 09 October 2006 18:30, Taj Morton wrote:
> Ralf Wildenhues gmx.de> writes:
> > Generatlly, you should not link against libraries using two different,
> > incompatible libstdc++ at the same time.
>
> Yeah, it's a bad idea. I'm not talking about /running/ libraries that link
> against both
Ralf Wildenhues gmx.de> writes:
>
> * Taj Morton wrote on Mon, Oct 09, 2006 at 06:38:10PM CEST:
> > Ralf Wildenhues gmx.de> writes:
> >
> > > Please rerun the link command with --debug and without --silent:
> > > /bin/sh ../../../libtool --debug --tag=CXX --mode=link ... >log 2>&1
> > > gzi
Albert Chin mlists.thewrittenword.com> writes:
>
> On Mon, Oct 09, 2006 at 03:07:45PM +, Taj Morton wrote:
> > When compiling /opt/gcc-3.3/bin/gcc-g++-3.3, I get link errors
> > because libstdc++.so is resolved to /usr/lib/libstdc++.so (the
> > system lib), instead of the compilers lib in /op
* Taj Morton wrote on Mon, Oct 09, 2006 at 06:38:10PM CEST:
> Ralf Wildenhues gmx.de> writes:
>
> > Please rerun the link command with --debug and without --silent:
> > /bin/sh ../../../libtool --debug --tag=CXX --mode=link ... >log 2>&1
> > gzip -9 log
> http://wildgardenseed.com/Taj/libtool
On Mon, Oct 09, 2006 at 03:07:45PM +, Taj Morton wrote:
> Searching the list archives, I see that other people have had this
> problem too, but the solutions in those threads don't really seem to
> work for me...
>
> My problem is that I have 2 compilers installed on my computer:
> gcc-3.4 in
Mike Frysinger gentoo.org> writes:
>
> On Monday 09 October 2006 11:07, Taj Morton wrote:
> > My problem is that I have 2 compilers installed on my computer: gcc-3.4 in
> > /usr (system compiler), and gcc-3.3 in /opt/gcc-3.3.
>
> what you want to do just wont work regardless of the issue you rai
Ralf Wildenhues gmx.de> writes:
Hi Ralf, Thanks for the reply!
> Please rerun the link command with --debug and without --silent:
> /bin/sh ../../../libtool --debug --tag=CXX --mode=link ... >log 2>&1
> gzip -9 log
http://wildgardenseed.com/Taj/libtool-log
> and attach log.gz. Please also s
On Monday 09 October 2006 11:07, Taj Morton wrote:
> My problem is that I have 2 compilers installed on my computer: gcc-3.4 in
> /usr (system compiler), and gcc-3.3 in /opt/gcc-3.3.
what you want to do just wont work regardless of the issue you raise below ...
gcc 3.3 and gcc 3.4 have incompatib
Hello Taj,
* Taj Morton wrote on Mon, Oct 09, 2006 at 05:07:45PM CEST:
>
> When compiling /opt/gcc-3.3/bin/gcc-g++-3.3, I get link errors because
> libstdc++.so is resolved to /usr/lib/libstdc++.so (the system lib), instead of
> the compilers lib in /opt/gcc-3.3/lib. When I delete the /usr/lib/li
17 matches
Mail list logo
