Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 02 Sep 2002 18:36:04 -0700
From:      Terry Lambert <tlambert2@mindspring.com>
To:        Matthew Dillon <dillon@apollo.backplane.com>
Cc:        Peter Wemm <peter@wemm.org>, hackers@FreeBSD.ORG
Subject:   Re: 64 bit API/ABI changes proposal for -current
Message-ID:  <3D741204.F035A715@mindspring.com>
References:  <20020902215358.E3A992A893@canning.wemm.org> <200209022207.g82M7OAe034138@apollo.backplane.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Dillon wrote:
>     Well, then what we want is a new syscall vector, duplicate libraries,
>     and a compiler option, and leave all the function names the same
>     (which means no bintime but allows us to retain everything else).
>     -current would release supporting both with the compiler option
>     defaulting to --unix32 on the IA32 and --unix64 on 64 bit platforms,
>     and then down the line the compiler option would default to --unix64
>     on all platforms, and then down the line a little more the original
>     syscall vector would become a compatibility option that most people
>     leave out.


Not to be a party-pooper, but I think this will fail as soon
as you have a program that wants to link against a third party
library that calls entry points in libc.

It doesn't even have to be a binary-only thing; think of trying
to build packages for the purposes of a CDROM distribution.  You
would end up needing to do the same "--unix32/--unix64" thing for
every library you build.

-- Terry

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




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