---------- Forwarded message --------- From: Derek Johansen <djohanse678@xxxxxxxxx> Date: Sun, Sep 29, 2019 at 10:04 AM Subject: Re: Gcc install package To: Marc-F. Lucca-Daniau <mfld.fr@xxxxxxxxx> Thank you for the quick reply. It took around 24 hrs for gcc to build. Hopefully that will only be needed rarely. Two new questions: 1. When I try to start elks with sudo ./qemu.sh It tells me tsc in an invalid qemu command. If I take tsc out of qemu startup script command line it seems to work fine 2. Find command in ELKS not working as expected. When I do "find ." from ELKS command prompt it says 'find: can't get path from environment". But when I do env command I see my PATH defined. Also echo $PATH returns correct PATH Thanks, Derek . On Sun, Sep 29, 2019 at 3:13 AM Marc-F. Lucca-Daniau <mfld.fr@xxxxxxxxx> wrote: > > Hello Derek, > > The ELKS 'clean' target preserves the 'cross' directory (except the > 'libc' installation), so you won't have to wait again for the tools to > rebuild, including the customized GCC for IA16. > > There is no binary package for the tools, except the GCC for IA16 one > that @Tkchia provides for Ubuntu. > > I understand that rebuilding GCC is quite long, but I see no easy way to > ensure full compatibility with the various build platforms out of > starting from the sources... > > Thanks, > > MFLD > > > > > Le sam. 28 sept. 2019 19:18, Derek Johansen <djohanse678@xxxxxxxxx > > <mailto:djohanse678@xxxxxxxxx>> a écrit : > > > > Hello, > > > > Been away from elks for a year or so now. Trying to migrate to new > > gcc compiler based build. After installing prerequisites gmp, mpc, > > mpfr, .build.sh script appears to be working. But on a linux vbox > > virtual machine hosted on a windows machine n2850 celeron processor > > circa 2014,compiling gcc is going on 14 hrs and counting. > > > > Is there any way to get a prebuilt binary of gcc to avoid this issue? > > Also if not, once everything is working hen will a make clean in the > > elks environment force another (14 hrs plus) rebuild of gcc? > > > > Thanks, > > Derek > >
