[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Link error for blahS.c when used in multiple GCC environment.

From: Brendon Costa
Subject: Re: Link error for blahS.c when used in multiple GCC environment.
Date: Tue, 03 Apr 2007 09:53:26 +1000
User-agent: Thunderbird (Windows/20070221)

Ralf Wildenhues wrote:
> * Brendon Costa wrote on Tue, Apr 03, 2007 at 12:21:05AM CEST:
>> They are both C++ libraries yes. I do not tell either of them to link
>> with libstdc++ explicitly. The linking lines for the libs are below.
> Libtool gets the libstdc++ part in, for g++.
>> There is no mention of libstdc++ in the linking of libmystatic. There is
>> however a reference to libstdc++ while linking libmyshared which is
>> added in by libtool. This should be normal behavior shouldn't it?
> I guess.  I meant: why do you have one static and one shared C++
> library?  What is the need?

I don't need it as such. This is a demonstration project that
demonstrates using various linking methods and how that affects the
usage of my analysis tool.

I assumed creating a static library was possible and that the
resulting library could then be used like any other static library on
the system. I could always change it to a convenience library which i
assume would not suffer from this problem, but it would be good to get
to the bottom of this problem.

There are probably a lot of other users out there that are doing this
that have not come across the problem because they are using a single
compiler. I really need to find a resolution to the problem otherwise
they will not be able to use my tool unless they also change to
convenience libraries which may not be what they want.

> I guess I need to dig out whether such a setup is supported by GCC.
> If it is, then it seems we have a Libtool limitation here.

I am sorry i don't understand what you mean by whether such a setup is
supported by GCC.

I will try and compile the project manually without libtool and see if
i can get it to work. That might give more of an indication of where
the problem might be.

Thanks for looking into it. I appreciate the help.

> Thanks,
> Ralf

reply via email to

[Prev in Thread] Current Thread [Next in Thread]