Re: CVS commit: src/sys/arch/m68k/fpsp

[Masao Uebayashi <uebayasi%gmail.com@localhost>]

On Mon, Sep 7, 2015 at 7:01 AM, David Laight <david%l8s.co.uk@localhost> wrote:
> On Sat, Sep 05, 2015 at 09:39:43AM +0900, Masao Uebayashi wrote:
>> The reason of this is that config(1) have no idea of library at this
>> moment.  Makefile.kern.inc has also a convention that all *.o files
>> have to be built under the top of kernel build directory.  libkern &
>> libcompat have speicalized make(1) rules, that work but look ugly.
>> I'd consider to extend config(1) to support library...

The first `this' referred to a rule I added to fix build:

fpsp.o: ${FPSP}
        ln -sf ${FPSP} fpsp.o

where ${FPSP} is an absolute path to ${.OBJDIR}/lib/fpsp/fpsp.o.

m68k defined ${FPSP} as ${MD_OBJS}, but I changed paths in ${MD_OBJS}
to be normalized to just file names (no /) to simplify explicit rule
generation.  Now that I introduced ${MD_LIBS}, whose paths are not
normalized, that symlink is no longer needed & removed.

(As a bonus, fpsp.o is linked at last, not just after start code.
Like other libraries.)

> Please can you keep some context in your emails.
> The 'this' is the first line is a reference to something unknown.
>
> Oh, and one historic reason for the kernel objects being in a .a
> file was to allow builds on systems with short command line length
> limits.
>
>         David
>
> --
> David Laight: david%l8s.co.uk@localhost