| View previous topic :: View next topic |
| Author |
Message |
m27315
Apprentice
Joined: 10 Dec 2004
Posts: 253
Location: 2 workstations down
|
 Posted: Fri Mar 17, 2006 2:18 pm Post subject: undeclared vars cause emerge -e system fails on busybox |
 |
|
During an "emerge -e system", I get the following error (on 117 of 121 - almost there...):
| Code: | i686-pc-linux-gnu-gcc -I/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/include -I/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/include -I/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/e2fsprogs -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -Wstrict-prototypes -Wshadow -Os -march=i386 -mpreferred-stack-boundary=2 -falign-functions=0 -falign-jumps=0 -falign-loops=0 -fomit-frame-pointer -D_GNU_SOURCE -DNDEBUG -I/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/e2fsprogs/ -c -o /var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.o /var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.c
/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.c: In function `icmp6_type_name':
/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.c:246: error: `ICMP6_MEMBERSHIP_QUERY' undeclared (first use in this function)
/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.c:246: error: (Each undeclared identifier is reported only once
/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.c:246: error: for each function it appears in.)
/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.c:247: error: `ICMP6_MEMBERSHIP_REPORT' undeclared (first use in this function)
/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.c:248: error: `ICMP6_MEMBERSHIP_REDUCTION' undeclared (first use in this function)
make: *** [/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.o] Error 1
!!! ERROR: sys-apps/busybox-1.00-r4 failed.
!!! Function src_compile, Line 144, Exitcode 2
!!! build failed
!!! If you need support, post the topmost build error, NOT this status message. |
I have no clue how to debug this, since it is not a "disk-full" or "blocking" error.
I am rebuilding the system because of the glibc2.4 update. Incidentally, I had to update my /etc/make.profile and add the "nptl nptlonly" USE flags to successfully emerge the new glibc2.4. ... Here are the steps I took to get here:- Moved /etc/make.profile pointer from 2005.3 to 2006.0
- edit USE flags in /etc/make.conf to include "nptl nptlonly", per glibc2.4 requirements
- download all necessary files to rebuild system:
rebuild system:
run head first into brick wall -  Any suggestions? Googling for "busybox undeclared ICMP6_MEMBERSHIP_QUERY" did not produce anything, and I can't find anything about this on Bugzilla either...  |
|
| Back to top |
|
 |
