| View previous topic :: View next topic |
| Author |
Message |
ddc
Guru
Joined: 29 Aug 2006
Posts: 525
|
 Posted: Sun Dec 14, 2008 12:38 pm Post subject: crossdev -t mips (host=ppc) |
 |
|
crossdev -C mips-linux-gnu
crossdev --target mips-linux-gnu
| Quote: |
--------------------------------------------------------------------------------
* Host Portage ARCH: ppc
* Target Portage ARCH: mips
* Target System: mips-linux-gnu
* Stage: 4 (C/C++ compiler)
* binutils: binutils-[latest]
* gcc: gcc-[latest]
* headers: linux-headers-[latest]
* libc: glibc-[latest]
* PORTDIR_OVERLAY: /usr/local/portage
* PORT_LOGDIR: /var/log/portage
* PKGDIR: /usr/portage/packages/cross/mips-linux-gnu
* PORTAGE_TMPDIR: /var/tmp/cross/mips-linux-gnu
_ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ -
* Forcing the latest versions of {binutils,gcc}-config/gnuconfig ... [ ok ]
* Log: /var/log/portage/cross-mips-linux-gnu-binutils.log
* Emerging cross-binutils ... [ ok ]
* Log: /var/log/portage/cross-mips-linux-gnu-linux-headers-quick.log
* Emerging cross-linux-headers-quick ... [ ok ]
* Log: /var/log/portage/cross-mips-linux-gnu-glibc-headers.log
* Emerging cross-glibc-headers ...
* glibc failed 
* If you file a bug, please attach the following logfiles:
* /var/log/portage/cross-mips-linux-gnu-info.log
* /var/log/portage/cross-mips-linux-gnu-glibc-headers.log
|
| Quote: |
./scripts/mkinstalldirs /var/tmp/cross/mips-linux-gnu/portage/cross-mips-linux-gnu/glibc-2.6.1/image//usr/mips-linux-gnu/usr/include/gnu
/bin/install -c -m 644 /var/tmp/cross/mips-linux-gnu/portage/cross-mips-linux-gnu/glibc-2.6.1/work/build-pos-mips-linux-gnu-headers/gnu/lib-names.h /var/tmp/cross/mips-linux-gnu/portage/cross-mips-linux-gnu/glibc-2.6.1/image//usr/mips-linux-gnu/usr/include/gnu/lib-names.h
/bin/install: cannot stat `/var/tmp/cross/mips-linux-gnu/portage/cross-mips-linux-gnu/glibc-2.6.1/work/build-pos-mips-linux-gnu-headers/gnu/lib-names.h': No such file or directory
make[1]: *** [/var/tmp/cross/mips-linux-gnu/portage/cross-mips-linux-gnu/glibc-2.6.1/image//usr/mips-linux-gnu/usr/include/gnu/lib-names.h] Error 1
make[1]: Leaving directory `/var/tmp/cross/mips-linux-gnu/portage/cross-mips-linux-gnu/glibc-2.6.1/work/glibc-2.6.1'
make: *** [install-headers] Error 2
*
* ERROR: cross-mips-linux-gnu/glibc-2.6.1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_install
* environment, line 3838: Called eblit-run 'src_install' 'src_install'
* environment, line 1172: Called eblit-glibc-src_install
* src_install-2.6.eblit, line 221: Called toolchain-glibc_headers_install
* src_install-2.6.eblit, line 189: Called die
* The specific snippet of code:
* make install_root="${D}/usr/${CTARGET}" install-headers || die "install-headers failed"
* The die message:
* install-headers 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/cross/mips-linux-gnu/portage/cross-mips-linux-gnu/glibc-2.6.1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/cross/mips-linux-gnu/portage/cross-mips-linux-gnu/glibc-2.6.1/temp/environment'.
* This ebuild is from an overlay: '/usr/local/portage/'
*
* Messages for package cross-mips-linux-gnu/glibc-2.6.1:
*
* ERROR: cross-mips-linux-gnu/glibc-2.6.1 failed.
* Call stack:
* ebuild.sh, line 49: Called src_install
* environment, line 3838: Called eblit-run 'src_install' 'src_install'
* environment, line 1172: Called eblit-glibc-src_install
* src_install-2.6.eblit, line 221: Called toolchain-glibc_headers_install
* src_install-2.6.eblit, line 189: Called die
* The specific snippet of code:
* make install_root="${D}/usr/${CTARGET}" install-headers || die "install-headers failed"
* The die message:
* install-headers 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/cross/mips-linux-gnu/portage/cross-mips-linux-gnu/glibc-2.6.1/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/cross/mips-linux-gnu/portage/cross-mips-linux-gnu/glibc-2.6.1/temp/environment'.
* This ebuild is from an overlay: '/usr/local/portage/'
|
any idea ?
also, i have to crossdev -t mipsel-linux-gnu |
|
| Back to top |
|
 |
