This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See crosstool-NG 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] |
Sasikumar, On Wed, Nov 4, 2015 at 1:53 PM, Bryan Hundven <bryanhundven@gmail.com> wrote: > Sasikumar, > > On Wed, Nov 4, 2015 at 1:51 PM, Sasikumar Kandhasamy <ckmsasi@gmail.com> wrote: >> Hi Bryan, >> >> Found the option to build the regular cross toolchain using glibc. But, am >> getting below error while extracting the newlibc. Here, i haven't selected >> newlib in the config, but still ct-ng is trying to build newlib-2.2.0. Is it >> expected? > > If you change the config run `ct-ng clean` before running `ct-ng build` again. > You have to clean out the build directory first! :) I am moving this conversation to crossgcc@sourceware.org from gcc-help@gcc.gnu.org, as this is the proper place for this conversation. Let us know if you need further assistance! Cheers, -Bryan >> ALL ] mode of `./config.sub' retained as 0755 (rwxr-xr-x) >> [ALL ] `/crossng/bldcng/crosstool-ng/scripts/config.sub' -> >> `./config.sub' >> [DEBUG] ==> Executing: 'touch' >> '/crossng/bldcng/ctc/.build/src/.gcc-5.2.0.patched' >> [DEBUG] ==> Executing: 'rm' '-f' >> '/crossng/bldcng/ctc/.build/src/.gcc-5.2.0.patching' >> [DEBUG] ==> Executing: 'touch' >> '/crossng/bldcng/ctc/.build/src/.newlib-2.2.0.extracting' >> [DEBUG] Entering '/crossng/bldcng/ctc/.build/src' >> [EXTRA] Extracting 'newlib-2.2.0' >> [DEBUG] ==> Executing: 'mkdir' '-p' 'newlib-2.2.0' >> [DEBUG] ==> Executing: 'tar' '--strip-components=1' '-C' 'newlib-2.2.0' >> '-xv' '-f' '-' >> [FILE ] tar: This does not look like a tar archive >> [FILE ] tar: Exiting with failure status due to previous errors >> [ERROR] >> [ERROR] >> >> [ERROR] >> Build failed in step 'Extracting and patching toolchain >> components' >> [ERROR] >> called in step '(top-level)' >> [ERROR] >> >> [ERROR] >> Error happened in: CT_DoExecLog[scripts/functions@257] >> [ERROR] >> called from: CT_Extract[scripts/functions@982] >> [ERROR] >> called from: >> do_libc_extract[scripts/build/libc/newlib.sh@39] >> [ERROR] >> called from: main[scripts/crosstool-NG.sh@609] >> [ERROR] >> >> [ERROR] >> For more info on this error, look at the file: 'build.log' >> [ERROR] >> There is a list of known issues, some with workarounds, in: >> [ERROR] >> '/crossng/bldcng/crosstool-ng/docs/B - Known issue >> >> >> Thanks & Regards >> Sasi >> >> On Wed, Nov 4, 2015 at 11:27 AM, Sasikumar Kandhasamy <ckmsasi@gmail.com> >> wrote: >>> >>> Thanks a lot Bryan. That worked. Currently, build is in progress. >>> >>> Another clarification, does it build elf/abi bare metal cross toolchain or >>> regular gcc cross toolchain? Because i would like build regular cross >>> toolchain and didn't see any option in menuconfig regarding the same. >>> >>> Thanks & Regards >>> Sasi >>> >>> On Wed, Nov 4, 2015 at 2:48 AM, Bryan Hundven <bryanhundven@gmail.com> >>> wrote: >>>> >>>> Sasikumar, >>>> >>>> On Mon, Nov 2, 2015 at 4:20 PM, Sasikumar Kandhasamy <ckmsasi@gmail.com> >>>> wrote: >>>> > Hi Steve/Bryan, >>>> > >>>> > My linux machine is doesn't have latest autoconf to configure the >>>> > crosstool-ng and i don't have permission to upgrade the autoconf and >>>> > dependency software. >>>> > >>>> > How can i get the latest version of crosstool-ng with the above fix? >>>> > Also, i >>>> > hope, we can configure crosstool-ng manually. >>>> >>>> You could just install autoconf, automake, and libtool to a local >>>> path, say: $HOME/autotools >>>> >>>> get the source for each... >>>> ./configure --prefix="$HOME/autotools" >>>> make >>>> make install >>>> export PATH="$HOME/autotools:$PATH" >>>> >>>> Cheers, >>>> >>>> -Bryan >>>> >>>> > Thanks & Regards >>>> > Sasi >>>> > >>>> > On Mon, Nov 2, 2015 at 3:52 PM, Steve Ellcey <sellcey@imgtec.com> >>>> > wrote: >>>> >> >>>> >> On Mon, 2015-11-02 at 14:19 -0800, Bryan Hundven wrote: >>>> >> >>>> >> > > Oh! I see now. 64-bit should not need to be marked as >>>> >> > > experimental! >>>> >> > > I will make sure that is fixed in 1.22.0 (which will be releasing >>>> >> > > soon!)! >>>> >> > >>>> >> > My apologies for not noticing the issue sooner! This is now fixed in >>>> >> > git and will be fixed in 1.22.0: >>>> >> > >>>> >> > >>>> >> > https://github.com/crosstool-ng/crosstool-ng/commit/4be766254d2368901513aa25fefbaa383092f3cd >>>> >> > >>>> >> > Thanks! >>>> >> > >>>> >> > -Bryan >>>> >> >>>> >> FYI: I downloaded the latest crosstool-ng sources and was able to >>>> >> successfully build a mips64 toolchain (n64 ABI) that included Fortran. >>>> >> >>>> >> Steve Ellcey >>>> >> sellcey@imgtec.com >>>> >> >>>> > >>> >>> >> -- 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] |