This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
Ask on crossgcc mailing list for help building arm toolchains; you have to edit demo-arm.sh.
We target on arm platform. but running $sh demo-arm.sh cannot be sucessful.(error messeage related to some .h file)
running $sh demo-mipsel.sh was success.
another question is that under which directory we should use $wget ..../crosstool-0.26.tar.gz. I use $wget .../crosstool-0.26.tar.gz under ...opt/scanner/. but I guess it does not matter really.
>From: "Dan Kegel" <dank@kegel.com> >To: "Z. M." <zed6641@hotmail.com> >Subject: Re: intro to Embedded linux programming >Date: Fri, 22 Sep 2006 05:55:12 -0700 > >Not sure I understand the question. >What hardware are you trying to target? > >The demo-foo.sh scripts are really just examples; you have >to look at them carefully and maybe update them before using them. >See buildlogs/index.html for working combinations of tools. >- Dan > >On 9/22/06, Z. M. <zed6641@hotmail.com> wrote: >> >>Now it is ok for $sh demo-mipsel.sh, do we have to run >>$sh demo-arm.sh for arm as well? >>i didn't run for power pc but the tool chains were generated for power pc >>under ./crosstool. >> >> >> >From: "Dan Kegel" <dank@kegel.com> >> >To: "Z. M." <zed6641@hotmail.com> >> >Subject: Re: intro to Embedded linux programming >> >Date: Wed, 20 Sep 2006 22:05:46 -0700 >> > >> >Yes. Try >> > unset LD_LIBRARY_PATH >> >first. >> > >> >On 9/20/06, Z. M. <zed6641@hotmail.com> wrote: >> >> >> >>I was sucessful to build the tool chains on one linux machine. But >>today >> >>when I ytied to build the tool chain on another one, under >>crosstool-0.26 >> >>by >> >>typing >> >> >> >>$sh demo-mipsel.sh >> >> >> >>the following error happened. >> >> >> >>checking ... >> >>checking... >> >>checking ... >> >>configure: error: >> >>*** LD_LIBRARY_PATH should not contain current directory when building >> >>glibc. PLEASE CHNAGE THE ENVIORNMENT VARIABLE AND RUN CONFIGURE AGAIN. >> >> >> >> >> >>I tried others like >> >>$sh demo-arm.sh >> >> >> >>same error shows up. >> >>Does it related to PC envionment setting? >> >> >> >> >> >> >> >>regards, >> >> >> >> >From: "Dan Kegel" <dank@kegel.com> >> >> >To: "Z. M." <zed6641@hotmail.com> >> >> >Subject: Re: intro to Embedded linux programming >> >> >Date: Thu, 14 Sep 2006 08:18:09 -0700 >> >> > >> >> >On 9/14/06, Z. M. <zed6641@hotmail.com> wrote: >> >> >>thanks. that's what I guess -it must run on the firmware (scanner). >>but >> >>i >> >> >>guess it might be a shortcoming for linux embed dev. - at least >>there >> >> >>should >> >> >>be some kind of software tools to play on linux PC ... >> >> > >> >> >There are a few simulators out there if you need them. >> >> >Some are included with gdb, but you have to build from source, >> >> >and I haven't played with them. >> >> >- Dan >> >> >> >> >> >> >> > >> > >> >-- >> >Wine for Windows ISVs: http://kegel.com/wine/isv >> >> >> > > >-- >Wine for Windows ISVs: http://kegel.com/wine/isv
-- Wine for Windows ISVs: http://kegel.com/wine/isv
-- For unsubscribe information see http://sourceware.org/lists.html#faq
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |