| To: | <unlisted-recipients:>, <no To-header on input>, "IMB Recipient 1" <mspop3connector.david.sanchez@lexbox.fr> |
|---|---|
| Subject: | RE: mips64 crosstool |
| From: | "Bryan Althouse" <bryan.althouse@3phoenix.com> |
| Date: | Mon, 18 Jul 2005 21:00:26 +0200 |
| Cc: | "'Linux/MIPS Development'" <linux-mips@linux-mips.org> |
| Delivered-to: | lexbox.fr-david.sanchez@lexbox.fr |
| Importance: | normal |
| In-reply-to: | <6097c4905071221414a929ed2@mail.gmail.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| Priority: | normal |
| Sender: | linux-mips-bounce@linux-mips.org |
| Thread-index: | AcWHZSfad2BSW7ZHSgK2kHba95oicQEYtSEA |
Many thanks to everyone who has helped me on this issue. I ended up abandoning the crosstool approach. It supports mips32 well, but not mips64. Linux from scratch has a very good step by step procedure for building a tool chain for mips64. I was able to build with very little headaches. Unfortunately, I have not yet been able to execute any programs compiled with the tool chain. I'm not sure where I went wrong. PMC sierra is working on an update for their tool chain. They have supplied me with a "beta" version tool chain that has solved my problems. Now, I am able to compile with -mabi=64 and -lpthread. The executable no longer Segfaults. Since I'm past this problem, I will probably not spend much more time trying to build a working tool chain. Bryan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | RE: mips64 crosstool, Bryan Althouse |
|---|---|
| Next by Date: | Linux 2.6.11.5 on R3912 problems, Mark Underwood |
| Previous by Thread: | RE: mips64 crosstool, Bryan Althouse |
| Next by Thread: | elf_core_dump() from binfmt_elfo32.c trashes heap, Dave Johnson |
| Indexes: | [Date] [Thread] [Top] [All Lists] |