[Elua-svn] compiling the toolchain error
Locked
|
I'm trying the toolchain built from
http://fun-tech.se/stm32/gcc/index.php with the libgloss thing in the newlib configure.ac (target-libgloss) added.Everything builds ok but when I try to build elua from this weeks cvs I get this error./usr/local/stm32/lib/gcc/arm-none-eabi/4.4.4/thumb/libgcc.a(unwind-arm.o): In function `unwind_phase2': then a bunch of "unwind-arm.c:698: undefined reference to `abort" errors. Does anyone know what they are?? Everything seems to be built except the binaries. The cvs build using codesourcery if you uncomment the #ifdef FORSTM3210E_EVAL part in src/platform/stm32/platform_conf.h Thanks _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
Hi -
Just to clarify did eLua build before with the same toolchain or has your toolchain changed? I'm not familiar with this particular toolchain creation script. If you want to try my own toolchain builder, it should work on Ubuntu: https://github.com/jsnyder/arm-eabi-toolchain This should, in general, work with eLua. -jsnyder On Tue, Nov 23, 2010 at 1:35 PM, rogerb <[hidden email]> wrote: > I'm trying the toolchain built from > http://fun-tech.se/stm32/gcc/index.php with the libgloss > thing in the newlib configure.ac (target-libgloss) added.Everything > builds ok but when I try to build elua from this weeks cvs I get this > error./usr/local/stm32/lib/gcc/arm-none-eabi/4.4.4/thumb/libgcc.a(unwind-arm.o): > In function `unwind_phase2': then a bunch of "unwind-arm.c:698: > undefined reference to `abort" errors. Does anyone know what they are?? > Everything seems to be built except the binaries. > > The cvs build using codesourcery if you uncomment the > #ifdef FORSTM3210E_EVAL part in src/platform/stm32/platform_conf.h > Thanks > > _______________________________________________ > eLua-dev mailing list > [hidden email] > https://lists.berlios.de/mailman/listinfo/elua-dev > -- James Snyder Biomedical Engineering Northwestern University [hidden email] PGP: http://fanplastic.org/key.txt Phone: (847) 448-0386 _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
On Tue, 23 Nov 2010 14:32:38 -0600
James Snyder <[hidden email]> wrote: > Hi - > > Just to clarify did eLua build before with the same toolchain or has > your toolchain changed? I'm not familiar with this particular > toolchain creation script. > I was using codesourcery and it build ok but I thought i would try the build script at http://fun-tech.se/stm32/gcc/index.php It builds the toolchain ok but when I compile elua it gets as far as building all the object files but fails in the linker stage. It's very close to the build stuff on the elua website but with insight and gdb and it has the gcc patch. I'll enclose the error text > If you want to try my own toolchain builder, it should work on Ubuntu: > https://github.com/jsnyder/arm-eabi-toolchain > > This should, in general, work with eLua. > > -jsnyder > > On Tue, Nov 23, 2010 at 1:35 PM, rogerb <[hidden email]> wrote: > > I'm trying the toolchain built from > > http://fun-tech.se/stm32/gcc/index.php with the libgloss > > thing in the newlib configure.ac (target-libgloss) added.Everything > > builds ok but when I try to build elua from this weeks cvs I get > > this > > error./usr/local/stm32/lib/gcc/arm-none-eabi/4.4.4/thumb/libgcc.a(unwind-arm.o): > > In function `unwind_phase2': then a bunch of "unwind-arm.c:698: > > undefined reference to `abort" errors. Does anyone know what they > > are?? Everything seems to be built except the binaries. > > > > The cvs build using codesourcery if you uncomment the > > #ifdef FORSTM3210E_EVAL part in src/platform/stm32/platform_conf.h > > Thanks > > > > _______________________________________________ > > eLua-dev mailing list > > [hidden email] > > https://lists.berlios.de/mailman/listinfo/elua-dev > > > > > _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
error.txt (1K) |
|
Try add this somewhere (for example in main.c):
void abort(void) { while( 1 ); } Kind of weird that it doesn't find this function though. Best, Bogdan On Tue, Nov 23, 2010 at 11:30 PM, rogerb <[hidden email]> wrote: > On Tue, 23 Nov 2010 14:32:38 -0600 > James Snyder <[hidden email]> wrote: > >> Hi - >> >> Just to clarify did eLua build before with the same toolchain or has >> your toolchain changed? I'm not familiar with this particular >> toolchain creation script. >> > I was using codesourcery and it build ok but I thought i would try the > build script at http://fun-tech.se/stm32/gcc/index.php It builds the > toolchain ok but when I compile elua it gets as far as building all the > object files but fails in the linker stage. > It's very close to the build stuff on the elua website but with insight > and gdb and it has the gcc patch. I'll enclose the error text > >> If you want to try my own toolchain builder, it should work on Ubuntu: >> https://github.com/jsnyder/arm-eabi-toolchain >> >> This should, in general, work with eLua. >> >> -jsnyder >> >> On Tue, Nov 23, 2010 at 1:35 PM, rogerb <[hidden email]> wrote: >> > I'm trying the toolchain built from >> > http://fun-tech.se/stm32/gcc/index.php with the libgloss >> > thing in the newlib configure.ac (target-libgloss) added.Everything >> > builds ok but when I try to build elua from this weeks cvs I get >> > this >> > error./usr/local/stm32/lib/gcc/arm-none-eabi/4.4.4/thumb/libgcc.a(unwind-arm.o): >> > In function `unwind_phase2': then a bunch of "unwind-arm.c:698: >> > undefined reference to `abort" errors. Does anyone know what they >> > are?? Everything seems to be built except the binaries. >> > >> > The cvs build using codesourcery if you uncomment the >> > #ifdef FORSTM3210E_EVAL part in src/platform/stm32/platform_conf.h >> > Thanks >> > >> > _______________________________________________ >> > eLua-dev mailing list >> > [hidden email] >> > https://lists.berlios.de/mailman/listinfo/elua-dev >> > >> >> >> > > _______________________________________________ > eLua-dev mailing list > [hidden email] > https://lists.berlios.de/mailman/listinfo/elua-dev > > eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
On Tue, 23 Nov 2010 23:33:07 +0200
Bogdan Marinescu <[hidden email]> wrote: > Try add this somewhere (for example in main.c): > > void abort(void) > { > while( 1 ); > } > > Kind of weird that it doesn't find this function though. > Added it to main.c and it worked thanks a lot > Best, > Bogdan > > On Tue, Nov 23, 2010 at 11:30 PM, rogerb <[hidden email]> wrote: > > On Tue, 23 Nov 2010 14:32:38 -0600 > > James Snyder <[hidden email]> wrote: > > > >> Hi - > >> > >> Just to clarify did eLua build before with the same toolchain or > >> has your toolchain changed? I'm not familiar with this particular > >> toolchain creation script. > >> > > I was using codesourcery and it build ok but I thought i would try > > the build script at http://fun-tech.se/stm32/gcc/index.php It > > builds the toolchain ok but when I compile elua it gets as far as > > building all the object files but fails in the linker stage. > > It's very close to the build stuff on the elua website but with > > insight and gdb and it has the gcc patch. I'll enclose the error > > text > > > >> If you want to try my own toolchain builder, it should work on > >> Ubuntu: https://github.com/jsnyder/arm-eabi-toolchain > >> > >> This should, in general, work with eLua. > >> > >> -jsnyder > >> > >> On Tue, Nov 23, 2010 at 1:35 PM, rogerb <[hidden email]> wrote: > >> > I'm trying the toolchain built from > >> > http://fun-tech.se/stm32/gcc/index.php with the libgloss > >> > thing in the newlib configure.ac (target-libgloss) > >> > added.Everything builds ok but when I try to build elua from > >> > this weeks cvs I get this > >> > error./usr/local/stm32/lib/gcc/arm-none-eabi/4.4.4/thumb/libgcc.a(unwind-arm.o): > >> > In function `unwind_phase2': then a bunch of "unwind-arm.c:698: > >> > undefined reference to `abort" errors. Does anyone know what they > >> > are?? Everything seems to be built except the binaries. > >> > > >> > The cvs build using codesourcery if you uncomment the > >> > #ifdef FORSTM3210E_EVAL part in > >> > src/platform/stm32/platform_conf.h Thanks > >> > > >> > _______________________________________________ > >> > eLua-dev mailing list > >> > [hidden email] > >> > https://lists.berlios.de/mailman/listinfo/elua-dev > >> > > >> > >> > >> > > > > _______________________________________________ > > eLua-dev mailing list > > [hidden email] > > https://lists.berlios.de/mailman/listinfo/elua-dev > > > > > _______________________________________________ > eLua-dev mailing list > [hidden email] > https://lists.berlios.de/mailman/listinfo/elua-dev > _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
I don't know which library would usually provide that, it is a bit
strange that it's not finding it, but some of the major differences that can come up between the eLua website described toolchain build, my toolchain makefile and some of the other ones out there is whether or not certain libraries are included and whether or not newlib provides syscalls. Generally we don't want the newlib syscalls since we're providing our own. The syscalls newlib provides are mainly for debugging purposes, it might be that that build provides some version of a library that needs abort somewhere, but the library that includes abort isn't compiled in. eLua will often tend to expose these sorts of things where you might not have seen it with another project because we might be using a wider swath of C standard library plus system calls. On Tue, Nov 23, 2010 at 3:46 PM, rogerb <[hidden email]> wrote: > On Tue, 23 Nov 2010 23:33:07 +0200 > Bogdan Marinescu <[hidden email]> wrote: > >> Try add this somewhere (for example in main.c): >> >> void abort(void) >> { >> while( 1 ); >> } >> >> Kind of weird that it doesn't find this function though. >> > Added it to main.c and it worked thanks a lot >> Best, >> Bogdan >> >> On Tue, Nov 23, 2010 at 11:30 PM, rogerb <[hidden email]> wrote: >> > On Tue, 23 Nov 2010 14:32:38 -0600 >> > James Snyder <[hidden email]> wrote: >> > >> >> Hi - >> >> >> >> Just to clarify did eLua build before with the same toolchain or >> >> has your toolchain changed? I'm not familiar with this particular >> >> toolchain creation script. >> >> >> > I was using codesourcery and it build ok but I thought i would try >> > the build script at http://fun-tech.se/stm32/gcc/index.php It >> > builds the toolchain ok but when I compile elua it gets as far as >> > building all the object files but fails in the linker stage. >> > It's very close to the build stuff on the elua website but with >> > insight and gdb and it has the gcc patch. I'll enclose the error >> > text >> > >> >> If you want to try my own toolchain builder, it should work on >> >> Ubuntu: https://github.com/jsnyder/arm-eabi-toolchain >> >> >> >> This should, in general, work with eLua. >> >> >> >> -jsnyder >> >> >> >> On Tue, Nov 23, 2010 at 1:35 PM, rogerb <[hidden email]> wrote: >> >> > I'm trying the toolchain built from >> >> > http://fun-tech.se/stm32/gcc/index.php with the libgloss >> >> > thing in the newlib configure.ac (target-libgloss) >> >> > added.Everything builds ok but when I try to build elua from >> >> > this weeks cvs I get this >> >> > error./usr/local/stm32/lib/gcc/arm-none-eabi/4.4.4/thumb/libgcc.a(unwind-arm.o): >> >> > In function `unwind_phase2': then a bunch of "unwind-arm.c:698: >> >> > undefined reference to `abort" errors. Does anyone know what they >> >> > are?? Everything seems to be built except the binaries. >> >> > >> >> > The cvs build using codesourcery if you uncomment the >> >> > #ifdef FORSTM3210E_EVAL part in >> >> > src/platform/stm32/platform_conf.h Thanks >> >> > >> >> > _______________________________________________ >> >> > eLua-dev mailing list >> >> > [hidden email] >> >> > https://lists.berlios.de/mailman/listinfo/elua-dev >> >> > >> >> >> >> >> >> >> > >> > _______________________________________________ >> > eLua-dev mailing list >> > [hidden email] >> > https://lists.berlios.de/mailman/listinfo/elua-dev >> > >> > >> _______________________________________________ >> eLua-dev mailing list >> [hidden email] >> https://lists.berlios.de/mailman/listinfo/elua-dev >> > > _______________________________________________ > eLua-dev mailing list > [hidden email] > https://lists.berlios.de/mailman/listinfo/elua-dev > -- James Snyder Biomedical Engineering Northwestern University [hidden email] PGP: http://fanplastic.org/key.txt Phone: (847) 448-0386 _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
On Tue, 23 Nov 2010 17:37:19 -0600
James Snyder <[hidden email]> wrote: > I don't know which library would usually provide that, it is a bit > strange that it's not finding it, but some of the major differences > that can come up between the eLua website described toolchain build, > my toolchain makefile and some of the other ones out there is whether > or not certain libraries are included and whether or not newlib > provides syscalls. Generally we don't want the newlib syscalls since > we're providing our own. The syscalls newlib provides are mainly for > debugging purposes, it might be that that build provides some version > of a library that needs abort somewhere, but the library that includes > abort isn't compiled in. > > eLua will often tend to expose these sorts of things where you might > not have seen it with another project because we might be using a > wider swath of C standard library plus system calls. I think its libgloss In the build instructions on the elua site it shows were to modify the newlib configure.ac script but it turns out that when I rebuilt it the buildscript loads the old configure.ac. I added the changes to the tarball and gave it another go but it builds the same error stuff without the void abort() with it you get the code built but it hard faults after the elua prompt. I'll tweek the build script and check out what happens > > On Tue, Nov 23, 2010 at 3:46 PM, rogerb <[hidden email]> wrote: > > On Tue, 23 Nov 2010 23:33:07 +0200 > > Bogdan Marinescu <[hidden email]> wrote: > > > >> Try add this somewhere (for example in main.c): > >> > >> void abort(void) > >> { > >> while( 1 ); > >> } > >> > >> Kind of weird that it doesn't find this function though. > >> > > Added it to main.c and it worked thanks a lot > >> Best, > >> Bogdan > >> > >> On Tue, Nov 23, 2010 at 11:30 PM, rogerb <[hidden email]> wrote: > >> > On Tue, 23 Nov 2010 14:32:38 -0600 > >> > James Snyder <[hidden email]> wrote: > >> > > >> >> Hi - > >> >> > >> >> Just to clarify did eLua build before with the same toolchain or > >> >> has your toolchain changed? I'm not familiar with this > >> >> particular toolchain creation script. > >> >> > >> > I was using codesourcery and it build ok but I thought i would > >> > try the build script at http://fun-tech.se/stm32/gcc/index.php It > >> > builds the toolchain ok but when I compile elua it gets as far as > >> > building all the object files but fails in the linker stage. > >> > It's very close to the build stuff on the elua website but with > >> > insight and gdb and it has the gcc patch. I'll enclose the error > >> > text > >> > > >> >> If you want to try my own toolchain builder, it should work on > >> >> Ubuntu: https://github.com/jsnyder/arm-eabi-toolchain > >> >> > >> >> This should, in general, work with eLua. > >> >> > >> >> -jsnyder > >> >> > >> >> On Tue, Nov 23, 2010 at 1:35 PM, rogerb <[hidden email]> wrote: > >> >> > I'm trying the toolchain built from > >> >> > http://fun-tech.se/stm32/gcc/index.php with the libgloss > >> >> > thing in the newlib configure.ac (target-libgloss) > >> >> > added.Everything builds ok but when I try to build elua from > >> >> > this weeks cvs I get this > >> >> > error./usr/local/stm32/lib/gcc/arm-none-eabi/4.4.4/thumb/libgcc.a(unwind-arm.o): > >> >> > In function `unwind_phase2': then a bunch of > >> >> > "unwind-arm.c:698: undefined reference to `abort" errors. > >> >> > Does anyone know what they are?? Everything seems to be built > >> >> > except the binaries. > >> >> > > >> >> > The cvs build using codesourcery if you uncomment the > >> >> > #ifdef FORSTM3210E_EVAL part in > >> >> > src/platform/stm32/platform_conf.h Thanks > >> >> > > >> >> > _______________________________________________ > >> >> > eLua-dev mailing list > >> >> > [hidden email] > >> >> > https://lists.berlios.de/mailman/listinfo/elua-dev > >> >> > > >> >> > >> >> > >> >> > >> > > >> > _______________________________________________ > >> > eLua-dev mailing list > >> > [hidden email] > >> > https://lists.berlios.de/mailman/listinfo/elua-dev > >> > > >> > > >> _______________________________________________ > >> eLua-dev mailing list > >> [hidden email] > >> https://lists.berlios.de/mailman/listinfo/elua-dev > >> > > > > _______________________________________________ > > eLua-dev mailing list > > [hidden email] > > https://lists.berlios.de/mailman/listinfo/elua-dev > > > > > _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
 