ecatmur
Advocate
Joined: 20 Oct 2003
Posts: 3595
Location: Edinburgh
|
|
| Back to top |
|
|
m27315
Apprentice
Joined: 10 Dec 2004
Posts: 253
Location: 2 workstations down
|
| Posted: Fri Mar 17, 2006 2:51 pm Post subject: |
|
|
| ecatmur wrote: | | It's probably because of the glibc 2.4 upgrade. Try using a newer (unstable) busybox. |
Should I pull in the newer version of the dependency too?
| Code: | $ ACCEPT_KEYWORDS="~x86" emerge -epvt busybox
These are the packages that I would merge, in reverse order:
Calculating dependencies ...done!
[ebuild N ] sys-apps/busybox-1.1.0 -debug -floppyboot -make-symlinks -netboot -savedconfig -static 1,375 kB
[ebuild N ] sys-devel/patch-2.5.9-r1 -build -static 0 kB
Total size of downloads: 1,375 kB |
Or, just the unstable version of busybox?
| Code: | $ ACCEPT_KEYWORDS="~x86" emerge -pvt busybox
These are the packages that I would merge, in reverse order:
Calculating dependencies ...done!
[ebuild U ] sys-apps/busybox-1.1.0 [1.00-r4] -debug -floppyboot -make-symlinks -netboot -savedconfig -static 1,375 kB
|
|
|
| Back to top |
|
|
m27315
Apprentice
Joined: 10 Dec 2004
Posts: 253
Location: 2 workstations down
|
| Posted: Fri Mar 17, 2006 3:45 pm Post subject: Thanks! |
|
|
Good call, ecatmur! Using the ~x86 version of busybox did the trick. I proceeding by not using ~x86 for the dependency. We'll see what happens...
Now I am off to do an "emerge -e world"! But, first I did this, just so I don't get hung up again during the world rebuild:
| Code: | | echo "sys-apps/busybox ~x86" >> /etc/portage/package.keywords |
BTW, should I create a bug report for this on Bugzilla?
Thanks!!! |
|
| Back to top |
|
|
ecatmur
Advocate
Joined: 20 Oct 2003
Posts: 3595
Location: Edinburgh
|
| Posted: Fri Mar 17, 2006 3:52 pm Post subject: |
|
|
Glad to hear it.
I guess you could file a bug, though I don't think too many people would be affected at present. OTOH there's a chance glibc 2.4 would go stable on some arch before busybox 1.1.0 does. I imagine the right fix would be to set busybox-1.00 to DEPEND on <sys-libs/glibc-2.4.
_________________
No more cruft
dep: Revdeps that work
Using command-line ACCEPT_KEYWORDS? |
|
| Back to top |
|
|
m27315
Apprentice
Joined: 10 Dec 2004
Posts: 253
Location: 2 workstations down
|
|
| Back to top |
|
|
Dominique_71
Veteran
Joined: 17 Aug 2005
Posts: 1885
Location: Switzerland (Romandie)
|
| Posted: Sun Mar 19, 2006 1:10 pm Post subject: |
|
|
I get the same problem, but after at I have write "sys-apps/busybox ~x86" in "/etc/portage/package.keywords", "emerge --resume" is still installing the same busybox-1.00-r4 version. I have triple checked to be sure at I have no typo error in my package.keywords.
My etc/make.profile is still 2005.1 and my gcc before "emerge -eav system" was gcc3.4.4 and it is now gcc.3.4.5 with glibc2.4. I have put nptlonly in my USE flags. (nptl was allready in my use flags.)
The error is not the same, but it is the same function. | Code: | i686-pc-linux-gnu-gcc -I/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/include -I/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/include -I/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/e2fsprogs -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Wall -Wstrict-prototypes -Wshadow -Os -march=i386 -mpreferred-stack-boundary=2 -falign-functions=0 -falign-jumps=0 -falign-loops=0 -fomit-frame-pointer -D_GNU_SOURCE -DNDEBUG -I/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/e2fsprogs/ -c -o /var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.o /var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.c
/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.c: In function `icmp6_type_name':
/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.c:246: error: `ICMP6_MEMBERSHIP_QUERY' undeclared (first use in this function)
/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.c:246: error: (Each undeclared identifier is reported only once
/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.c:246: error: for each function it appears in.)
/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.c:247: error: `ICMP6_MEMBERSHIP_REPORT' undeclared (first use in this function)
/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.c:248: error: `ICMP6_MEMBERSHIP_REDUCTION' undeclared (first use in this function)
make: *** [/var/tmp/portage/busybox-1.00-r4/work/busybox-1.00/networking/ping6.o] Erreur 1
!!! ERROR: sys-apps/busybox-1.00-r4 failed.
!!! Function src_compile, Line 144, Exitcode 2 |
_________________
"Confirm You are a robot." - the singularity |
|
| Back to top |
|
|
Dominique_71
Veteran
Joined: 17 Aug 2005
Posts: 1885
Location: Switzerland (Romandie)
|
| Posted: Sun Mar 19, 2006 1:43 pm Post subject: |
|
|
It look like if I do an "emerge --system", emerge understand the ~x86 for busybox and is only emerging the rest of the system packages. I am trying that.
...
It worked. It is only 2 more packages at I must emerge by hand, because "emerge --system" don't install them in comparaison to "emerge -eav system". I am lucky at this problem come with one of the last packages of the uppdate.
_________________
"Confirm You are a robot." - the singularity |
|
| Back to top |
|
|
ellotheth
Tux's lil' helper
Joined: 30 Aug 2005
Posts: 123
|
| Posted: Fri Mar 24, 2006 12:54 pm Post subject: |
|
|
| ecatmur wrote: | | It's probably because of the glibc 2.4 upgrade. Try using a newer (unstable) busybox. |
helped me too, thanks.
_________________
monjoy |
|
| Back to top |
|
|
|
Portage & Programming
