Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Cross compiler x86->ppc
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC
View previous topic :: View next topic  
Author Message
BlueShift
Tux's lil' helper
Tux's lil' helper


Joined: 04 Jun 2002
Posts: 114
Location: Belgium

PostPosted: Thu Jun 17, 2004 8:36 am    Post subject: Cross compiler x86->ppc Reply with quote

Hi,

I just love my ibook (G3 600MHz), it's light, has a good screen and is more than powerfull enough for my needs. Except for 1 thing: keeping Gentoo up to date. emerge -u world can easliy take more than a day (Ok, I do this only once every couple of months)
Since I have a few more powerfull x86 systems around I thought it would be a good idea to build a cross compiler on these to compile the ppc code. If I can then somehow throw in distcc everything should go a lot faster.
After looking around at the forums I found the crossdev package. This contains a script that should take care of building all the necessary stuff.
On my ibook I have:
gcc: 3.3.3_pre20040408-r1
binutils: 2.14.90.0.6-r6
glibc: 2.3.3.20040420
linux-headers: 2.6.3-r1
So to build the cross compiler I would need to use
Code:
crossdev.sh --arch=ppc --clean --vbinutils=2.14.90.0.6-r6 --vgcc=3.3.3_pre20040408-r1 --vglibc=2.3.3.20040420 --vheaders=2.6.3-r1

However, this immediately crashes with the error message
Code:
 * Unpacking /usr/portage/sys-devel/binutils/binutils-2.14.90.0.6-r6.ebuild...
>>> md5 src_uri ;-) binutils-2.14.90.0.6.tar.bz2
/usr/sbin/ebuild.sh: line 1297: /var/db/pkg/sys-devel/binutils-2.14.90.0.6-r6/binutils-2.14.90.0.6-r6.ebuild: No such file or directory

!!! ERROR: sys-devel/binutils-2.14.90.0.6-r6 failed.
!!! Function , Line 1297, Exitcode 1
!!! error sourcing ebuild


 * doebuild(): Call to /usr/sbin/ebuild failed!

Why would it look for /var/db/pkg/sys-devel/binutils-2.14.90.0.6-r6/binutils-2.14.90.0.6-r6.ebuild ? The right path is obviously /usr/portage/sys-devel/binutils/binutils-2.14.90.0.6-r6.ebuild like it says 2 lines higher.
I suspect this is a bug in this binutils ebuild, but I'd rather ask here first. Furthermore, if I use --vbinutils=2.14.90.0.2 this step does work (while /var/db/pkg/sys-devel/binutils-2.14.90.0.2/binutils-2.14.90.0.2.ebuild does not exist either) (binutils-2.14.90.0.2 is another ppc-stable ebuild)
OK, so downgrading to
Code:
crossdev.sh --arch=ppc --clean --vbinutils=2.14.90.0.2 --vgcc=3.3.3_pre20040408-r1 --vglibc=2.3.3.20040420 --vheaders=2.6.3-r1

gets me 1 step futher. However, now the script crashes in Stage 2: Installing Kernel Headers:
Code:
*
* Cryptographic options
*
Cryptographic API (CRYPTO) [N/y/?] n
make: *** No rule to make target `symlinks'.  Stop.

 * InstallKernelHeaders(): Failed to create include/linux/version.h!

Another bug?
If I leave off the switch --vheaders it uses the linux-headers which are installed (linux-headers-2.4.21-r1)

So now we come to
Code:
crossdev.sh --arch=ppc --clean --vbinutils=2.14.90.0.2 --vgcc=3.3.3_pre20040408-r1 --vglibc=2.3.3.20040420

Here, Stage 2 and Stage 3 (Configure, Build, & Install binutils) work fine but we crash in Stage 4 (Configure, Build, & Install gcc-bootstrap):
Code:
/var/tmp/portage/crossdevbuild/gcc-3.3.3_pre20040408/buildboothere-ppc/gcc/xgcc -B/var/tmp/portage/crossdevbuild/gcc-3.3.3_pre20040408/buildboothere-ppc/gcc/ -B/home/crossdev/ppc/powerpc-unknown-linux-gnu/bin/ -B/home/crossdev/ppc/powerpc-unknown-linux-gnu/lib/ -isystem /home/crossdev/ppc/powerpc-unknown-linux-gnu/include -O2  -DIN_GCC -DCROSS_COMPILE   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -isystem ./include  -fPIC -g  -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I../../gcc -I../../gcc/. -I../../gcc/config -I../../gcc/../include  -DL_eprintf -c ../../gcc/libgcc2.c -o libgcc/./_eprintf.o
In file included from ../../gcc/unwind-dw2.c:26:
../../gcc/unwind-pe.h: In function `size_of_encoded_value':
../../gcc/unwind-pe.h:76: warning: implicit declaration of function `abort'
../../gcc/unwind-dw2.c: In function `extract_cie_info':
../../gcc/unwind-dw2.c:252: warning: implicit declaration of function `strlen'
../../gcc/unwind-dw2.c: In function `uw_frame_state_for':
../../gcc/unwind-dw2.c:933: warning: implicit declaration of function `memset'
../../gcc/unwind-dw2.c:947: error: structure has no member named `regs'
../../gcc/unwind-dw2.c:947: error: structure has no member named `regs'
../../gcc/unwind-dw2.c:947: error: structure has no member named `regs'
../../gcc/unwind-dw2.c:947: error: structure has no member named `regs'
../../gcc/unwind-dw2.c: In function `uw_install_context_1':
../../gcc/unwind-dw2.c:1244: warning: implicit declaration of function `memcpy'
make[2]: *** [libgcc/./unwind-dw2.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/var/tmp/portage/gcc-3.3.3_pre20040408-r1/work/gcc-20040408/buildboothere-ppc/gcc'
make[1]: *** [stmp-multilib] Error 2
make[1]: Leaving directory `/var/tmp/portage/gcc-3.3.3_pre20040408-r1/work/gcc-20040408/buildboothere-ppc/gcc'
make: *** [all-gcc] Error 2

 * InstallGccBootstrap(): Failed to compile!


In the end I found that
Code:
crossdev.sh --arch=ppc --clean --vbinutils=2.14.90.0.2 --vgcc=3.2.3-r4 --vglibc=2.3.1-r5
finishes with no errors, but then I have only a 3.2.3 gcc compiler and the versions of binutils and glibc don't match (don't know how much of a problem this would be). I did notice that programs compiled with gcc-3.3.3 feel a bit faster (subjective of course) and I think if I want to use distcc, I should at least use the same gcc version on all nodes (I didn't really get to that part yet)

So, if anybody here has ever tried this I would love to here about it. Does anybody have any suggestions on how to continue?
Many thanks for reading this far :-)

Jan.
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43553
Location: 56N 3W

PostPosted: Thu Jun 17, 2004 7:17 pm    Post subject: Reply with quote

BlueShift,

Try to find a script on the web that will do what you want.
It may not do the versions you need, however.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
_savage
Guru
Guru


Joined: 06 Jun 2004
Posts: 308
Location: Redmond, WA

PostPosted: Thu Jun 17, 2004 10:18 pm    Post subject: Reply with quote

i wouldn't rely on scripts in that case. if you want to build a cross compiler, then build it yourself ;) download gcc (whatever version you'd like to use) and the ./configure it with --target=powerpc. you also need to build the powerpc binutils.

- binutils in the version of your mac, ./configure --prefix=/wherever --target=G4 (or do you have a G3?)
- gcc, do the same.
- glibc, do the same (although you might not need glibc when you you link it dynamically on your mac, i think).

good luck,
jens :)
_________________
Jens Troeger
http://savage.light-speed.de/
Back to top
View user's profile Send private message
BlueShift
Tux's lil' helper
Tux's lil' helper


Joined: 04 Jun 2002
Posts: 114
Location: Belgium

PostPosted: Fri Jun 25, 2004 9:15 pm    Post subject: Reply with quote

OK, I have it working, I'll try to explain how I got it working, in case anybody else wants to give it a try.
A few days after (well, actually before, but I only saw it later) I posted the first message on this forum David Bélanger posted a howto on the gentoo-ppc-user mailing list. His can be found at http://www.sable.mcgill.ca/~dbelan2/crossdev-powerpc-i686.html. What he did is analyse the crossdev.sh script and do the same thing manually. At that time I was trying to hack the crossdev.sh script so the manualy stuff would be minimal.

