Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64] [filemon fails to load on powerpc64]

[Bryan Drewery]

On 6/4/2016 12:17 AM, Mark Millard wrote:
> On 2016-Jun-2, at 12:36 PM, Bryan Drewery  wrote:
> 
>> On 6/1/2016 6:39 PM, Mark Millard wrote:
>>> while filemon.ko now exists:
 # ls -l /boot/*/filemon*
 -r-xr-xr-x  1 root  wheel  32064 Jun  1 17:59 /boot/kernel/filemon.ko
>>> it does not load:
 # kldload -n filemon
 kldload: can't load filemon: No such file or directory
 # dmesg | grep link_elf
 link_elf: symbol elf64_freebsd_sysvec undefined
>>> So no WITH_META_MODE=yes yet for powerpc64.
>>
>>
>> Please try this patch: http://dpaste.com/37VP5MD.txt
>>
>> And once you have filemon loaded please run this basic test script.  It
>> should return no output and a zero exit status.
>>
>> http://dpaste.com/23NTA0A.txt
>>
>> Just sh file it.
>>
>> -- 
>> Regards,
>> Bryan Drewery
> 
> Unfortunately other things interfered and I was unable to do this before 
> temporarily losing access to the powerpc and powerpc64 boxes --for what will 
> probably be weeks or months.
> 

No problem...

> So for now it is the end of my native-testing for powerpc64 and powerpc.
> 
> I do not know if anyone else has an appropriate context and willingness to do 
> this specific test or not.
> 
> For the duration I should still be able to do amd64 -> powerpc64 or powerpc 
> cross builds (buildworld buildkernel), although likely with less time and 
> more delay for doing so.
> 
> I am hoping to still have rpi2 access for armv6/v7 native use. But I've yet 
> to make the soft-float to hard-float leap: I focused primarily on the 
> powerpc64 and powerpc use, knowing up front of the pending 
> temporarily-unavailable status.
> 
> 
> 
> Thanks for all the work on the build system by you and others. Originally I 
> had a bunch of workarounds in my src.conf files to avoid problems that 
> occurred for the likes of a libc++-based, xtoolchain-based so-called "cross 
> build" (self-hosted), powerpc64 environment (no gcc 4.2.1 and clang not 
> working for such yet). Far more works implicitly in src.conf files for such a 
> context now.
> 

Thanks for all of the testing and feedback!


-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64] [filemon fails to load on powerpc64]

[Mark Millard]

On 2016-Jun-2, at 12:36 PM, Bryan Drewery  wrote:

> On 6/1/2016 6:39 PM, Mark Millard wrote:
>> while filemon.ko now exists:
>>> # ls -l /boot/*/filemon*
>>> -r-xr-xr-x  1 root  wheel  32064 Jun  1 17:59 /boot/kernel/filemon.ko
>> it does not load:
>>> # kldload -n filemon
>>> kldload: can't load filemon: No such file or directory
>>> # dmesg | grep link_elf
>>> link_elf: symbol elf64_freebsd_sysvec undefined
>> So no WITH_META_MODE=yes yet for powerpc64.
> 
> 
> Please try this patch: http://dpaste.com/37VP5MD.txt
> 
> And once you have filemon loaded please run this basic test script.  It
> should return no output and a zero exit status.
> 
> http://dpaste.com/23NTA0A.txt
> 
> Just sh file it.
> 
> -- 
> Regards,
> Bryan Drewery

Unfortunately other things interfered and I was unable to do this before 
temporarily losing access to the powerpc and powerpc64 boxes --for what will 
probably be weeks or months.

So for now it is the end of my native-testing for powerpc64 and powerpc.

I do not know if anyone else has an appropriate context and willingness to do 
this specific test or not.

For the duration I should still be able to do amd64 -> powerpc64 or powerpc 
cross builds (buildworld buildkernel), although likely with less time and more 
delay for doing so.

