Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 153677 - emerging sys-devel/gcc-4.1.1 fails due to syntax error
Summary: emerging sys-devel/gcc-4.1.1 fails due to syntax error
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-01 06:28 UTC by gentoolinux
Modified: 2006-11-06 06:59 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gentoolinux 2006-11-01 06:28:24 UTC
Hello,

during bootstrapping (I am doing a fresh stage 1 install) the emerge of sys-devel/gcc-4.1.1 fails due to a syntax error. The source compiles fine but installing fails. Here's the error:

for file in /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/resize_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/find_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/erase_no_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/resize_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/debug_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/erase_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/policy_access_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/cmp_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/insert_no_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/insert_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/find_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/find_no_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/cond_key_dtor_entry_dealtor.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/constructor_destructor_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/entry_list_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/constructor_destructor_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/erase_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/cc_ht_map_.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/constructor_destructor_no_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/standard_policies.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/info_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/iterators_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/insert_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/debug_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/size_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/debug_no_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/cc_ht_map_/resize_no_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/resize_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/find_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/erase_no_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/resize_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/debug_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/erase_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/policy_access_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/insert_no_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/insert_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/find_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/find_no_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/constructor_destructor_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/constructor_destructor_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/erase_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/constructor_destructor_no_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/info_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/insert_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/debug_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/gp_ht_map_.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/iterator_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/debug_no_store_hash_fn_imps.hpp /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/ext/pb_assoc/detail/gp_ht_map_/resize_no_store_hash_fn_imps.hpp ; do \
  install_base=/var/tmp/portage/gcc-4.1.1/image//usr/lib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./ext/pb_assoc ; \
  relative_name=`echo $file | sed -e "s|/var/tmp/portage/gcc-4.1.1/work/gc-4.1.1/libstdc++-v3/include/ext/pb_assoc|.|g"`` ;\
  /bin/install -c -m 644 ${file} ${install_base}/${relative_name} ; done
/bin/sh: -c: line 0: unexpected EOF while looking for matching ``'
/bin/sh: -c: line 1: syntax error: unexpected end of file
make[4]: *** [install-headers] Error 2
make[4]: Leaving directory `/var/tmp/portage/gcc-4.1.1/work/build/i686-pc-linux-gnu/libstdc++-v3/include'
make[3]: *** [install-am] Error 2
make[3]: Leaving directory `/var/tmp/portage/gcc-4.1.1/work/build/i686-pc-linux-gnu/libstdc++-v3/include'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/gcc-4.1.1/work/build/i686-pc-linux-gnu/libstdc++-v3'
make[1]: *** [install-target-libstdc++-v3] Error 2
make[1]: Leaving directory `/var/tmp/portage/gcc-4.1.1/work/build'
make: *** [install] Error 2

!!! ERROR: sys-devel/gcc-4.1.1 failed.
Call stack:
  ebuild.sh, line 1546:   Called dyn_install
  ebuild.sh, line 1020:   Called src_install
  ebuild.sh, line 1255:   Called toolchain_src_install
  toolchain.eclass, line 33:   Called gcc-compiler_src_install
  toolchain.eclass, line 1608:   Called die

!!! (no error message)
!!! If you need support, post the topmost build error, and the call stack if relevant.


Looks like there is one ` too much in the line with "relative_name".

Any help appreciated. Thanks in advance!
Comment 1 SpanKY gentoo-dev 2006-11-05 03:18:00 UTC
that file isnt generated or anything so i dont know why there is `` like that

run this command and see what you get:
grep relative_name= /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/Makefile*
Comment 2 gentoolinux 2006-11-05 07:25:02 UTC
livecd portage # grep relative_name= /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/Makefile*
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/Makefile.am:       relative_name=`echo $$file | sed -e "s|${assoc_srcdir}|.|g"` ;\
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/Makefile.am:       relative_name=`echo $$file | sed -e "s|${assoc_srcdir}|.|g"` ;\
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/Makefile.am:       relative_name=`echo $$file | sed -e "s|${assoc_srcdir}|.|g"` ;\
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/Makefile.am:       relative_name=`echo $$file | sed -e "s|${assoc_srcdir}|.|g"` ;\
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/Makefile.am:       relative_name=`echo $$file | sed -e "s|${assoc_srcdir}|.|g"` ;\
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/Makefile.in:       relative_name=`echo $$file | sed -e "s|${assoc_srcdir}|.|g"` ;\
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/Makefile.in:       relative_name=`echo $$file | sed -e "s|${assoc_srcdir}|.|g"` ;\
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/Makefile.in:       relative_name=`echo $$file | sed -e "s|${assoc_srcdir}|.|g"` ;\
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/Makefile.in:       relative_name=`echo $$file | sed -e "s|${assoc_srcdir}|.|g"` ;\
/var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/include/Makefile.in:       relative_name=`echo $$file | sed -e "s|${assoc_srcdir}|.|g"` ;\

There is only one ` ?!
Any ideas?
Comment 3 SpanKY gentoo-dev 2006-11-05 13:32:04 UTC
so i guess /var/tmp/portage/gcc-4.1.1/work/build/i686-pc-linux-gnu/libstdc++-v3/include/Makefile has two '' at the end ?

