Re: Relationship between libstdc++ and libsupc++

[Phil Edwards <phil at jaj dot com>]

On Wed, Nov 12, 2003 at 03:55:45PM -0800, Ramadass, Ramanathan wrote:
> So both the libstdc++ & libsupc++ should be built when i build gcc? In my case no libraries are built maybe because i give the --with-libs option (i am building a cross from i686-pc-linux-gnu to i386-elf) and gmake target as "all-gcc". Other then libgcc no libraries are installed. After building and installing gcc i run gmake with target "all-target-libstdc++-v3" when it fails. The failure happens at;

You're making it more difficult than it needs to be.  I don't think
--with-libs does anything, but in any case, don't split up the make targets.
Just type "make" and let it run.


> checking whether the C compiler ( /mnt/home/rramadass/gnu/gccobj/gcc/xgcc -B/mnt/home/rramadass/gnu/gccobj/gcc/ -B/mnt/home/rramadass/gnu/gcc/i386-elf/bin/ -B/mnt/home/rramadass/gnu/gcc/i386-elf/lib/ -isystem /mnt/home/rramadass/gnu/gcc/i386-elf/include -O2 -g -O2 ) works... no
> configure: error: installation or configuration problem: C compiler cannot create executables.
> gmake: *** [configure-target-libiberty] Error 1

Look in i386-elf/libiberty/config.log to see what went wrong.


> "all-target-libstdc++=v3" depends on "all-target-libiberty" which is
> dependant on "configure-target-libiberty". So how can i build libstdc++?

Build libiberty.  (You don't need to install it, but if X depends on Y,
you can't just skip Y and go straight to X.  Not much point in writing
the dependency if you could...)


> Also since i need only libsupc++ is there a simple way to bypass all these and build libsupc++ only?

Not in 3.3.

-- 
Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
    - Brian W. Kernighan