I am hoping to still have rpi2 access for armv6/v7 native use. But I've yet to 
make the soft-float to hard-float leap: I focused primarily on the powerpc64 
and powerpc use, knowing up front of the pending temporarily-unavailable status.



Thanks for all the work on the build system by you and others. Originally I had 
a bunch of workarounds in my src.conf files to avoid problems that occurred for 
the likes of a libc++-based, xtoolchain-based so-called "cross build" 
(self-hosted), powerpc64 environment (no gcc 4.2.1 and clang not working for 
such yet). Far more works implicitly in src.conf files for such a context now.

===
Mark Millard
markmi at dsl-only.net

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64] [filemon fails to load on powerpc64]

[Bryan Drewery]

On 6/1/2016 6:39 PM, Mark Millard wrote:
> while filemon.ko now exists:
>> # ls -l /boot/*/filemon*
>> -r-xr-xr-x  1 root  wheel  32064 Jun  1 17:59 /boot/kernel/filemon.ko
> it does not load:
>> # kldload -n filemon
>> kldload: can't load filemon: No such file or directory
>> # dmesg | grep link_elf
>> link_elf: symbol elf64_freebsd_sysvec undefined
> So no WITH_META_MODE=yes yet for powerpc64.


Please try this patch: http://dpaste.com/37VP5MD.txt

And once you have filemon loaded please run this basic test script.  It
should return no output and a zero exit status.

http://dpaste.com/23NTA0A.txt

Just sh file it.

-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64] [filemon fails to load on powerpc64]

[Justin Hibbits]

On Wed, Jun 1, 2016 at 8:59 PM, Bryan Drewery  wrote:
> On 6/1/2016 6:39 PM, Mark Millard wrote:
>> while filemon.ko now exists:
>>> # ls -l /boot/*/filemon*
>>> -r-xr-xr-x  1 root  wheel  32064 Jun  1 17:59 /boot/kernel/filemon.ko
>> it does not load:
>>> # kldload -n filemon
>>> kldload: can't load filemon: No such file or directory
>>> # dmesg | grep link_elf
>>> link_elf: symbol elf64_freebsd_sysvec undefined
>
> There's 2 different ABI formats for powerpc64?
>
>> sys/powerpc/powerpc/elf64_machdep.c:INIT_SYSENTVEC(elf64_sysvec_v1, 
>> _freebsd_sysvec_v1);
>> sys/powerpc/powerpc/elf64_machdep.c:INIT_SYSENTVEC(elf64_sysvec_v2, 
>> _freebsd_sysvec_v2);
>
> What's up with that?
>
> --
> Regards,
> Bryan Drewery
>

Yes, powerpc64 has two ABIs now.  ELFv1 is traditional ABI.  ELFv2 was
created IBM for their little-endian (POWER8 ppc64le) target.  Nathan
added support to use it in FreeBSD.  It cleans up some of the
silliness that's in ELFv1, such as function descriptors.

- Justin
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64] [filemon fails to load on powerpc64]

[Mark Millard]

On 2016-Jun-1, at 7:21 PM, Bryan Drewery  wrote:
> 
> The fix is easy, I am just wondering why there are 2 ABI formats
> supported.  If only one is normally used and the default then I'll only
> support that one.
> 
> Filemon hooks the syscall table.

The only differences that I see are (_v1 then _v2 pairs):

.sv_sigcode = sigcode64,
.sv_szsigcode   = ,
.sv_name= "FreeBSD ELF64",
vs.
.sv_sigcode = sigcode64_elfv2,
.sv_szsigcode   = _elfv2,
.sv_name= "FreeBSD ELF64 V2",

and:

.sv_setregs = exec_setregs_funcdesc,
vs.
.sv_setregs = exec_setregs,

Only for the _v1 case:

.sv_trap= NULL,

This appears to be two different ELF format versions.

This is confirmed by:

https://patchwork.ozlabs.org/patch/433747/

(from 2015-Jan-28) where Nathan wrote:

Big-endian ELF64 ELF executables normally (the Linux kernel is an 
exception) have their entry point refer to a function descriptor instead 
of the first instruction. Distinguish between the Linux case and the 
function descriptor case, which is used for the FreeBSD kernel, by 
checking whether the entry point points into an executable section or 
not. This allows use of the FreeBSD kernel as a skiboot payload.


===
Mark Millard
markmi at dsl-only.net

Older material. . .

On 6/1/2016 7:16 PM, Mark Millard wrote:
> May be Nathan Whitehorn knows what is going on that prevents filemon.ko
> from loading for powerpc64 based on how it is now built (added for more
> than i386 and amd64 as of -r301130)?
> 
> Nathan: See below if it sounds like something you might have a clue
> about. As to why this comers up: Loading filemon.ko is required in order
> for WITH_META_MODE=yes to work for incremental builds.
> 
> ===
> Mark Millard
> markmi at dsl-only.net 
> 
> On 2016-Jun-1, at 6:59 PM, Bryan Drewery  > wrote:
> 
>> On 6/1/2016 6:39 PM, Mark Millard wrote:
>>> while filemon.ko now exists:
 # ls -l /boot/*/filemon*
 -r-xr-xr-x  1 root  wheel  32064 Jun  1 17:59 /boot/kernel/filemon.ko
>>> it does not load:
 # kldload -n filemon
 kldload: can't load filemon: No such file or directory
 # dmesg | grep link_elf
 link_elf: symbol elf64_freebsd_sysvec undefined
>> 
>> There's 2 different ABI formats for powerpc64?
>> 
>>> sys/powerpc/powerpc/elf64_machdep.c:INIT_SYSENTVEC(elf64_sysvec_v1,
>>> _freebsd_sysvec_v1);
>>> sys/powerpc/powerpc/elf64_machdep.c:INIT_SYSENTVEC(elf64_sysvec_v2,
>>> _freebsd_sysvec_v2);
>> 
>> What's up with that?
>> 
>> -- 
>> Regards,
>> Bryan Drewery
> 
> 


-- 
Regards,
Bryan Drewery


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64] [filemon fails to load on powerpc64]

[Bryan Drewery]

The fix is easy, I am just wondering why there are 2 ABI formats
supported.  If only one is normally used and the default then I'll only
support that one.

Filemon hooks the syscall table.

On 6/1/2016 7:16 PM, Mark Millard wrote:
> May be Nathan Whitehorn knows what is going on that prevents filemon.ko
> from loading for powerpc64 based on how it is now built (added for more
> than i386 and amd64 as of -r301130)?
> 
> Nathan: See below if it sounds like something you might have a clue
> about. As to why this comers up: Loading filemon.ko is required in order
> for WITH_META_MODE=yes to work for incremental builds.
> 
> ===
> Mark Millard
> markmi at dsl-only.net 
> 
> On 2016-Jun-1, at 6:59 PM, Bryan Drewery  > wrote:
> 
>> On 6/1/2016 6:39 PM, Mark Millard wrote:
>>> while filemon.ko now exists:
 # ls -l /boot/*/filemon*
 -r-xr-xr-x  1 root  wheel  32064 Jun  1 17:59 /boot/kernel/filemon.ko
>>> it does not load:
 # kldload -n filemon
 kldload: can't load filemon: No such file or directory
 # dmesg | grep link_elf
 link_elf: symbol elf64_freebsd_sysvec undefined
>>
>> There's 2 different ABI formats for powerpc64?
>>
>>> sys/powerpc/powerpc/elf64_machdep.c:INIT_SYSENTVEC(elf64_sysvec_v1,
>>> _freebsd_sysvec_v1);
>>> sys/powerpc/powerpc/elf64_machdep.c:INIT_SYSENTVEC(elf64_sysvec_v2,
>>> _freebsd_sysvec_v2);
>>
>> What's up with that?
>>
>> -- 
>> Regards,
>> Bryan Drewery
> 
> 


