Slashdot Mirror

← Back to Stories (view on slashdot.org)

amd64 cross-world completed on FreeBSD

Posted by CmdrTaco on from the bsd-uber-alles dept.

BSD Forums writes "FreeBSD's Dag-Erling Smorgrav reports the successful cross-world build of the amd64 tree (A tinderbox is system designed to test builds and report failure. In the FreeBSD case, tinderboxes build world [the base system], GENERIC, and if applicable LINT kernels. Dag-Erling Smorgrav currently runs all the tinderboxes by cross-building from i386)."

4 of 31 comments (clear)

  1. amd64 support in -current by kernelistic · · Score: 5, Informative

    It's important to note that this anouncement only affects FreeBSD -current. -current also supports alpha, ia64 (Itanium2), pc98 and sparc64.

    The -stable branch currently only supports i386, pc98 and alpha. When the 5.x branch will be deemed to be stable, all of -current's architectures will get official ISO images and testing using a wider audience will be possible. At this point work on 6-current will begin.

  2. For a bit more information by edhall · · Score: 4, Informative
    Here is a commit message, which lists what is and isn't working yet. There are still some loose ends (as the message states), but things appear to be coming along quickly.
    -Ed
  3. FreeBSD portability by Anonymous Coward · · Score: 3, Interesting

    Please forgive my ignorance, but does FreeBSD have a bus/architecture independant driver model similar to the one found in NetBSD? I hear that such a gerneric/"object oriented" driver model greatly eases the porting process from one architecture to another. Does FreeBSD have such a thing, or does it have separate drivers for each different bus or architecture?

    I was just reading the following page and began to wonder about this:

    http://www.netbsd.org/Goals/system.html

    I would be greatful for any information you folks could give me.

    1. Re:FreeBSD portability by Anonymous Coward · · Score: 4, Informative

      www.freebsd.org/projects/busdma

      FreeBSD has been working on alpha, sparc64, ia64, powerpc, mips, s390, arm, and amd64 ports for a while and they've grabbed a little NetBSD code along the way to improve driver portability (adding in their own contributions as well) while NetBSD has grabbed FreeBSD's kqueue code and other goodies. Read the release notes for the various architectures to get a progress report. 5.x branch is the one that supports much more architectures and what not.