Properly building newlib to install spec files

[Jeff Johnston]

If you build and install the various components to the same installation
directory, it should just work.

See: https://gist.github.com/resetnow/1b55beed32f3eb3f90513896565ef5c0

(your gcc compiler config options may vary)

If a spec file is installed somewhere else, you can use the -B option on
the compile to specify a location for gcc to look for it.

-- Jeff J.

On Sat, Jan 5, 2019 at 4:20 PM Mojca Miklavec <mojca@macports.org> wrote:

> Hi,
>
> I'm fixing some packages for a package manager. I think I have a bunch
> of various working gcc crosscompilers, but if I try to test something
> like
>
> $ msp430-elf-gcc -mmcu=msp430g2211 -specs=nosys.specs -o test.elf test.c
> msp430-elf-gcc: error: nosys.specs: No such file or directory
>
> apparently the specs files are missing.
>
> I'm creating a symlink from gcc to newlib and build gcc with
> --with-newlib, but apparently the files don't get installed. I noticed
> that random instructions suggest separately building:
> - first gcc
> - then newlib
> - then gcc again
> http://www.ifp.illinois.edu/~nakazato/tips/xgcc.html#gccagain
>
> while other instructions say to use just --with-newlib.
>
> Can you please advise me how to build newlib in a proper way, so that
> the spec files will be installed? Where should they usually end up?
>
> Thank you very much,
>     Mojca
>