Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Failed to emerge sci-electronics/ghdl after updating system.
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Portage & Programming
View previous topic :: View next topic  
Author Message
Mucka_
n00b
n00b


Joined: 24 Feb 2013
Posts: 5

PostPosted: Sun Feb 24, 2013 11:47 am    Post subject: Failed to emerge sci-electronics/ghdl after updating system. Reply with quote

After I updated system I have problem with emerge sci-electronics/ghdl package.
While building dependency dev-lang/gnat-gcc error appears:
Code:
/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/build/./gcc/xgcc -B/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include -g -fkeep-inline-functions -m32 -O2  -O2 -g -O2 -pipe   -DIN_GCC    -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition  -isystem ./include  -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED   -I. -I. -I../../.././gcc -I/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/gcc-4.3.6/libgcc -I/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/gcc-4.3.6/libgcc/. -I/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/gcc-4.3.6/libgcc/../gcc -I/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/gcc-4.3.6/libgcc/../include -I/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/gcc-4.3.6/libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS -DUSE_TLS -o unwind-dw2.o -MT unwind-dw2.o -MD -MP -MF unwind-dw2.dep -fexceptions -c /var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/gcc-4.3.6/libgcc/../gcc/unwind-dw2.c
In file included from /var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/gcc-4.3.6/libgcc/../gcc/unwind-dw2.c:338:
/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/gcc-4.3.6/libgcc/../gcc/config/i386/linux-unwind.h: In function ‘x86_fallback_frame_state’:
/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/gcc-4.3.6/libgcc/../gcc/config/i386/linux-unwind.h:142: error: field ‘info’ has incomplete type
make[5]: *** [unwind-dw2.o] Error 1
make[5]: Leaving directory `/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/build/x86_64-pc-linux-gnu/32/libgcc'
make[4]: *** [multi-do] Error 1
make[4]: Leaving directory `/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/build/x86_64-pc-linux-gnu/libgcc'
make[3]: *** [all-multi] Error 2
make[3]: Leaving directory `/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/build/x86_64-pc-linux-gnu/libgcc'
make[2]: *** [all-stage1-target-libgcc] Error 2
make[2]: Leaving directory `/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/build'
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory `/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/build'
make: *** [bootstrap] Error 2
emake failed
 * ERROR: dev-lang/gnat-gcc-4.3.6 failed (compile phase):
 *   bootstrap failed
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_compile
 *   environment, line 3838:  Called gnatbuild_src_compile 'configure' 'make-tools' 'bootstrap'
 *   environment, line 2654:  Called die
 * The specific snippet of code:
 *                       emake bootstrap || die "bootstrap failed"
 *
 * If you need support, post the output of `emerge --info '=dev-lang/gnat-gcc-4.3.6'`,
 * the complete build log and the output of `emerge -pqv '=dev-lang/gnat-gcc-4.3.6'`.
 * The complete build log is located at '/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/build'
 * S: '/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/gcc-4.3.6'

>>> Failed to emerge dev-lang/gnat-gcc-4.3.6, Log file:

>>>  '/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/temp/build.log'

 * Messages for package dev-lang/gnat-gcc-4.3.6:

 * ERROR: dev-lang/gnat-gcc-4.3.6 failed (compile phase):
 *   bootstrap failed
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_compile
 *   environment, line 3838:  Called gnatbuild_src_compile 'configure' 'make-tools' 'bootstrap'
 *   environment, line 2654:  Called die
 * The specific snippet of code:
 *                       emake bootstrap || die "bootstrap failed"

Instaling explicitly gnat-gcc works, but then emerge --nodeps ghdl fails with the same error.
My env looks:
Code:
Portage 2.1.11.52 (default/linux/amd64/13.0/desktop, gcc-4.6.3, glibc-2.16.0, 3.8.0-gentoo x86_64)
=================================================================
                         System Settings
=================================================================
System uname: Linux-3.8.0-gentoo-x86_64-Intel-R-_Core-TM-_i3_CPU_M_350_@_2.27GHz-with-gentoo-2.2
KiB Mem:     3838208 total,    161552 free
KiB Swap:    4194300 total,   4159292 free
Timestamp of tree: Sun, 24 Feb 2013 04:45:01 +0000
ld GNU ld (GNU Binutils) 2.23.1
app-shells/bash:          4.2_p42
dev-java/java-config:     2.1.12-r1
dev-lang/python:          2.7.3-r3, 3.2.3-r2
dev-util/cmake:           2.8.10.2-r1
dev-util/pkgconfig:       0.28
sys-apps/baselayout:      2.2
sys-apps/openrc:          0.11.8
sys-apps/sandbox:         2.6
sys-devel/autoconf:       2.13, 2.69
sys-devel/automake:       1.11.6, 1.13.1
sys-devel/binutils:       2.23.1
sys-devel/gcc:            4.6.3
sys-devel/gcc-config:     1.8
sys-devel/libtool:        2.4.2
sys-devel/make:           3.82-r4
sys-kernel/linux-headers: 3.7 (virtual/os-headers)
sys-libs/glibc:           2.16.0

Few day ago on a similar system (most config files the same) but not updated i had no problem at all to install this package. System looked like:
Code:
Portage 2.1.11.50 (default/linux/amd64/13.0, gcc-4.6.3, glibc-2.15-r3, 3.7.4-gentoo x86_64)
=================================================================
                         System Settings
=================================================================
System uname: Linux-3.7.4-gentoo-x86_64-Intel-R-_Core-TM-_i5-3450_CPU_@_3.10GHz-with-gentoo-2.1
KiB Mem:     8131468 total,   5572312 free
KiB Swap:   15624996 total,  15624996 free
Timestamp of tree: Fri, 22 Feb 2013 07:45:01 +0000
ld GNU ld (GNU Binutils) 2.22
app-shells/bash:          4.2_p37
dev-java/java-config:     2.1.12-r1
dev-lang/python:          2.7.3-r3, 3.2.3
dev-util/cmake:           2.8.10.2-r1
dev-util/pkgconfig:       0.27.1
sys-apps/baselayout:      2.1-r1
sys-apps/openrc:          0.11.8
sys-apps/sandbox:         2.5
sys-devel/autoconf:       2.13, 2.69
sys-devel/automake:       1.11.6
sys-devel/binutils:       2.22-r1
sys-devel/gcc:            4.6.3
sys-devel/gcc-config:     1.7.3
sys-devel/libtool:        2.4-r1
sys-devel/make:           3.82-r4
sys-kernel/linux-headers: 3.6 (virtual/os-headers)
sys-libs/glibc:           2.15-r3
=================================================================
                        Package Settings
=================================================================

sci-electronics/ghdl-0.29
sci-electronics/ghdl-0.29 was built with the following:
USE="(multilib)" ABI_X86="64"

I found some clues on the internet that changing single line in the header file can fix the problem
but this was info from arch linux forum and was quite old and was related to gcc itself not gnat-gcc.
I've reemerged gcc, done revdep-rebuild, still error appear.
I'm quite fresh gentoo user and i'm stuck at this point. Anybody can help.
Back to top
View user's profile Send private message
rmzelnick
n00b
n00b


Joined: 03 Feb 2013
Posts: 24

PostPosted: Mon Feb 25, 2013 6:25 am    Post subject: Reply with quote

What happens when you try to compile a C program using GCC?
Back to top
View user's profile Send private message
Mucka_
n00b
n00b


Joined: 24 Feb 2013
Posts: 5

PostPosted: Mon Feb 25, 2013 8:43 pm    Post subject: Reply with quote

Nothing abnormal, i'm using gcc few times a day.
For now I found a solution but it's quite ugly.
While emerging gdhl after unpacking sources to the tmp dir, i edited files
/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/gcc-4.3.6/gcc/config/i386/linux-unwind.h
and the analogical file from the ghdl source, following tip from the arch linux forum
http://pastebin.com/VkgE27Pd
and everything compiled and works fine (i'm using whole day ghdl and it's working fine).
Like I said i'm quite new in gentoo and I don't know if I should consider this as a bug and report it,
or it's still my fault.
Back to top
View user's profile Send private message
daniel.santos
n00b
n00b


Joined: 05 Jun 2007
Posts: 49

PostPosted: Sun Jul 06, 2014 11:49 pm    Post subject: Reply with quote

Mucka_ wrote:
Nothing abnormal, i'm using gcc few times a day.
For now I found a solution but it's quite ugly.
While emerging gdhl after unpacking sources to the tmp dir, i edited files
/var/tmp/portage/dev-lang/gnat-gcc-4.3.6/work/gcc-4.3.6/gcc/config/i386/linux-unwind.h
and the analogical file from the ghdl source, following tip from the arch linux forum
http://pastebin.com/VkgE27Pd
and everything compiled and works fine (i'm using whole day ghdl and it's working fine).
Like I said i'm quite new in gentoo and I don't know if I should consider this as a bug and report it,
or it's still my fault.


Sorry to resurrect an ancient thread, but this is now bug #516276. OK, I guess I'm not really sorry.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Portage & Programming All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum