egcs and binutils cross compiling
Quoted 9 lines
Okay, I've finished packaging the following:
- an update on binutils to bring it to 2.9.1
- egcsIt looks like it might work, but to be honest it's difficult to tell at this point. At least it will be a starting point.
I think most of you are using Mklinux as the crosscompiler host. Has anyone tried building the cross compiler from HP-UX? This will probably have to be my build system since Mklinux doesn't work for me. jason.
----------------------------------------------------------------------
To unsubscribe: send e-mail to [email protected] with `unsubscribe' as the subject.
Quoted 4 lines · Jason Eckhardt
I think most of you are using Mklinux as the crosscompiler host. Has anyone tried building the cross compiler from HP-UX? This will probably have to be my build system since Mklinux doesn't work for me. jason.
My primary non-native build environment for the forseeable future is my PII 400 (i386 family) running Red Hat Linux, for which these packages were intended. That may change.
Well, I'm certainly not against having hpux based cross compilers, and they shouldn't be that difficult to do. I might have a look at it myself, although I'm not sure if the 735 I have has CC or gcc on it.
Certainly, though, I'd entertain distributing binaries for cross compiling egcs and binutils with host=hppa1.1-hp-hpux target=hppa1.1-hp-linux. All the parts are there.
Normally I'd say that it's easy to build it yourself, but building cross compilers tends to be a real pain.
Also, Paul is changing the ELF header structure significantly between mklinux and *real* linux, so we're getting close to having to just abandon all of mklinux.
- Alex
----------------------------------------------------------------------
To unsubscribe: send e-mail to [email protected] with `unsubscribe' as the subject.
Quoted 3 lines
Also, Paul is changing the ELF header structure significantly between mklinux and *real* linux, so we're getting close to having to just abandon all of mklinux.
Write an mklinux binary loader bfore you do that. Having a mostly functional user space while doing kernel hacks, and being able to use mklinux to mend the result of failed native kernels is a large win
----------------------------------------------------------------------
To unsubscribe: send e-mail to [email protected] with `unsubscribe' as the subject.
Quoted 8 lines · Alan Cox
Quoted 4 lines
Also, Paul is changing the ELF header structure significantly between mklinux and *real* linux, so we're getting close to having to just abandon all of mklinux.
Write an mklinux binary loader bfore you do that. Having a mostly functional user space while doing kernel hacks, and being able to use mklinux to mend the result of failed native kernels is a large win
The current idea is that we will make the kernel data structures as
close to HP-UX as possible so future HP-UX compatibility is possible. If we go the MkLinux binary loader route then we'll be stuck making our kernel structures MkLinux like or writing an emulation layer. I'm no ELF expert, but at least the MkLinux stuff seems easy, the binary is mapped from beginning to end. Sections aren't mapped at different addresses (as other archs seem to do).
- Paul
----------------------------------------------------------------------
To unsubscribe: send e-mail to [email protected] with `unsubscribe' as the subject.