View previous topic :: View next topic |
Author |
Message |
amp_man n00b
Joined: 19 Aug 2006 Posts: 26 Location: Bangor, ME
|
Posted: Tue Feb 12, 2008 11:18 pm Post subject: busybox error with uclibc/gentoo embedded (TinyGentoo) |
|
|
I'm following the guide here: http://gentoo-wiki.com/TinyGentoo
I'm installing this on a 2GB USB flash drive, using OpenSUSE 10.3 as the host system. I've grabbed the uclibc stage 3 and the latest (normal, is that okay?) portage tree, done all of the setup on the chroot and entered the chroot, update portage, then got this while updating world:
Quote: | libbb/time.c: In function 'monotonic_us':
libbb/time.c:20: error: '__NR_clock_gettime' undeclared (first use in this function)
libbb/time.c:20: error: (Each undeclared identifier is reported only once
libbb/time.c:20: error: for each function it appears in.)
libbb/time.c: In function 'monotonic_sec':
libbb/time.c:27: error: '__NR_clock_gettime' undeclared (first use in this function)
make[1]: *** [libbb/time.o] Error 1
make: *** [libbb] Error 2
*
* ERROR: sys-apps/busybox-1.8.2 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
* busybox-1.8.2.ebuild, line 159: Called die
* The specific snippet of code:
* emake busybox || die "build failed"
* The die message:
* build failed
*
* 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-apps/busybox-1.8.2/temp/build.log'.
*
* Messages for package sys-apps/busybox-1.8.2:
* Could not locate user configfile, so we will save a default one
*
* ERROR: sys-apps/busybox-1.8.2 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
* busybox-1.8.2.ebuild, line 159: Called die
* The specific snippet of code:
* emake busybox || die "build failed"
* The die message:
* build failed
*
* 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-apps/busybox-1.8.2/temp/build.log'.
* |
I found something online that said to disable CONFIG_MONOTONIC_SYSCALL, so I entered the work directory and edited the .config, and now it builds successfully. My questions are, how do I use that .config file for future builds, is it safe to use the default portage tree instead of the embedded one, and what would happen if I switched to the normal 2007.0 profile? BTW, this is for an x86 system, I'm just looking for speed and smaller size. |
|
Back to top |
|
|
JohnyB n00b
Joined: 07 Aug 2002 Posts: 16 Location: Luebeck/Germany
|
Posted: Tue Feb 12, 2008 11:27 pm Post subject: |
|
|
Yes, you can reuse your config. There is a use-flag "savedconfig" for busybox.
I hope, this helped
bye then
julian
PS: IIRC the busybox ebuild should give you some output on how to use the savedconfig feature.... |
|
Back to top |
|
|
amp_man n00b
Joined: 19 Aug 2006 Posts: 26 Location: Bangor, ME
|
Posted: Wed Feb 13, 2008 12:09 am Post subject: |
|
|
JohnyB wrote: | Yes, you can reuse your config. There is a use-flag "savedconfig" for busybox.
[...]
PS: IIRC the busybox ebuild should give you some output on how to use the savedconfig feature.... |
Yep, it does, thanks. Any help for the other questions?
Thanks! |
|
Back to top |
|
|
JohnyB n00b
Joined: 07 Aug 2002 Posts: 16 Location: Luebeck/Germany
|
Posted: Wed Feb 13, 2008 12:44 am Post subject: |
|
|
amp_man wrote: | Yep, it does, thanks. Any help for the other questions? |
Ahh, I'm sorry. I didn't read your post carefully enough, I think.
I suggest you to stick with the embedded profile to keep the system small. If you need software from the portage tree, that is masked in your profile, there are better ways to get them installed anyway.
If you switch to the normal profile, an "emerge world -uND" would update your installed packeges and pull in all (may be unwanted) software from the normal profile. But: nothing prevents you from just see what happens:
Use eselet profile to change your profile (or just change the symlink to /etc/make.profile manually) and try emerge world -uNDpv. This will show you everything that *would* happen. If this is ok for you, leave the -p option and this will do the update. If you don't like it, just move back to your recent profile.
You can unmask packeges in /etc/portage/package.unmask. That would be the way to stay with your recent profile. It's also possible to add new use-flags, to make your installed software less "embedded".
Now it's up to you to decide which way to go
bye then
julian |
|
Back to top |
|
|
LucaSpiller Apprentice
Joined: 10 Sep 2004 Posts: 188 Location: Censorship Land (aka England)
|
Posted: Sat Feb 16, 2008 3:07 pm Post subject: |
|
|
To avoid this error you can also upgrade to uclibc-0.9.29. Ebuilds are available in bug 182094. _________________ :: Luca :: Mac Fag :: Original Macbook, 2g RAM :: Closet Linux user (seasoned with salt and pepper) :: C2D E4400 @ 2ghz, 4g RAM (only 3.2g detected under 64bit...), Nvidia 9600GSO :: |
|
Back to top |
|
|
|
|
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
|
|