Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 4 Apr 1995 14:43:59 -0700 (PDT)
From:      "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
To:        rkw@dataplex.net (Richard Wackerbarth)
Cc:        current@FreeBSD.org
Subject:   Re: cvs commit: src/sys/i386/conf Makefile.i386
Message-ID:  <199504042143.OAA08472@gndrsh.aac.dev.com>
In-Reply-To: <v02120b04aba764b0764d@[199.183.109.242]> from "Richard Wackerbarth" at Apr 4, 95 04:13:28 pm

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> >The rule for genassym's should be changed such that it always uses
> >/usr/include/stdio.h, that is the correct file to use, period, as
> >it is going to be linked and run against /usr/lib/libc.a at the time
> >the kernel is compiled.  This will be extreamly important for cross
> >compilation in the future.
> 
> Actually, cross compilation is why it is WRONG!.

You had better go understand genassym a bit more before you start in
on this....

> There are two genassym's. One will be run on "this" machine to generate a
> kernel for "that" machine and the other is a version which will be in the
> distribution which is installed on "that" machine and used to rebuild the
> kernel.

Your never going to be able to put a genassym in the distribution that
will last longer than a day with our kernel sources, and it would
not work for all the possible kernel config options that a kernel
can have.

> Since the two versions are linked against different libraries, it is
> important that thare is NO ABSOLUTE reference to any file. All references
> MUST be RELATIVE to the environment in which the code will be executed.

Drop this issue for now, until you have actually made what you are
saying work.

-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                   Custom computers for FreeBSD



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504042143.OAA08472>