osdir.com
mailing list archive

Subject: portage light? - msg#00002

List: linux.gentoo.embedded

Date: Prev Next Index Thread: Prev Next Index
Hi,

I wonder if there is a way to filter out things in portage that you dont
want. Like dev-dotnet, games-*, gnome-*, kde-*, x11-*

My portage tree is over 240MB and its really slow on older computers.

Any other tips to make portage more lightweight? Not only speed but also
size to save bandwidth/diskspace for my gentoo based project.

Natanael Copa



Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

Re: Error building glibc for arm on AMD's?

On Tue, 2007-07-03 at 19:41 -0700, Jeff Cunningham wrote: > I am new to this list. I'm hoping someone will be able to help me solve > a problem building a toolchain for use with a 2.6 kernel on an arm9 > board using crossdev. The issue is this: I can build a toolchain > successfully on a Pentium 4 dual-core machine. But when I try to build > the exact same toolchain on either of two AMD boxes it fails with the > same error while building glibc. Thats your env sneaking in. blame eradicator. Anyway what seems to work for most people cleanly is to make a 32bit chroot and do your delopment from there. Good luck. > > I looked through the archives of this mailing list without seeing > anything relevant. I am hoping someone has seen this before and can tell > me what I'm doing wrong. > > Here are the particulars: > > The toolchain in question will build with the following command: > > USE="-* nls glibc-omitfp nptl nptlonly tls" crossdev \ > --b 2.16.1-r3 \ > --g 4.1.1-r3 \ > --k 2.6.19.2-r2 \ > --l 2.3.6-r5 \ > -t arm-softfloat-linux-gnu > > on the Intel P4 box is running Gentoo 2.6.18 (I don't know the revision > number right now). But if fails on both of these: > > Athlon-xp box running Gentoo 2.6-19-r5 or 2.6-20-r8 > Duron box running Gentoo 2.6.17-r4 > > Here is the error message for either of the AMD's: > > * Host Portage ARCH: x86 > * Target Portage ARCH: arm > * Target System: arm-softfloat-linux-gnu > * Stage: 4 (C/C++ compiler) > > * binutils: binutils-2.16.1-r3 > * gcc: gcc-4.1.1-r3 > * headers: linux-headers-2.6.19.2-r2 > * libc: glibc-2.3.6-r5 > > * PORTDIR_OVERLAY: /usr/local/portage > * PORT_LOGDIR: /var/log/portage > * PKGDIR: > /usr/portage/packages/cross/arm-softfloat-linux-gnu > * PORTAGE_TMPDIR: /var/tmp/cross/arm-softfloat-linux-gnu > _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ > - _ - ~ - _ - ~ - _ - ~ - _ > * Forcing the latest versions of binutils-config/gcc-config > ... [ ok ] > * Log: /var/log/portage/cross-arm-softfloat-linux-gnu-binutils.log > * Emerging cross-binutils > ... > [ ok ] > * Log: /var/log/portage/cross-arm-softfloat-linux-gnu-gcc-stage1.log > * Emerging cross-gcc-stage1 > ... > [ ok ] > * Log: /var/log/portage/cross-arm-softfloat-linux-gnu-linux-headers.log > * Emerging cross-linux-headers > ... > [ ok ] > * Log: /var/log/portage/cross-arm-softfloat-linux-gnu-glibc.log > * Emerging cross-glibc ... > > * glibc failed :( > * If you file a bug, please attach the following logfiles: > * /var/log/portage/cross-arm-softfloat-linux-gnu-info.log > * /var/log/portage/cross-arm-softfloat-linux-gnu-glibc.log > > > And here is the topmost build error in the glibc.log: > > gcc ../sysdeps/unix/sysv/linux/arm/sysdep.S -c > -I../include > -I. > -I/var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softfloat-linux-gnu/glibc-2.3.6 > -r5/work/build-default-arm-softfloat-linux-gnu-linuxthreads/csu > -I.. > -I../libio > -I/var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softfloat-linux-gnu/glibc-2.3.6 > -r5/work/build-default-arm-softfloat-linux-gnu-linuxthreads > -I../sysdeps/arm/elf > -I../linuxthreads/sysdeps/unix/sysv/linux/arm > -I../linuxthreads/sysdeps/unix/sysv/linux > -I../linuxthreads/sysdeps/pthread > -I../sysdeps/pthread > -I../linuxthreads/sysdeps/unix/sysv > -I../linuxthreads/sysdeps/unix > -I../linuxthreads/sysdeps/arm > -I../libidn/sysdeps/unix > -I../sysdeps/unix/sysv/linux/arm > -I../sysdeps/unix/sysv/linux > -I../sysdeps/gnu > -I../sysdeps/unix/common > -I../sysdeps/unix/mman > -I../sysdeps/unix/inet > -I../sysdeps/unix/sysv > -I../sysdeps/unix/arm > -I../sysdeps/unix > -I../sysdeps/posix > -I../sysdeps/arm > -I../sysdeps/wordsize-32 > -I../sysdeps/ieee754/flt-32 > -I../sysdeps/ieee754/dbl-64 > -I../sysdeps/ieee754 > -I../sysdeps/generic/elf > -I../sysdeps/generic > -nostdinc > -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include > -isystem /usr/arm-softfloat-linux-gnu/usr/include > -D_LIBC_REENTRANT > -include ../include/libc-symbols.h > -DHAVE_INITFINI > -DASSEMBLER > -I/var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softfloat-linux-gnu/glibc-2.3.6 > -r5/work/build-default-arm-softfloat-linux-gnu-linuxthreads/csu/. > -Wa,--noexecstack > -Wa,--noexecstack > -o > /var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softfloat-linux-gnu/glibc-2.3. > 6-r5/work/build-default-arm-softfloat-linux-gnu-linuxthreads/csu/sysdep.o > -MD > -MP > -MF > /var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softfloat-linux-gnu/glibc-2.3 > .6-r5/work/build-default-arm-softfloat-linux-gnu-linuxthreads/csu/sysdep.o.dt > > -MT > /var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softfloat-linux-gnu/glibc-2.3 > .6-r5/work/build-default-arm-softfloat-linux-gnu-linuxthreads/csu/sysdep.o > ../sysdeps/generic/libc-start.c: In function '__libc_start_main': > ../sysdeps/generic/libc-start.c:192: warning: implicit declaration of > function '__guard_se > tup' > ../sysdeps/unix/sysv/linux/arm/sysdep.S: Assembler messages: > ../sysdeps/unix/sysv/linux/arm/sysdep.S:31: Error: no such instruction: > `rsb r0,r0,$0' > ../sysdeps/unix/arm/sysdep.S:41: Error: invalid char '[' beginning > operand 2 `[sp' > ../sysdeps/unix/arm/sysdep.S:42: Error: invalid char '[' beginning > operand 2 `[sp' > ../sysdeps/unix/arm/sysdep.S:43: Error: no such instruction: `bl > __errno_location(PLT)' > ../sysdeps/unix/arm/sysdep.S:44: Error: no such instruction: `ldr r1,[sp],' > ../sysdeps/unix/arm/sysdep.S:45: Error: invalid char '[' beginning > operand 2 `[r0]' > ../sysdeps/unix/arm/sysdep.S:46: Error: no such instruction: `mvn r0,$0' > ../sysdeps/unix/arm/sysdep.S:47: Error: no such instruction: `ldr pc,[sp],' > make[2]: *** > [/var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softfloat-linux-gnu > /glibc-2.3.6-r5/work/build-default-arm-softfloat-linux-gnu-linuxthreads/csu/sysdep.o] > > Erro > r 1 > make[2]: *** Waiting for unfinished jobs.... > make[2]: Leaving directory > `/var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softf > loat-linux-gnu/glibc-2.3.6-r5/work/glibc-2.3.6/csu' > make[1]: *** [csu/subdir_lib] Error 2 > make[1]: Leaving directory > `/var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softf > loat-linux-gnu/glibc-2.3.6-r5/work/glibc-2.3.6' > make: *** [all] Error 2 > > !!! ERROR: cross-arm-softfloat-linux-gnu/glibc-2.3.6-r5 failed. > Call stack: > ebuild.sh, line 1615: Called dyn_compile > ebuild.sh, line 972: Called qa_call 'src_compile' > ebuild.sh, line 44: Called src_compile > glibc-2.3.6-r5.ebuild, line 1127: Called src_compile > glibc-2.3.6-r5.ebuild, line 1138: Called toolchain-glibc_src_compile > glibc-2.3.6-r5.ebuild, line 221: Called die > > > > And I can post the > /var/log/portage/cross-arm-softfloat-linux-gnu-info.log too, if it would > do any good. > > Thanks in advance. > --Jeff Cunningham

Next Message by Date: click to view message preview

Re: portage light?

On 7/4/07, Natanael Copa <natanael.copa-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote: I wonder if there is a way to filter out things in portage that you dont want. Like dev-dotnet, games-*, gnome-*, kde-*, x11-* Yes, there is. http://gentoo-wiki.com/TIP_Exclude_categories_from_emerge_sync

Previous Message by Thread: click to view message preview

Error building glibc for arm on AMD's?

I am new to this list. I'm hoping someone will be able to help me solve a problem building a toolchain for use with a 2.6 kernel on an arm9 board using crossdev. The issue is this: I can build a toolchain successfully on a Pentium 4 dual-core machine. But when I try to build the exact same toolchain on either of two AMD boxes it fails with the same error while building glibc. I looked through the archives of this mailing list without seeing anything relevant. I am hoping someone has seen this before and can tell me what I'm doing wrong. Here are the particulars: The toolchain in question will build with the following command: USE="-* nls glibc-omitfp nptl nptlonly tls" crossdev \ --b 2.16.1-r3 \ --g 4.1.1-r3 \ --k 2.6.19.2-r2 \ --l 2.3.6-r5 \ -t arm-softfloat-linux-gnu on the Intel P4 box is running Gentoo 2.6.18 (I don't know the revision number right now). But if fails on both of these: Athlon-xp box running Gentoo 2.6-19-r5 or 2.6-20-r8 Duron box running Gentoo 2.6.17-r4 Here is the error message for either of the AMD's: * Host Portage ARCH: x86 * Target Portage ARCH: arm * Target System: arm-softfloat-linux-gnu * Stage: 4 (C/C++ compiler) * binutils: binutils-2.16.1-r3 * gcc: gcc-4.1.1-r3 * headers: linux-headers-2.6.19.2-r2 * libc: glibc-2.3.6-r5 * PORTDIR_OVERLAY: /usr/local/portage * PORT_LOGDIR: /var/log/portage * PKGDIR: /usr/portage/packages/cross/arm-softfloat-linux-gnu * PORTAGE_TMPDIR: /var/tmp/cross/arm-softfloat-linux-gnu _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ * Forcing the latest versions of binutils-config/gcc-config ... [ ok ] * Log: /var/log/portage/cross-arm-softfloat-linux-gnu-binutils.log * Emerging cross-binutils ... [ ok ] * Log: /var/log/portage/cross-arm-softfloat-linux-gnu-gcc-stage1.log * Emerging cross-gcc-stage1 ... [ ok ] * Log: /var/log/portage/cross-arm-softfloat-linux-gnu-linux-headers.log * Emerging cross-linux-headers ... [ ok ] * Log: /var/log/portage/cross-arm-softfloat-linux-gnu-glibc.log * Emerging cross-glibc ... * glibc failed :( * If you file a bug, please attach the following logfiles: * /var/log/portage/cross-arm-softfloat-linux-gnu-info.log * /var/log/portage/cross-arm-softfloat-linux-gnu-glibc.log And here is the topmost build error in the glibc.log: gcc ../sysdeps/unix/sysv/linux/arm/sysdep.S -c -I../include -I. -I/var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softfloat-linux-gnu/glibc-2.3.6 -r5/work/build-default-arm-softfloat-linux-gnu-linuxthreads/csu -I.. -I../libio -I/var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softfloat-linux-gnu/glibc-2.3.6 -r5/work/build-default-arm-softfloat-linux-gnu-linuxthreads -I../sysdeps/arm/elf -I../linuxthreads/sysdeps/unix/sysv/linux/arm -I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/sysdeps/pthread -I../sysdeps/pthread -I../linuxthreads/sysdeps/unix/sysv -I../linuxthreads/sysdeps/unix -I../linuxthreads/sysdeps/arm -I../libidn/sysdeps/unix -I../sysdeps/unix/sysv/linux/arm -I../sysdeps/unix/sysv/linux -I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix/arm -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/arm -I../sysdeps/wordsize-32 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sysdeps/generic -nostdinc -isystem /usr/lib/gcc/i686-pc-linux-gnu/4.1.2/include -isystem /usr/arm-softfloat-linux-gnu/usr/include -D_LIBC_REENTRANT -include ../include/libc-symbols.h -DHAVE_INITFINI -DASSEMBLER -I/var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softfloat-linux-gnu/glibc-2.3.6 -r5/work/build-default-arm-softfloat-linux-gnu-linuxthreads/csu/. -Wa,--noexecstack -Wa,--noexecstack -o /var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softfloat-linux-gnu/glibc-2.3. 6-r5/work/build-default-arm-softfloat-linux-gnu-linuxthreads/csu/sysdep.o -MD -MP -MF /var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softfloat-linux-gnu/glibc-2.3 .6-r5/work/build-default-arm-softfloat-linux-gnu-linuxthreads/csu/sysdep.o.dt -MT /var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softfloat-linux-gnu/glibc-2.3 .6-r5/work/build-default-arm-softfloat-linux-gnu-linuxthreads/csu/sysdep.o ../sysdeps/generic/libc-start.c: In function '__libc_start_main': ../sysdeps/generic/libc-start.c:192: warning: implicit declaration of function '__guard_se tup' ../sysdeps/unix/sysv/linux/arm/sysdep.S: Assembler messages: ../sysdeps/unix/sysv/linux/arm/sysdep.S:31: Error: no such instruction: `rsb r0,r0,$0' ../sysdeps/unix/arm/sysdep.S:41: Error: invalid char '[' beginning operand 2 `[sp' ../sysdeps/unix/arm/sysdep.S:42: Error: invalid char '[' beginning operand 2 `[sp' ../sysdeps/unix/arm/sysdep.S:43: Error: no such instruction: `bl __errno_location(PLT)' ../sysdeps/unix/arm/sysdep.S:44: Error: no such instruction: `ldr r1,[sp],' ../sysdeps/unix/arm/sysdep.S:45: Error: invalid char '[' beginning operand 2 `[r0]' ../sysdeps/unix/arm/sysdep.S:46: Error: no such instruction: `mvn r0,$0' ../sysdeps/unix/arm/sysdep.S:47: Error: no such instruction: `ldr pc,[sp],' make[2]: *** [/var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softfloat-linux-gnu /glibc-2.3.6-r5/work/build-default-arm-softfloat-linux-gnu-linuxthreads/csu/sysdep.o] Erro r 1 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory `/var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softf loat-linux-gnu/glibc-2.3.6-r5/work/glibc-2.3.6/csu' make[1]: *** [csu/subdir_lib] Error 2 make[1]: Leaving directory `/var/tmp/cross/arm-softfloat-linux-gnu/portage/cross-arm-softf loat-linux-gnu/glibc-2.3.6-r5/work/glibc-2.3.6' make: *** [all] Error 2 !!! ERROR: cross-arm-softfloat-linux-gnu/glibc-2.3.6-r5 failed. Call stack: ebuild.sh, line 1615: Called dyn_compile ebuild.sh, line 972: Called qa_call 'src_compile' ebuild.sh, line 44: Called src_compile glibc-2.3.6-r5.ebuild, line 1127: Called src_compile glibc-2.3.6-r5.ebuild, line 1138: Called toolchain-glibc_src_compile glibc-2.3.6-r5.ebuild, line 221: Called die And I can post the /var/log/portage/cross-arm-softfloat-linux-gnu-info.log too, if it would do any good. Thanks in advance. --Jeff Cunningham

Next Message by Thread: click to view message preview

Re: portage light?

On 7/4/07, Natanael Copa <natanael.copa-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote: I wonder if there is a way to filter out things in portage that you dont want. Like dev-dotnet, games-*, gnome-*, kde-*, x11-* Yes, there is. http://gentoo-wiki.com/TIP_Exclude_categories_from_emerge_sync
Sign up for updates to this mailing list. email:
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by