| View previous topic :: View next topic |
| Author |
Message |
dixtow
n00b
Joined: 10 May 2005
Posts: 28
|
 Posted: Wed Nov 21, 2007 4:15 pm Post subject: sys-devel/gcc-3.3.6-r1 build fails [depend] |
 |
|
| Code: | stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/ -c -pipe -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -DHAVE_CONFIG_H -I. -If -I/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc -I/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/f -I/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/config -I/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/../include /var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/f/top.c -o f/top.o
stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/ -c -pipe -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -DHAVE_CONFIG_H -I. -If -I/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc -I/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/f -I/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/config -I/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/../include /var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/f/type.c -o f/type.o
stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/ -c -pipe -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -DHAVE_CONFIG_H -I. -If -I/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc -I/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/f -I/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/config -I/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/../include /var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/f/where.c -o f/where.o
rm -f f771
stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/ -pipe -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wtraditional -pedantic -Wno-long-long -DHAVE_CONFIG_H -o f771 f/bad.o f/bit.o f/bld.o f/com.o f/data.o f/equiv.o f/expr.o f/global.o f/implic.o f/info.o f/intrin.o f/lab.o f/lex.o f/malloc.o f/name.o f/parse.o f/src.o f/st.o f/sta.o f/stb.o f/stc.o f/std.o f/ste.o f/storag.o f/stp.o f/str.o f/sts.o f/stt.o f/stu.o f/stv.o f/stw.o f/symbol.o f/target.o f/top.o f/type.o f/where.o main.o libbackend.a ../libiberty/libiberty.a
bison -v /var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/treelang/parse.y\
--output=/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/treelang/parse.c --defines
bison: cannot open file `/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/treelang/parse.y--output=/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/treelang/parse.c': No such file or directory
make[2]: *** [/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/treelang/parse.h] Error 1
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/build/gcc'
make[1]: *** [stage2_build] Error 2
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/build/gcc'
make: *** [bootstrap-lean] Error 2
*
* ERROR: sys-devel/gcc-3.3.6-r1 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* ebuild.sh, line 1383: Called toolchain_src_compile
* toolchain.eclass, line 26: Called gcc_src_compile
* toolchain.eclass, line 1548: Called gcc_do_make
* toolchain.eclass, line 1422: Called die
* The specific snippet of code:
* emake \
* LDFLAGS="${LDFLAGS}" \
* STAGE1_CFLAGS="${STAGE1_CFLAGS}" \
* LIBPATH="${LIBPATH}" \
* BOOT_CFLAGS="${BOOT_CFLAGS}" \
* ${GCC_MAKE_TARGET} \
* || die "emake failed with ${GCC_MAKE_TARGET}"
* The die message:
* emake failed with bootstrap-lean
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-devel/gcc-3.3.6-r1/temp/build.log'.
*
* Messages for package sys-devel/gcc-3.3.6-r1:
*
* ERROR: sys-devel/gcc-3.3.6-r1 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* ebuild.sh, line 1383: Called toolchain_src_compile
* toolchain.eclass, line 26: Called gcc_src_compile
* toolchain.eclass, line 1548: Called gcc_do_make
* toolchain.eclass, line 1422: Called die
* The specific snippet of code:
* emake \
* LDFLAGS="${LDFLAGS}" \
* STAGE1_CFLAGS="${STAGE1_CFLAGS}" \
* LIBPATH="${LIBPATH}" \
* BOOT_CFLAGS="${BOOT_CFLAGS}" \
* ${GCC_MAKE_TARGET} \
* || die "emake failed with ${GCC_MAKE_TARGET}"
* The die message:
* emake failed with bootstrap-lean
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-devel/gcc-3.3.6-r1/temp/build.log'.
*
|
All I wanted was an emerge world -uNDav.... I've got no clue what this "Cannot open file" and "No such file or directory" thing is about. |
|
| Back to top |
|
 |
Sadako
Advocate
Joined: 05 Aug 2004
Posts: 3792
Location: sleeping in the bathtub
|
|
| Back to top |
|
|
monsm
Guru
Joined: 26 Sep 2007
Posts: 467
Location: London, UK
|
| Posted: Fri Nov 23, 2007 11:35 am Post subject: |
|
|
Hi,
I had this problem too with emerge suddenly wanting to install gcc3 when I am already on 4.2.
I am also trying to update world. One of the wikis mentions a world file in the /var tree somewhere, but its not there. I did a "locate world" and found it (I run updatedb reguarly so locate finds what I'm looking for, actually i should setup a cron job for updatedb...[make mental note  ]).
Anyway, I'll try that libstdc++-v3 later, thanks.
mons
UPDATE: Yes, libstdc++v3 solved it for me, cheers. |
|
| Back to top |
|
|
UgolinoII
Tux's lil' helper
Joined: 25 Apr 2004
Posts: 119
|
| Posted: Sun Nov 25, 2007 4:27 pm Post subject: |
|
|
dig around beforehand, you might be surprised ....
| Code: | # cat /etc/cron.daily/slocate
#! /bin/sh
if [ -x /usr/bin/updatedb ]
then
if [ -f /etc/updatedb.conf ]
then
nice /usr/bin/updatedb
else
nice /usr/bin/updatedb -f proc
fi
chown root:locate /var/lib/slocate/slocate.db
fi |
|
|
| Back to top |
|
|
monsm
Guru
Joined: 26 Sep 2007
Posts: 467
Location: London, UK
|
| Posted: Mon Nov 26, 2007 10:30 am Post subject: |
|
|
Thanks for that UgolinoII. I did indeed find that bit in my cron.daily. I guess a few others have had the same brilliant thought
Dixtow are you ok as well now? If so, maybe you should mark the thread subject with "[SOLVED]".
Mons |
|
| Back to top |
|
|
eczary
n00b
Joined: 26 Nov 2007
Posts: 1
|
| Posted: Mon Nov 26, 2007 7:55 pm Post subject: |
|
|
I found the same problem with compiling gcc3, and after some reading of this error messages I found this:
bison -v /var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/treelang/parse.y\
--output=/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/treelang/parse.c --defines
bison: cannot open file `/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/treelang/parse.y--output=/var/tmp/portage/sys-devel/gcc-3.3.6-r1/work/gcc-3.3.6/gcc/treelang/parse.c': No such file or directory
^^ as you can see, there is no space between parse.y and --output=, therefore bison cannot find file to work on.
On the other hand emergeing libstdc++-v3 solved my problem too (in a way that gcc3 is no longer necessary) |
|
| Back to top |
|
|
dixtow
n00b
Joined: 10 May 2005
Posts: 28
|
| Posted: Mon Nov 26, 2007 11:16 pm Post subject: |
|
|
Thanks, issue resolved! |
|
| Back to top |
|
|
Huwawa
Tux's lil' helper
Joined: 24 Feb 2006
Posts: 105
Location: Sol
|
| Posted: Wed Nov 28, 2007 7:54 pm Post subject: |
|
|
| monsm wrote: | Hi,
I had this problem too with emerge suddenly wanting to install gcc3 when I am already on 4.2.
I am also trying to update world. One of the wikis mentions a world file in the /var tree somewhere, but its not there. I did a "locate world" and found it (I run updatedb reguarly so locate finds what I'm looking for, actually i should setup a cron job for updatedb...[make mental note ]).
Anyway, I'll try that libstdc++-v3 later, thanks.
mons
UPDATE: Yes, libstdc++v3 solved it for me, cheers. |
\
If you want an easier to manage locate, try rlocate. You never have to update it, because it uses a kernel module to monitor for file changes. |
|
| Back to top |
|
|
monsm
Guru
Joined: 26 Sep 2007
Posts: 467
Location: London, UK
|
| Posted: Thu Nov 29, 2007 10:24 pm Post subject: |
|
|
| Huwawa wrote: |
If you want an easier to manage locate, try rlocate. You never have to update it, because it uses a kernel module to monitor for file changes. |
Thanks for that. After what I understand from that link its checking if its up to date every time you run it. For someone who have frequent file updates that might be the better choice. I recon, for my use, I'll stick with it being updated once a day with the existing cron job. I already update the time through ntp using cron a couple of times a week anyway. |
|
| Back to top |
|
|
|
Other Things Gentoo