Pliablemammal
n00b
Joined: 02 Oct 2006
Posts: 52
Location: Sacramento
|
| Posted: Sun Dec 14, 2008 1:23 pm Post subject: |
|
|
What sort of mips machine are you building this for if you don't mind me asking? 
Also what is the output of (that's an "L")
_________________
Linux ps3-betabox 2.6.28-rc7-00948-gc5fd701 #5 SMP PREEMPT Sun Dec 14 18:25:40 PST 2008 ppc64 Cell Broadband Engine, altivec supported GNU/Linux - gcc version 4.4.0 20081212 (experimental) (GCC) Videos |
|
| Back to top |
|
|
ddc
Guru
Joined: 29 Aug 2006
Posts: 525
|
| Posted: Sun Dec 14, 2008 3:05 pm Post subject: |
|
|
| Pliablemammal wrote: | What sort of mips machine are you building this for if you don't mind me asking?
Also what is the output of (that's an "L") |
--target is mips_LittleEndian (32bit), so mipsle is OK for me
gcc-config -l
[1] hppa-unknown-linux-gnu-4.3.2 *
[2] mipsel-unknown-linux-gnu-4.3.2 *
[3] powerpc-unknown-linux-gnu-3.4.6
[4] powerpc-unknown-linux-gnu-4.1.2 *
unfortunately i get "glibc failed " error message forum crossdev |
|
| Back to top |
|
|
ddc
Guru
Joined: 29 Aug 2006
Posts: 525
|
|
| Back to top |
|
|
ddc
Guru
Joined: 29 Aug 2006
Posts: 525
|
| Posted: Tue Dec 16, 2008 2:38 pm Post subject: |
|
|
it seems crossdev is a pain in your ***
I'am using crosstools that has successfully built my dev chain!
(wandering why crossdev's guy make things so complicated) |
|
| Back to top |
|
|
roarinelk
Guru
Joined: 04 Mar 2004
Posts: 520
|
| Posted: Tue Dec 16, 2008 5:35 pm Post subject: |
|
|
| ddc wrote: | it seems crossdev is a pain in your ***
(wandering why crossdev's guy make things so complicated) |
It's not really crossdev's (or vapier's) fault; crossdev just sets up environment
variables so portage builds for the correct target. In my experience the
problem is in the source packages themselves.
(btw, binutils-2.19, gcc-4.3.2, glibc-2.9 build fine for mips cross and native
targets). |
|
| Back to top |
|
|
ddc
Guru
Joined: 29 Aug 2006
Posts: 525
|
| Posted: Tue Dec 16, 2008 8:06 pm Post subject: |
|
|
yes, but crossdev is too difficult to be understood in his internals !
I mean I'd like to apply a patch to gcc/binutils/*libc! and I'm not so able to understand how crossdev has to be modified !
also !
crossdev has no database of which is the rightest version of {glibc, header, binutils, gcc} for a certain target !
If the build fails, try various versions of binutils and gcc, it may be a little tinkering to get a combo that works.
crosstools has a database, so you can save yourself from sparing your time trying combo
Last edited by ddc on Tue Dec 16, 2008 9:30 pm; edited 1 time in total |
|
| Back to top |
|
|
ddc
Guru
Joined: 29 Aug 2006
Posts: 525
|
| Posted: Tue Dec 16, 2008 8:09 pm Post subject: |
|
|
| roarinelk wrote: | | glibc-2.9 |
glibc 2.9 ? ins't too experimental for ppc 2008 ?
I am integrating crosstool with the gentoo's stuff
also I am adding embedded target ( i mean no Operating System target)
example: mycrosscompiler --verbose --target m68hc11
(*) GCC cross-compiler build script
(*) host
(*) gcc =gcc-4.1.2
(*) binutils=binutils-2.18
(*) target
(*) gcc =gcc-3.0.4 with these pathes {}
(*) binutils=binutils-2.12.1 with these patches {}
(*) lib =newlib-1.10.0 with these patches {newlib-1.10.0.patch}
(*) script
(*) archive=tar.bz2
(*) builderOS=linux
(*) Checking for tool source in /src/crosstool/m68hc11
(*) Building m6811-elf cross toolset under linux and installing in /usr/crosstool/gcc-3.0.4-newlibc-1.10.0/m6811-elf
(*) Extracting binutils from archive... done
(*) patching...
(*) Extracting gcc-core and gcc-g++ from archive... done
(*) patching...
(*) Extracting newlib from archive... done
(*) patching... patching file libgloss/ChangeLog.M68HC11
(*) Removing unneeded languages (Java, chill, fortran, Objective C) and linking newlib to gcc: done
(*) Create a build directory: done
(*) Configuring binutils (for details see build/binutils-configure.log): done
(*) Building binutils (for details see build/binutils-make.log): done
(*) Installing binutils (for details see build/binutils-install.log): done
(*) Installing binutils-m6811-elf into /usr/local/bin: done
[!] Once we have a working binutils for our target we can build gcc and newlib together
(*) Configuring gcc and newlib (for details see build/gcc-newlib-configure.log): done
(*) Building gcc and newlib (for details see build/gcc-newlib-make.log): done |
|
| Back to top |
|
|
gringo
Advocate
Joined: 27 Apr 2003
Posts: 3793
|
| Posted: Wed Dec 17, 2008 12:05 pm Post subject: |
|
|
| Quote: | | I mean I'd like to apply a patch to gcc/binutils/*libc! and I'm not so able to understand how crossdev has to be modified ! |
no need to modify crossdev i think, create a customized ebuild and put it in the cross- directory that crossdev created for you in your local overlay.
Crossdev relies on portage after all.
| Quote: | crossdev has no database of which is the rightest version of {glibc, header, binutils, gcc} for a certain target !
If the build fails, try various versions of binutils and gcc, it may be a little tinkering to get a combo that works. |
yeah, i agree, finding a good combo takes quite some time.
| Quote: | I am integrating crosstool with the gentoo's stuff
also I am adding embedded target ( i mean no Operating System target) |
cool, maybe you want to contact Vapier to get some help !
cheers
_________________
Error: Failing not supported by current locale |
|
| Back to top |
|
|
|
Gentoo on Alternative Architectures