-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64] [filemon fails to load on powerpc64]

[Mark Millard]

May be Nathan Whitehorn knows what is going on that prevents filemon.ko from 
loading for powerpc64 based on how it is now built (added for more than i386 
and amd64 as of -r301130)?

Nathan: See below if it sounds like something you might have a clue about. As 
to why this comers up: Loading filemon.ko is required in order for 
WITH_META_MODE=yes to work for incremental builds.

===
Mark Millard
markmi at dsl-only.net

On 2016-Jun-1, at 6:59 PM, Bryan Drewery  wrote:

> On 6/1/2016 6:39 PM, Mark Millard wrote:
>> while filemon.ko now exists:
>>> # ls -l /boot/*/filemon*
>>> -r-xr-xr-x  1 root  wheel  32064 Jun  1 17:59 /boot/kernel/filemon.ko
>> it does not load:
>>> # kldload -n filemon
>>> kldload: can't load filemon: No such file or directory
>>> # dmesg | grep link_elf
>>> link_elf: symbol elf64_freebsd_sysvec undefined
> 
> There's 2 different ABI formats for powerpc64?
> 
>> sys/powerpc/powerpc/elf64_machdep.c:INIT_SYSENTVEC(elf64_sysvec_v1, 
>> _freebsd_sysvec_v1);
>> sys/powerpc/powerpc/elf64_machdep.c:INIT_SYSENTVEC(elf64_sysvec_v2, 
>> _freebsd_sysvec_v2);
> 
> What's up with that?
> 
> -- 
> Regards,
> Bryan Drewery


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64] [filemon fails to load on powerpc64]

[Bryan Drewery]

On 6/1/2016 6:39 PM, Mark Millard wrote:
> while filemon.ko now exists:
>> # ls -l /boot/*/filemon*
>> -r-xr-xr-x  1 root  wheel  32064 Jun  1 17:59 /boot/kernel/filemon.ko
> it does not load:
>> # kldload -n filemon
>> kldload: can't load filemon: No such file or directory
>> # dmesg | grep link_elf
>> link_elf: symbol elf64_freebsd_sysvec undefined

There's 2 different ABI formats for powerpc64?

> sys/powerpc/powerpc/elf64_machdep.c:INIT_SYSENTVEC(elf64_sysvec_v1, 
> _freebsd_sysvec_v1);
> sys/powerpc/powerpc/elf64_machdep.c:INIT_SYSENTVEC(elf64_sysvec_v2, 
> _freebsd_sysvec_v2);

What's up with that?

-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64] [filemon fails to load on powerpc64]

[Mark Millard]

[A top-posted error report for powerpc64.]

On 2016-Jun-1, at 8:20 AM, Bryan Drewery  wrote:
> I've just enabled the filemon(4) build on all architectures in r301130.

But on (built via powerpc64-gcc on the powerpc64 box):

> # uname -apKU
> FreeBSD FBSDG5C0 11.0-ALPHA1 FreeBSD 11.0-ALPHA1 #39 r301139M: Wed Jun  1 
> 17:37:17 PDT 2016 
> root@FBSDG5C0:/usr/obj/xtoolchain/powerpc.powerpc64/usr/src/sys/GENERIC64vtsc-NODEBUG
>   powerpc powerpc64 1100116 1100116

while filemon.ko now exists:

> # ls -l /boot/*/filemon*
> -r-xr-xr-x  1 root  wheel  32064 Jun  1 17:59 /boot/kernel/filemon.ko

it does not load:

> # kldload -n filemon
> kldload: can't load filemon: No such file or directory

> # dmesg | grep link_elf
> link_elf: symbol elf64_freebsd_sysvec undefined

So no WITH_META_MODE=yes yet for powerpc64.

I'm not sure when I get to trying the rpi2 (armv6).

===
Mark Millard
markmi at dsl-only.net

