Merging 64 bit changes to -HEAD - part 4

[Jayachandran C.]

On Thu, Jul 8, 2010 at 1:59 PM, Juli Mallett <jmallett at freebsd.org> wrote:
> On Thu, Jul 8, 2010 at 01:12, M. Warner Losh <imp at bsdimp.com> wrote:
>> In message: <AANLkTikSVi27V2UICgLvKd8Bk7v6tuGty9YX6-C6-21H at mail.gmail.com>
>>            "Jayachandran C." <c.jayachandran at gmail.com> writes:
>> : ldscript-64.patch
>> :  64 bit linker script (JC)
>> :  linker script for 64 bit compilation, and XLR configuration file.
>>
>> I wonder if the octeon ld script can be merged or if we can use this
>> for octeon.  Some investigation is warranted, I think...
>
> No investigation needed.
>
> U-Boot, at least on Octeon, requires only one (executable) program
> header, so it's necessary for Octeon to use its own ldscript -- I
> suspect other bootloaders have likewise weird constraints.  That said,
> there's really no need for all of these separate linker scripts,
> assuming you use buildkernel and have TARGET_ABI set right when you
> build kernel-toolchain.  I use a single linker script for all Octeon
> kernels, I think.  You don't need to specify the output format.

We could probably make the single script you have as the standard
script if it works for most bootloaders.

I still don't like the way   ARCH_FLAGS and LDSCRIPT_NAME needs to be
specified in the conf file - this could be taken from TARGET_ABI
too...

JC.