|
Martin Guy |
Re: [Elua-svn] compiling the toolchain error
|
|
Hi
The main repository of net wisdom in bulding cross toolchains is the crosstool-ng project at http://ymorin.is-a-geek.org/projects/crosstool I'd suggest using that and, if there are patches to add, contributing them at their list: [hidden email] The maintainer is very responsive to input from developers, and consequently the resulting toolchain quality is high and up to date. M _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
On Wed, 24 Nov 2010 13:32:33 +0100
Martin Guy <[hidden email]> wrote: > Hi > The main repository of net wisdom in bulding cross toolchains is > the crosstool-ng project at > http://ymorin.is-a-geek.org/projects/crosstool I'll check it out thanks > I'd suggest using that and, if there are patches to add, > contributing them at their list: [hidden email] > The maintainer is very responsive to input from developers, and > consequently the resulting toolchain quality is high and up to date. > > M > _______________________________________________ > eLua-dev mailing list > [hidden email] > https://lists.berlios.de/mailman/listinfo/elua-dev > _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
In reply to this post by Martin Guy
I've looked into playing with this toolchain builder a few times and I
have no doubt that it works pretty well. One thing that is generally a pain and crosstool avoids is building multilib (http://ymorin.is-a-geek.org/projects/crosstool#multilib). CodeSourcery's maintained version of GCC actually makes it pretty easy to build a single cross-compiling toolchain that builds for ARM, Thumb and Thumb2. I also like using their releases because they are the official maintainers of the ARM (and ColdFire) GCC ports so they tend to include their own upstream patches that might not get integrated into GCC and Newlib until the next release cycle. Perhaps one of these days I'll try integrating my own recipe into the crosstool framework, but I've not gotten around to it. CodeSourcery also provides pre-built versions of their toolchain here for 32-bit Windows & Linux (should work on 64-bit variants of either, including Linux if you have the appropriate ia32-libs or similar package): http://www.codesourcery.com/sgpp/lite/arm/portal/release1592 I also have pre-built versions of CodeSourcery for 64-bit linux and Mac OS X here: https://github.com/jsnyder/arm-eabi-toolchain/downloads (right now this is from the gcc 4.4 sources, I've got a 4.5 version based on the last CS release in a branch, but I haven't had time to fully test it yet) On Wed, Nov 24, 2010 at 7:32 AM, Martin Guy <[hidden email]> wrote: > Hi > The main repository of net wisdom in bulding cross toolchains is > the crosstool-ng project at > http://ymorin.is-a-geek.org/projects/crosstool > I'd suggest using that and, if there are patches to add, > contributing them at their list: [hidden email] > The maintainer is very responsive to input from developers, and > consequently the resulting toolchain quality is high and up to date. > > M > _______________________________________________ > eLua-dev mailing list > [hidden email] > https://lists.berlios.de/mailman/listinfo/elua-dev > -- James Snyder Biomedical Engineering Northwestern University [hidden email] PGP: http://fanplastic.org/key.txt Phone: (847) 448-0386 _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
On Thu, 25 Nov 2010 17:33:24 -0500
James Snyder <[hidden email]> wrote: > I've looked into playing with this toolchain builder a few times and I > have no doubt that it works pretty well. One thing that is generally a > pain and crosstool avoids is building multilib > (http://ymorin.is-a-geek.org/projects/crosstool#multilib). > CodeSourcery's maintained version of GCC actually makes it pretty easy > to build a single cross-compiling toolchain that builds for ARM, Thumb > and Thumb2. I also like using their releases because they are the > official maintainers of the ARM (and ColdFire) GCC ports so they tend > to include their own upstream patches that might not get integrated > into GCC and Newlib until the next release cycle. > > Perhaps one of these days I'll try integrating my own recipe into the > crosstool framework, but I've not gotten around to it. > > CodeSourcery also provides pre-built versions of their toolchain here > for 32-bit Windows & Linux (should work on 64-bit variants of either, > including Linux if you have the appropriate ia32-libs or similar > package): > http://www.codesourcery.com/sgpp/lite/arm/portal/release1592 > but though I'd try build one just to get a bit of a feel for it. It seems a little hit and miss from version to version. If I can get some time next I'll work on it a bit more > I also have pre-built versions of CodeSourcery for 64-bit linux and > Mac OS X here: > https://github.com/jsnyder/arm-eabi-toolchain/downloads > (right now this is from the gcc 4.4 sources, I've got a 4.5 version > based on the last CS release in a branch, but I haven't had time to > fully test it yet) > > > On Wed, Nov 24, 2010 at 7:32 AM, Martin Guy <[hidden email]> > wrote: > > Hi > > The main repository of net wisdom in bulding cross toolchains is > > the crosstool-ng project at > > http://ymorin.is-a-geek.org/projects/crosstool > > I'd suggest using that and, if there are patches to add, > > contributing them at their list: [hidden email] > > The maintainer is very responsive to input from developers, and > > consequently the resulting toolchain quality is high and up to date. > > > > M > > _______________________________________________ > > eLua-dev mailing list > > [hidden email] > > https://lists.berlios.de/mailman/listinfo/elua-dev > > > > > _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
Martin Guy |
Re: [Elua-svn] compiling the toolchain error
|
|
On Fri, Nov 26, 2010 at 1:37 AM, rogerb <[hidden email]> wrote:
> I have been using the latest version of CodeSourcery for awhile now > but though I'd try build one just to get a bit of a feel for it. It > seems a little hit and miss from version to version. I've seen a lot of discussion on the net about "use this version of you want this to work, and that version if you want that to work. Don't use this version cos it's broken but this is my favourite version". Well, basically the same as the GCC releases :) but more so :) M _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
Yep. They're all from the same stock, but with minor variations.
Most of these don't matter in most cases, especially if you dont mind having separate toolchains for different ARM instruction sets. They all also certainly have bugs as well :-) For the most part we should work on a variety of them since a number of us are working from various GCC versions and we have run into bugs present in one version or another that aren't present in others. We usually will work around these as necessary. If your toolchain doesn't work, definitely let us know so we can try and figure out whether it is our bug or not. Frequently if it's a GCC bug someone has already made a patch that just hasn't made it into a release that's available. tl;dr: If you have a working toolchain, just use it :-) If you want to learn about the pain an suffering involved in building toolchains, there are more than enough guides out there and some of them will probably work :-) On Sat, Nov 27, 2010 at 8:09 AM, Martin Guy <[hidden email]> wrote: > On Fri, Nov 26, 2010 at 1:37 AM, rogerb <[hidden email]> wrote: >> I have been using the latest version of CodeSourcery for awhile now >> but though I'd try build one just to get a bit of a feel for it. It >> seems a little hit and miss from version to version. > > I've seen a lot of discussion on the net about "use this version of > you want this to work, and that version if you want that to work. > Don't use this version cos it's broken but this is my favourite > version". > > Well, basically the same as the GCC releases :) but more so :) > > M > _______________________________________________ > eLua-dev mailing list > [hidden email] > https://lists.berlios.de/mailman/listinfo/elua-dev > -- James Snyder Biomedical Engineering Northwestern University [hidden email] PGP: http://fanplastic.org/key.txt Phone: (847) 448-0386 _______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
> tl;dr: If you have a working toolchain, just use it :-) If you want
> to learn about the pain an suffering involved in building toolchains, > there are more than enough guides out there and some of them will > probably work :-) Amen to that. The only reason that made me look at building toolchains in the first place was that a few years ago (when I started working with Cortex) there's wan't really a good toolchain available, so I had to improvise. Now I have CodeSourcery and I'm not even trying to build other toolchain. Life is simply too short for that :) Best, Bogdan > > On Sat, Nov 27, 2010 at 8:09 AM, Martin Guy <[hidden email]> wrote: >> On Fri, Nov 26, 2010 at 1:37 AM, rogerb <[hidden email]> wrote: >>> I have been using the latest version of CodeSourcery for awhile now >>> but though I'd try build one just to get a bit of a feel for it. It >>> seems a little hit and miss from version to version. >> >> I've seen a lot of discussion on the net about "use this version of >> you want this to work, and that version if you want that to work. >> Don't use this version cos it's broken but this is my favourite >> version". >> >> Well, basically the same as the GCC releases :) but more so :) >> >> M >> _______________________________________________ >> eLua-dev mailing list >> [hidden email] >> https://lists.berlios.de/mailman/listinfo/elua-dev >> > > > > -- > James Snyder > Biomedical Engineering > Northwestern University > [hidden email] > PGP: http://fanplastic.org/key.txt > Phone: (847) 448-0386 > _______________________________________________ > eLua-dev mailing list > [hidden email] > https://lists.berlios.de/mailman/listinfo/elua-dev > eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
|
|
Dado Sutter |
Re: [Elua-svn] compiling the toolchain error
|
|
On Sat, Nov 27, 2010 at 15:48, Bogdan Marinescu <[hidden email]> wrote:
.... and it almost turned our little project and list into a Toolchain Building one :) At that time it was really hard to find one that worked 100% and yours was the first one I could use for Thumb mode. Now I have CodeSourcery and I'm not even trying to build Agreed :) CodeSourcery has been giving good results downhere too and it's by far the easiest to install on the main OSs. But we'll be glad to keep the toolchain building tutorials on the site, if we get enough help to keep them up to date. They seem to be useful for other users too. Thanks for the help. Best, Best Dado
_______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev |
«
Return to eLua Development
|
1 view|%1 views
| Free forum by Nabble | Edit this page |