DragonFlyBSD

:
:With MACHINE set to pc32, installworld won't install fdisk (which is in
:sbin/i386). Should fdisk be moved to sbin/pc32?
:
:Sascha
:
:--
:http://yoyodyne.ath.cx

We could do that, or we could adjust /usr/src/sbin/Makefile to ALSO
    check for a MACHINE_ARCH subdirectory and push into that too:

.if exists(${.CURDIR}/${MACHINE})
    SUBDIR+= ${MACHINE}
    .endif
    .if exists(${.CURDIR}/${MACHINE_ARCH})    <<<< ADDME
    SUBDIR+= ${MACHINE_ARCH}            <<<< ADDME
    .endif                    <<<< ADDME

Which I think might be the correct solution here.

-Matt
                    Matthew Dillon 
                    <dillon@backplane.com>

[..]

Which I think might be the correct solution here.

I don't think so. fdisk is a part of the machine architecture (pc32),
not the cpu (i386). if we want to it correctly, we would have to move
fdisk to pc32.

cheers
simon

:..
:> check for a MACHINE_ARCH subdirectory and push into that too:
:[..]
:> Which I think might be the correct solution here.
:
:I don't think so. fdisk is a part of the machine architecture (pc32),
:not the cpu (i386). if we want to it correctly, we would have to move
:fdisk to pc32.
:
:cheers
: simon

Do you want 'fdisk' to exist for the virtual kernel build?  I think
    it should.

Alternatively we can use the new /usr/src/sys/machine/<BLAH>/Makefile.inc
    mechanism to condtionalize the build for fdisk and not have it depend
    on MACHINE or MACHINE_ARCH at all.

-Matt

Please also take a look at /usr/sbin/boot0cfg which also doesn't get
installed anymore because of the i386->pc32 changes.

Sascha

One more problem I forgot: The installation of the boot.8 manpage from
sbin/reboot/Makefile fails too because of these changes.

Sascha

:Please also take a look at /usr/sbin/boot0cfg which also doesn't get
:installed anymore because of the i386->pc32 changes.
:
:Sascha

Ok, that should be fixed now.

-Matt
                    Matthew Dillon 
                    <dillon@backplane.com>