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] |
On 1/9/06, Keith Kyzivat <kkyzivat@physiometrix.com> wrote: > I've got a sucessful canadian cross that is x86_64 built, i686 hosted > and i686 targetted, but ran into some ranlib problems that I fixed. > ... > Steps from Dan's Canadian Cross description > (http://kegel.com/crosstool/crosstool-0.38/doc/crosstool-howto.html#canadian) > > 1/2. BUILD=x86_64 HOST=x86_64 TARGET=i686 (destination HOST and TARGET > are the same - no need for separate steps 1 and 2 as they are the same) > 3. BUILD=x86_64 HOST/GCC_HOST=i686 TARGET=i686 > > > Step 1/2 worked fine. > After setting up the requsite GCC_HOST, AR, and CC vars and exporting > them, and starting the build, > I came by an error... > The obvious thing to choose was to set RANLIB the same way I set AR and > CC, with the ranlib generated from step 1. > investigating crosstool.sh seemed to support that argument, and off I > sent crosstool. > > Now it's done, and voila! I've got a canadian cross x86_64 built i686 > -> i686 cross-compiler. > > Now, here's the question: why is RANLIB not detected properly? Why > wasn't this caught before by Dan when he put in the bit of info on > canadian cross builds? Who knows! Sounds like an obvious thing to add, though. Thanks! - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |