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

Problems with g++ (Was: Re: A plan to get rid of unnecessary package dependencies)



Hello,

On Mon, 25 Sep 2006, Christian Aichinger wrote:
> As Steve Langasek detailed in his d-d-a mail[1], unnecessary
> dependencies cause lots of problems, as they make transitions
> bigger then they need to be.

Sorry for the noise. I wrote earlier to Christian Aichinger
(and submitted a report #389555 against g++) and got no response.

On Tue, 26 Sep 2006, I wrote:
>I have filed an ITA for "swish++" so the problems with that package land
>in my lap! 
>
>When looking through the makefiles and the libraries that are linked
>there is no mention of the two offending libraries "libm" or
>"libgcc". On the other hand I noticed (by giving CC="g++ -v") that it
>was "g++" which was putting these libraries in its call to collect2.
> 
>If instead of this I link with "gcc" and add a "-lstdc++" in order to
>get it to link correctly then the extra "NEEDED"'s disappear.
> 
>I suppose I could fix the problem this way, but is this not a bug with
>"g++"?
 
On Tue, 26 Sep 2006, I wrote:
>Actually, I found the following thread:
>
> 	http://gcc.gnu.org/ml/gcc/2005-01/msg00229.html
>
>This seems to indicate that g++ always links in libm and
>libgcc_*.
>
>This will mean that programs that use g++ to link will always create
>a problem.

Perhaps this should be solved by *not* using g++ to link.

I have now created a version of the "swish++" package that does not
use "g++" to link and uses "gcc" instead.

My question is whether this is "The Way". If so it could be
documented as a solution to at least some of the "problem" cases.

Regards,

Kapil.

P.S. Please CC me I do not subscribe to this list.
--

Attachment: signature.asc
Description: Digital signature


Reply to: