Re: [Gm2] Building gm2-4.7.3 on MacOS 10.5.8/PPC

[john o goyo]

Gaius:

On 04/09/2014 11:16, Gaius Mulley wrote (in part):
> > On 02/09/2014 21:59, john o goyo wrote (in part):
> > Now mod_init.o is there but could you please explain the linking
> > instructions above?  A grep for linkcommand found nothing that I understood.
> Hi John,
>
> sure, the program $(M2LINK) takes as input ../$(srcdir)/gm2/init/ppginit
> which is a list of module names.  It searches the $(M2PATH) to find each
> modulename.o or modulename.a and generates a file 'linkcommand' (in the
> build directory) which is a small script 'gcc list of module names '
> with the additional libraries (p2c/p2c-src/src/libp2c.a and
> ../../libiberty/safe-ctype.o).

I found the problem but not the solution.

I added a judicious comment character '#' to Make-lang.in to prevent
linkcommand from being deleted.  Here is the generated script:

    gcc-4.2 -g gm2-libs-boot/RTExceptions.o [...]

Now LDFLAGS='-m64 -mtune=970 -O3' was specified on the configuration
line.  I added '-m64 -mtune=970' to linkcommand and ppginit linked
without a problem.

Where does m2link pick up its linking flags and why does it not honour
LDFLAGS?

jog