This was pilot error... I used --enable-languages="c c++" vs. =c,c++. This caused the target to be c++ which causes the configuration havoc... Sorry for the noise... --- LLeweLLyn Reese <llewelly@xxxxxxxxxxxxxxxxxxxxxxxx> wrote: > Mike Ruff <mruff68@xxxxxxxxx> writes: > > > Hey all, > > > > This could be user error, but... > > > > ../gcc-3.3-20030714/configure > > --with-gcc-version-trigger=/work/mruff/gcc-3.3-20 > > 030714/gcc/version.c --host=i686-pc-linux-gnu > > --prefix=/tmp/local --enable-lang > > uages=c c++ --norecursion > > > > On RH7.2 (up2date), produces this... > > > > make[2]: Entering directory > > > `/work/mruff/build/i686-pc-linux-gnu/libstdc++-v3/i > > clude' > > make[2]: *** No rule to make target > > `/work/mruff/gcc-3.3-20030714/libstdc++-v3/ > > onfig/cpu//atomicity.h', needed by `stamp-target'. > > > Stop. > > > > It appears the try_cpu var is not being > > properly set in configure.target, resulting in.... > > > > ATOMICITY_INC_SRCDIR = config/cpu/ > > > > Oh, my shell is pdksh... > > Could you try again using e.g. bash? (to the best of > my knowledge, > bash shouldn't be required, but sometimes things > slip by.. ) > > Could you post > objdir/<target>/libstdc++-v3/config.log ? > > It is a file that logs the tests and results of > libstdc++-v3 > configure. Maybe we can pick through it and > figure out what went > wrong. __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com