re-emerge gcc and see if it still fails
Comment 4 gentoolinux 2006-11-06 05:43:08 UTC
Sorry, I don't understand your first question. The file /var/tmp/portage/gcc-4.1.1/work/build/i686-pc-linux-gnu/libstdc++-v3/include/Makefile does not exist. There is only a file Makefile.am and Makefile.in. You can find them in gcc-4.1.1.tar.bz2

Emerging gcc via "emerge --nodeps gcc" causes no error. After that I started the bootstrapping script again. Now I get the following error when installing:

for file in /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/config/os/gnu-linux/ctype_base.h /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/config/os/gnu-linux/ctype_inline.h /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/config/os/gnu-linux/ctype_noninline.h /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/config/os/gnu-linux/os_defines.h /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/config/cpu/generic/atomic_word.h /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/config/cpu/generic/cxxabi_tweaks.h /var/tmp/portage/gcc-4.1.1/work/gcc-4.1.1/libstdc++-v3/config/cpu/generic/cpu_defines.h         ./i686-pc-linux-gnu/bits/basic_file.h ./i686-pc-linux-gnu/bits/c++config.h ./i686-pc-linux-gnu/bits/c++allocator.h ./i686-pc-linux-gnu/bits/c++io.h ./i686-pc-linux-gnu/bits/c++locale.h ./i686-pc-linux-gnu/bits/messages_members.h ./i686-pc-linux-gnu/bits/time_members.h  \
 ./i686-pc-linux-gnu/bits/gthr.h ./i686-pc-linux-gnu/bits/gthr-single.h ./i686-pc-linux-gnu/bits/gthr-posix.h ./i686-pc-linux-gnu/bits/gthr-tpf.h ./i686-pc-linux-gnu/bits/gthr-default.h; do \
  /bin/install -c -m 644 ${file} /var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits; done
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
/bin/install: cannot create regular file `/var/tmp/portage/gcc-4.1.1/imag//usr/llib/gcc/i686-pc-linux-gnu/4.1.1/include/g++-v4/./i686-pc-linux-gnu/bits': No such file or directory
make[4]: *** [install-headers] Error 1
make[4]: Leaving directory `/var/tmp/portage/gcc-4.1.1/work/build/i686-pc-linux-gnu/libstdc++-v3/include'
make[3]: *** [install-am] Error 2
make[3]: Leaving directory `/var/tmp/portage/gcc-4.1.1/work/build/i686-pc-linux-gnu/libstdc++-v3/include'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/gcc-4.1.1/work/build/i686-pc-linux-gnu/libstdc++-v3'
make[1]: *** [install-target-libstdc++-v3] Error 2
make[1]: Leaving directory `/var/tmp/portage/gcc-4.1.1/work/build'
make: *** [install] Error 2

!!! ERROR: sys-devel/gcc-4.1.1 failed.


I think, I should do a stage 2 install...
Comment 5 SpanKY gentoo-dev 2006-11-06 06:59:43 UTC
this isnt exactly helpful in your case, but building up from stage1 isnt suggested anymore ... if you cant reproduce it with a stage3+ system then i'm not going to investigate it further ...

if you feel like looking into it and reporting back, i'd appreciate it ... there is just plenty of other things i could work on otherwise