status of amd64

[Robert Millan]

On Thu, Jan 19, 2006 at 10:40:01AM +0100, Petr Salinger wrote:
> 
> TODO list:
> 
> * decide ld.so location
>         It should be unique between all (at least Debian) ports,
>         namely not the same as on kfreebsd-i386 (/lib/ld.so.1).
>         See also http://www.linuxbase.org/futures/ideas/multiarch/index.html
> 
>         Proposed: /lib/ld-kfreebsd-amd64.so.1

Shouldn't we discuss this with upstream? (libc-ports)

> 
> * toolchain (gcc, binutils) support
>         Write config bits for proper
>         ld.so location:         /lib/ld.so.1    /lib/ld-kfreebsd-amd64.so.1
>         emulation:              elf_i386_fbsd   elf_x86_64_fbsd

AFAIK x86_64-*-kfreebsd-gnu already maps to elf_x86_64_fbsd in binutils.
(I don't know about -m64 flag)

As for gcc, I think we could ditch the sc_* register name problem by using a
union from the beginning (this way we don't have to add as much cruft to
x86_64/kfreebsd-gnu.h).

> * biarch capable kfreebsd-kernel-headers
>         similarly to linux-kernel-headers,
>         all files in /usr/include/machine should be autogenerated in form
>         on kfreebsd-i386
>                 #ifdef __x86_64__
>                 # include <amd64/param.h>
>                 #else
>                 # include <i386/param.h>
>                 #endif
>         on kfreebsd-amd64
>                 #ifdef __i386__
>                 # include <i386/param.h>
>                 #else
>                 # include <amd64/param.h>
>                 #endif
> 
>         the first step is to provide content of dir amd64,
>         it would be sufficient for test builds of glibc

Is this really a pre-requisite for starting an amd64 port ?  Maybe we can make
it "uniarch" first and add biarch support later.  This is what the GNU/Linux
port did AFAIK.

-- 
Robert Millan