First, I noticed I could not get crossdev to use linux-header for the 2.6 kernel. This is because the script uses 'make symlinks' on the kernel sources, which is no longer available in the 2.6 tree. To make this work, you need to change line 1158 of /usr/bin/crossdev.sh to
Code:
make ARCH="${KERNEL_ARCH}" include/asm include/linux/version.h || \


Next, in order to compile everything without any problems some changes need to be made to the source of gcc and glibc. I found it easiest to run the crossdev.sh script in 2 steps. First insert the line 'exit' on line 1056. If you then run
Code:
crossdev.sh --arch=ppc --vbinutils=2.14.90.0.6-r6 --vgcc=3.3.3_pre20040408-r1 --vglibc=2.3.3.20040420 --vheaders=2.6.7
It will unpack all sources and exit. Then we can make all necessary changes, remove the exit line and run crossdev.sh again. It will not overwrite your changes to the source directories.

Changes we need to make:
cd to /var/tmp/portage/gcc-3.3.3_pre20040408-r1/work/ you will see there's a directory gcc-20040408 Crossdev will expect this directory to be called gcc-3.3.3_pre20040408 I solved this by doing
Code:
ln -s /var/tmp/portage/gcc-3.3.3_pre20040408-r1/work/gcc-20040408 gcc-3.3.3_pre20040408
You need to specify the absolute path since this directory will be copied somewhere else so if you give a relative path this copy will point to nowhere. (Since it's all just temporary directories I decided not to worry about the deeper philosophical issues associated with crossdev.sh copying the symlink instead of actually making a copy of the files)
If we would try to compile gcc now it would fail on /var/tmp/portage/gcc-3.3.3_pre20040408-r1/work/gcc-20040408/gcc/unwind-dw2.c
Thanks to Davids howto I found out this can be solved by making a symlink from /home/crossdev/ppc/powerpc-unknown-linux-gnu/include to /home/crossdev/ppc/include
Code:

mkdir /home/crossdev
mkdir /home/crossdev/ppc/
mkdir /home/crossdev/ppc/include
mkdir /home/crossdev/ppc/powerpc-unknown-linux-gnu
cd /home/crossdev/ppc/powerpc-unknown-linux-gnu
ln -s ../include

Like David, I don't know if this the correct way of fixing it, but it sure is a lot cleaner than my original dirty hack (changing unwind-dw2.c so the offending line would never be compiled, which also works BTW)

Next we need to fix a problem with glibc. Here is a reference to the gcc_eh library which won't be available. It turns out this isn't necessary for a cross compiler (sorry, forgot to write down the page I found which explains this.)
Code:
cd /var/tmp/portage/glibc-2.3.3.20040420/work/glibc-2.3.2
vim Makeconfig

goto line 521 and change this section to this:
Code:
ifneq ($(have-as-needed),yes)
 libgcc_eh :=
else
 libgcc_eh := -Wl,--as-needed -lgcc_s -Wl,--no-as-needed
endif
ifneq ($(have-cc-with-libunwind),yes)
 gnulib := -lgcc $(libgcc_eh)
 static-gnulib := -lgcc $(libgcc_eh)
else
 gnulib := -lgcc $(libgcc_eh) -lunwind
 static-gnulib := -lgcc $(libgcc_eh) -lunwind
endif
(there's a diff on David Bélangers page)

Ok, that's it. Don't forget to remove the exit line from /usr/bin/crossdev.sh and rerun
Code:
crossdev.sh --arch=ppc --vbinutils=2.14.90.0.6-r6 --vgcc=3.3.3_pre20040408-r1 --vglibc=2.3.3.20040420 --vheaders=2.6.7


Have patience......
When the build finishes succesfully you should have your cross-compiler toolchain in /home/crossdev/ppc
Getting this to work with DISTCC is really easy: just install and configure distcc on both machines (there's an excelent documentation in the gentoo docs) and change the PATH in /etc/init.d/distcc on the x86 to
Code:
PATH="/home/crossdev/ppc/powerpc-unknown-linux-gnu/bin:${PATH}"

From now on you can just do
Code:
emerge some-package
on the mac and it will be distributed to the x86. I didn't need the CC=powerpc-unknown-linux-gnu CXX=powerpc-unknown-linux-gnu that are on David Bélangers page (in fact, it didn't work that way for me).

Believe me, mozilla compiles a lot faster on an ibook + AthlonXP1700 than on only an ibook. I've used this for a few day now and it seems to work perfectly. (but off course don't blame me if it happens to trash your system)

I also found this page by Benjamin Meyer. He recommends using unsermake (from KDE) in combination with distcc for even more speed. I plan to give this a try as well.

Voila, that's it, I hope this could be usefull for at least someone. If not, I'm still glad I wrote this down now that it's still fresh in my mind.

Greetings,

Jan.
Back to top
View user's profile Send private message
tomasino
Apprentice
Apprentice


Joined: 11 Feb 2004
Posts: 154
Location: Italy, Bologna

PostPosted: Sat Jun 26, 2004 8:53 am    Post subject: Reply with quote

very useful, I will try it after installing gentoo on my PIII (I was trying to have this working with debian on x86 machine, but it's much complicated, specially when compiling 3.3.3_pre20040408 return error :( )
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 43553
Location: 56N 3W

PostPosted: Sat Jun 26, 2004 11:03 am    Post subject: Reply with quote

BlueShift,

I'll see if this can be generalised to the ARM processor?
Did you submit your findings to the crossdev maintainer ?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
gongloo
n00b
n00b


Joined: 01 Nov 2002
Posts: 19
Location: Boston, MA, USA

PostPosted: Sat Jul 17, 2004 3:38 pm    Post subject: Reply with quote

I am currently in the same endeavour with my powerbook G4 and a P4. I had everything set up already using crossdev, but this was back in the days of gcc 3.2 -- I upgraded gcc to 3.3 on my powerbook, and compiles started to break when using distcc, on linking to core gcc functions (they apparently removed some core, everyday functions in the new gcc). I quickly remembered I had not updated gcc on the P4 crossdev chain, and determined that this was the culprit.

I am following the guide posted above, and have already run into an issue: crossdev.sh looks for a linux-headers ebuild, and found none for 2.6. This is because the 2.6 headers were moved to sys-kernel/linux26-headers. I made the following change on line 57 in /usr/bin/crossdev.sh to correct this, and this allowed me at least to extract everything properly:

Code:
HEADERS_LOC="sys-kernel/linux26-headers"


Just thought I'd contribute that right away. I will pitch in more if/when i run in to and solve more problems.

--EDIT: 2004.07.17 12:36 GMT-5--

I'm having compile problems with compiling glibc. Undefined references to '--fixsfdi', specifically in the math build directory, while linking libm.so. I have been unable to solve them.

Code:

: /var/tmp/portage/crossdevbuild/glibc-2.3.2/buildhere-ppc/math/libm.a
/var/tmp/portage/crossdevbuild/glibc-2.3.2/buildhere-ppc/math/libm_pic.a(s_llrint.os)(.text+0x10): In function `__llrint':
../sysdeps/powerpc/powerpc32/fpu/s_llrint.c:25: undefined reference to `__fixdfdi'
/var/tmp/portage/crossdevbuild/glibc-2.3.2/buildhere-ppc/math/libm_pic.a(s_llround.os)(.text+0x20): In function `__llround':
../sysdeps/powerpc/fpu/s_llround.c:33: undefined reference to `__fixdfdi'
/var/tmp/portage/crossdevbuild/glibc-2.3.2/buildhere-ppc/math/libm_pic.a(s_llround.os)(.text+0x24):../sysdeps/powerpc/fpu/s_llround.c:34: undefined reference to `__floatdidf'
/var/tmp/portage/crossdevbuild/glibc-2.3.2/buildhere-ppc/math/libm_pic.a(s_llround.os)(.text+0x58):../sysdeps/powerpc/fpu/s_llround.c:44: undefined reference to `__fixdfdi'
/var/tmp/portage/crossdevbuild/glibc-2.3.2/buildhere-ppc/math/libm_pic.a(s_llrintf.os)(.text+0x10): In function `__llrintf':
../sysdeps/powerpc/powerpc32/fpu/s_llrintf.c:25: undefined reference to `__fixsfdi'
/var/tmp/portage/crossdevbuild/glibc-2.3.2/buildhere-ppc/math/libm_pic.a(s_llroundf.os)(.text+0x20): In function `__llroundf':
../sysdeps/powerpc/fpu/s_llroundf.c:33: undefined reference to `__fixsfdi'
/var/tmp/portage/crossdevbuild/glibc-2.3.2/buildhere-ppc/math/libm_pic.a(s_llroundf.os)(.text+0x24):../sysdeps/powerpc/fpu/s_llroundf.c:34: undefined reference to `__floatdisf'
/var/tmp/portage/crossdevbuild/glibc-2.3.2/buildhere-ppc/math/libm_pic.a(s_llroundf.os)(.text+0x58):../sysdeps/powerpc/fpu/s_llroundf.c:44: undefined reference to `__fixsfdi'
collect2: ld returned 1 exit status
Back to top
View user's profile Send private message
yther
Apprentice
Apprentice


Joined: 25 Oct 2002
Posts: 151
Location: Charlotte, NC (USA)

PostPosted: Mon Jul 26, 2004 2:24 am    Post subject: Crossdev fails on i686 -> ppc Reply with quote

I'm having the exact same failure as gongloo above. I'm trying to build the toolchain on a dual P3, and following this procedure I got farther than ever before, but now I'm stuck with the missing references to __fixxxx as well.

My Mac and I are on kernel 2.4, and here's what it's trying to install:
Code:
sys-kernel/linux-headers-2.4.22
sys-devel/binutils-2.15.90.0.3-r3
sys-devel/gcc-3.3.3_pre20040408-r1
sys-libs/glibc-2.3.3.20040420


If someone knows how to get over this new speed bump, I'd like to hear about it!
Back to top
View user's profile Send private message
jon_vas
n00b
n00b


Joined: 14 May 2004
Posts: 37
Location: somewhere

PostPosted: Fri Aug 06, 2004 3:02 pm    Post subject: Reply with quote

hi. couple of questions. i am trying to compile from a i686 to a powerpc(dreambox). do i need distcc to compile? can't i just compile the file on the i686 and copy it to the powerpc?
Back to top
View user's profile Send private message
BlueShift
Tux's lil' helper
Tux's lil' helper


Joined: 04 Jun 2002
Posts: 114
Location: Belgium

PostPosted: Fri Aug 06, 2004 9:39 pm    Post subject: Reply with quote

jon_vas wrote:
hi. couple of questions. i am trying to compile from a i686 to a powerpc(dreambox). do i need distcc to compile? can't i just compile the file on the i686 and copy it to the powerpc?

If just want to compile simple programs you can indeed compile on the x86 and transfer to the ppc. distcc is just handy to use in combination with portage: it will transparantly outsource the compilation to one or more other boxes and you don't have to transfer anything manually.

Jan.
Back to top
View user's profile Send private message
john36
Tux's lil' helper
Tux's lil' helper


Joined: 16 Jul 2002
Posts: 141
Location: Boston

PostPosted: Sun Sep 05, 2004 2:56 pm    Post subject: Reply with quote

Yikes, well I am stuck.

I first tried the manual method. The beginning was easy, but I couldnt get glibc to compile.
It told me it couldnt find the linux headers.
Quote:

running configure fragment for sysdeps/powerpc/powerpc32/elf
running configure fragment for sysdeps/pthread
running configure fragment for sysdeps/unix/sysv/linux
checking for egrep... (cached) grep -E
checking installed Linux kernel header files... TOO OLD!

But I am darn certain I had them specified correctly, I even put some echo commands in the configure script to test

--with-headers="${CROSS_INSTALL}/include
and
CROSS_INSTALL="/home/crossdev"
were in my configure script.

OK, after not solving this problem, I decided to run the crossdev script.

This too fails. It wont get past binutils.
Quote:

configure: error: source directory already configured; run make distclean there first

make: *** [configure binutils] Error 1

InstallBinutils() Failed to compile!

Any ideas?
I tried deleting the /var/tmp/portage/binutils directory and tried again, but same error

I am attempting to set up

gcc-3.3.3_pre20040408-r1
binutils-2.14.90.0.6-r6
glibc-2.3.3.20040420-r1
linuxheaders-2.4.22

It's going on a PIII laptop with a 2.4.21 kernel.
Back to top
View user's profile Send private message
john36
Tux's lil' helper
Tux's lil' helper


Joined: 16 Jul 2002
Posts: 141
Location: Boston

PostPosted: Tue Sep 07, 2004 5:28 pm    Post subject: Reply with quote

Well, I wrote an email to David Bélanger and he sent me a reply.
I changed one line in my linux-headers script
(and cleaned up a lot of typos elsewhere)
and got it too work.

Thanks you.

David said he was working on an update, which I would suggest all curious hackers should watch out for.



I have two more questions for everyone.

1. What flags can be used? I just used the standard "-O2 -g". Has anyone tried more of them?
Has anyone tried altivec?

2. I don't want to use distcc. I would like to do all my PPC compilation on my x86 box, build the package there, and then samba it over to my PPC box.
(My x86 is a laptop and spends most of it's life disconnected from the PPC )

Anyone know how to do that?
Back to top
View user's profile Send private message
iTux
Guru
Guru


Joined: 07 Sep 2004
Posts: 586
Location: Toronto

PostPosted: Wed Sep 08, 2004 7:16 pm    Post subject: Reply with quote

john36 wrote:

David said he was working on an update, which I would suggest all curious hackers should watch out for.


I managed to get a newer cross-compiler working. I updated my doc: http://www.sable.mcgill.ca/~dbelan2/crossdev/crossdev-powerpc-i686.html

john36 wrote:

1. What flags can be used? I just used the standard "-O2 -g". Has anyone tried more of them?
Has anyone tried altivec?


I successfully build the toolchain with my usual flags:
CROSS_CFLAGS="-O3 -mcpu=750 -pipe"
MY_CFLAGS="-O2 -pipe -march=i686 -fomit-frame-pointer"

john36 wrote:

2. I don't want to use distcc. I would like to do all my PPC compilation on my x86 box, build the package there, and then samba it over to my PPC box.
(My x86 is a laptop and spends most of it's life disconnected from the PPC )


If you use distcc, it will be a lot simpler...

The linking occurs on the client (machine where emerge is run) and I think the headers are preprocessed there.

That means, you don't need to have the libs required for compilation installed on the distcc servers.

For cross-compilation, this means, you do not need to have a version of all powerpc libs compiled on the servers...

David "iTux" Bélanger
Back to top
View user's profile Send private message
iTux
Guru
Guru


Joined: 07 Sep 2004
Posts: 586
Location: Toronto

PostPosted: Wed Sep 08, 2004 7:23 pm    Post subject: Re: Crossdev fails on i686 -> ppc Reply with quote

yther wrote:
I'm having the exact same failure as gongloo above. I'm trying to build the toolchain on a dual P3, and following this procedure I got farther than ever before, but now I'm stuck with the missing references to __fixxxx as well.


For glibc, try using:
CC="${CROSS_CHOST}-gcc ${CROSS_CFLAGS}"
instead of the:
CC="${CROSS_CHOST}-gcc -O2 -nostdlib -nostartfiles ${CROSS_CFLAGS}"
that is in the crossdev script.

where:
CROSS_CHOST=powerpc-unknown-linux-gnu

CROSS_CFLAGS="-O3 -mcpu=750 -pipe" for a G3 or
CROSS_CFLAGS="-O2 -pipe" if unsure of what to use.

iTux
Back to top
View user's profile Send private message
secondshadow
Guru
Guru


Joined: 23 Jun 2003
Posts: 362

PostPosted: Fri Nov 12, 2004 7:50 am    Post subject: Reply with quote

well, I'd like to say, first off, that I found this thread incredably helpfull in getting my ppc cross-compiler working. Secondly, I'd like to share an idea I had for getting multiple cross-compilers working with distcc, which can be found here:

https://forums.gentoo.org/viewtopic.php?p=1754321#1754321
Back to top
View user's profile Send private message
iTux
Guru
Guru


Joined: 07 Sep 2004
Posts: 586
Location: Toronto

PostPosted: Sat Nov 13, 2004 3:03 am    Post subject: Reply with quote

Hi,

And for people interested to have ebuilds for building a cross-compiler toolchain:

https://forums.gentoo.org/viewtopic.php?p=1757576

iTux
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on PPC 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