On 2016-Jun-1, at 8:20 AM, Bryan Drewery  wrote:

> On 5/29/2016 3:53 PM, Mark Millard wrote:
>> Quoting the original note about WITH_META_MODE ( 
>> https://lists.freebsd.org/pipermail/freebsd-current/2016-May/061481.html ):
>> 
>>> You will also need to load the filemon(4) module with 'kldload filemon'.
>> 
>> But head's sys/modules/Makefile says:
>> 
>>> .if defined(MODULES_OVERRIDE) && !defined(ALL_MODULES)
>>> SUBDIR=${MODULES_OVERRIDE}
>>> .else
>>> SUBDIR= \
>> 
>> . . .
>>>   ${_filemon} \
>> 
>> . . .
>>> .if ${MACHINE_CPUARCH} == "i386" || ${MACHINE_CPUARCH} == "amd64"
>> . . .
>>> _filemon=   filemon
>> . . .
>> 
>> as the only contexts that provide a filemon.ko to use with kldload.
>> 
>> Thus, for example, arm variants (32 bit and 64 bit) and powerpc variants 
>> (32bit and 64 bit) do not have WITH_META_MODE as an option as things are set 
>> up.
>> 
>> I had been hoping to cut down on the time for clang-related rebuilds during 
>> native buildworld runs on my slower buildworld contexts (armv7a/cortex-a7, 
>> powerpc, powerpc64). But it was not to be.
>> 
>> It appears that, once some arm variants are officially tier 1, 
>> WITH_META_MODE will not span all tier 1 platforms.
>> 
>> [Since I tend to use non-tier-1 platforms I tend to notice some of the 
>> statements about FreeBSD that are true of only tier 1 without being explicit 
>> about it. But initially it takes some research to discover that status for 
>> each such point. WITH_META_MODE is an example.]
>> 
> 
> I've just enabled the filemon(4) build on all architectures in r301130.
> 
> -- 
> Regards,
> Bryan Drewery


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64]

[Bryan Drewery]

On 5/29/2016 3:53 PM, Mark Millard wrote:
> Quoting the original note about WITH_META_MODE ( 
> https://lists.freebsd.org/pipermail/freebsd-current/2016-May/061481.html ):
> 
>> You will also need to load the filemon(4) module with 'kldload filemon'.
> 
> But head's sys/modules/Makefile says:
> 
>> .if defined(MODULES_OVERRIDE) && !defined(ALL_MODULES)
>> SUBDIR=${MODULES_OVERRIDE}
>> .else
>> SUBDIR= \
> 
> . . .
>>${_filemon} \
> 
> . . .
>> .if ${MACHINE_CPUARCH} == "i386" || ${MACHINE_CPUARCH} == "amd64"
> . . .
>> _filemon=   filemon
> . . .
> 
> as the only contexts that provide a filemon.ko to use with kldload.
> 
> Thus, for example, arm variants (32 bit and 64 bit) and powerpc variants 
> (32bit and 64 bit) do not have WITH_META_MODE as an option as things are set 
> up.
> 
> I had been hoping to cut down on the time for clang-related rebuilds during 
> native buildworld runs on my slower buildworld contexts (armv7a/cortex-a7, 
> powerpc, powerpc64). But it was not to be.
> 
> It appears that, once some arm variants are officially tier 1, WITH_META_MODE 
> will not span all tier 1 platforms.
> 
> [Since I tend to use non-tier-1 platforms I tend to notice some of the 
> statements about FreeBSD that are true of only tier 1 without being explicit 
> about it. But initially it takes some research to discover that status for 
> each such point. WITH_META_MODE is an example.]
> 

I've just enabled the filemon(4) build on all architectures in r301130.

-- 
Regards,
Bryan Drewery



signature.asc
Description: OpenPGP digital signature

Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64]

[Bryan Drewery]

