okay, what's a "tagged combination" in libtool?
Phil Edwards
pedwards@disaster.jaj.com
Mon Oct 16 13:55:00 GMT 2000
On Mon, Oct 16, 2000 at 01:32:44PM -0700, Benjamin Kosnik wrote:
>
> I've noticed this sometimes too. On occasion, I have to do
>
> <bkoz@fillmore> /mnt/hd/ahimsa/bld-x86-gcc-3-c
> % rm -rf i686-pc-linux-gnu/
> % make all-target-libstdc++-v3
>
> for some reason the config.cache seems to screw things up.
> (ie, i686-pc-linux-gnu/config.cache)
I've become adept at clearing out the libtool-related lines and leaving
the rest of the cache there. This time it didn't help, even though
config.cache's from various levels/subdirs were cleared. Funky.
> Your results may vary but you might try something like this as well.
rm -rf foo-bar-baz
srcdir/configure --blah
make all-target-libstdc++-v3
is what I need to do, else the foo-bar-baz tree never gets created.
Also funky.
> I'd like to try and clean up some of the residual wonkiness when
> libstdc++-v3 is rebuilt.
More wonkiness to consider in the meantime:
In mkcheck.in, there is a line
C_DIR="`basename @C_INCLUDE_DIR@`"
which gets expanded to
C_DIR="`basename $(top_srcdir)/include/c`"
and then the $(foo) construction has a wildly different effect in shell
scripts then it does in makefiles... I'm working on this, and on limiting
the amount of heap memory used for testsuites (that part's done, actually).
Phil
--
pedwards at disaster dot jaj dot com | pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools. Fools are protected by more capable fools.
More information about the Libstdc++
mailing list