On 5/29/16 3:53 PM, Mark Millard wrote:
> Quoting the original note about WITH_META_MODE ( 
> https://lists.freebsd.org/pipermail/freebsd-current/2016-May/061481.html ):
> 
>> You will also need to load the filemon(4) module with 'kldload filemon'.
> 
> But head's sys/modules/Makefile says:
> 
>> .if defined(MODULES_OVERRIDE) && !defined(ALL_MODULES)
>> SUBDIR=${MODULES_OVERRIDE}
>> .else
>> SUBDIR= \
> 
> . . .
>>${_filemon} \
> 
> . . .
>> .if ${MACHINE_CPUARCH} == "i386" || ${MACHINE_CPUARCH} == "amd64"
> . . .
>> _filemon=   filemon
> . . .
> 
> as the only contexts that provide a filemon.ko to use with kldload.
> 
> Thus, for example, arm variants (32 bit and 64 bit) and powerpc variants 
> (32bit and 64 bit) do not have WITH_META_MODE as an option as things are set 
> up.
> 
> I had been hoping to cut down on the time for clang-related rebuilds during 
> native buildworld runs on my slower buildworld contexts (armv7a/cortex-a7, 
> powerpc, powerpc64). But it was not to be.
> 
> It appears that, once some arm variants are officially tier 1, WITH_META_MODE 
> will not span all tier 1 platforms.
> 
> [Since I tend to use non-tier-1 platforms I tend to notice some of the 
> statements about FreeBSD that are true of only tier 1 without being explicit 
> about it. But initially it takes some research to discover that status for 
> each such point. WITH_META_MODE is an example.]
> 

Ah, I wasn't aware of the restriction. I am testing building it for
other archs now.  Most of the arch-dependent code has been removed since
the restriction was added.


-- 
Regards,
Bryan Drewery
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64]

[Simon J. Gerraty]

Mark Millard  wrote:
> > .if ${MACHINE_CPUARCH} == "i386" || ${MACHINE_CPUARCH} == "amd64"
> . . .
> > _filemon=   filemon
> . . .
> 

> Thus, for example, arm variants (32 bit and 64 bit) and powerpc
> variants (32bit and 64 bit) do not have WITH_META_MODE as an option as
> things are set up.

FWIW I'm not aware of any reason that filemon(4) wouldn't work on any
architecture.  I expect the above restriction is mostly just a
reflection of expected build hosts.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [CFT] WITH_META_MODE: Working incremental build [only on i386 and amd64]

[Mark Millard]

Quoting the original note about WITH_META_MODE ( 
https://lists.freebsd.org/pipermail/freebsd-current/2016-May/061481.html ):

> You will also need to load the filemon(4) module with 'kldload filemon'.

But head's sys/modules/Makefile says:

> .if defined(MODULES_OVERRIDE) && !defined(ALL_MODULES)
> SUBDIR=${MODULES_OVERRIDE}
> .else
> SUBDIR= \

. . .
>${_filemon} \

. . .
> .if ${MACHINE_CPUARCH} == "i386" || ${MACHINE_CPUARCH} == "amd64"
. . .
> _filemon=   filemon
. . .

as the only contexts that provide a filemon.ko to use with kldload.

Thus, for example, arm variants (32 bit and 64 bit) and powerpc variants (32bit 
and 64 bit) do not have WITH_META_MODE as an option as things are set up.

I had been hoping to cut down on the time for clang-related rebuilds during 
native buildworld runs on my slower buildworld contexts (armv7a/cortex-a7, 
powerpc, powerpc64). But it was not to be.

It appears that, once some arm variants are officially tier 1, WITH_META_MODE 
will not span all tier 1 platforms.

[Since I tend to use non-tier-1 platforms I tend to notice some of the 
statements about FreeBSD that are true of only tier 1 without being explicit 
about it. But initially it takes some research to discover that status for each 
such point. WITH_META_MODE is an example.]

===
Mark Millard
markmi at dsl-only.net

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"