On 5/31/16 5:17 PM, Simon J. Gerraty wrote:
>> Another reported issue just now is that right after an installworld,
>> everything rebuilds due to changed /bin/sh (-dM flag to make tells you
>> why things rebuild). I'll look into some mitigations for this.
>
> It is probably sufficient to just add
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
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
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_e
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 lo
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 _
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 filem
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 filem
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_e
[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 r301
Bryan Drewery wrote:
> Yup, it's not really simple to fix. This problem defeats the goal of
> the feature too. I had not ran into this case in all of my testing since
> I wasn't installing to /.
I never do that either (except for bmake).
I'm guessing that installworld it is a rare event - compar
On 6/1/2016 10:27 AM, Bryan Drewery wrote:
> On 5/31/2016 5:17 PM, Simon J. Gerraty wrote:
>>> Another reported issue just now is that right after an installworld,
>>> everything rebuilds due to changed /bin/sh (-dM flag to make tells you
>>> why things rebuild). I'll look into some mitigations fo
On 5/31/2016 5:17 PM, Simon J. Gerraty wrote:
>> Another reported issue just now is that right after an installworld,
>> everything rebuilds due to changed /bin/sh (-dM flag to make tells you
>> why things rebuild). I'll look into some mitigations for this.
>
> It is probably sufficient to just a
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:
>
>>
> Another reported issue just now is that right after an installworld,
> everything rebuilds due to changed /bin/sh (-dM flag to make tells you
> why things rebuild). I'll look into some mitigations for this.
It is probably sufficient to just add
.MAKE.META.IGNORE_PATHS += ${__MAKE_SHELL}
__
On 5/31/16 4:51 PM, Bryan Drewery wrote:
> On 5/31/16 4:41 PM, Bryan Drewery wrote:
>> On 5/31/16 4:37 PM, Bryan Drewery wrote:
>>> On 5/31/16 7:06 AM, David Wolfskill wrote:
Kernel build failed (on laptop). But siince the build machine had
succeeded,
I tried "make cleanworld" on t
On 5/31/16 4:41 PM, Bryan Drewery wrote:
> On 5/31/16 4:37 PM, Bryan Drewery wrote:
>> On 5/31/16 7:06 AM, David Wolfskill wrote:
>>> Kernel build failed (on laptop). But siince the build machine had
>>> succeeded,
>>> I tried "make cleanworld" on the laptop, taht re-tried the build... and
>>> it
On 5/31/16 4:37 PM, Bryan Drewery wrote:
> On 5/31/16 7:06 AM, David Wolfskill wrote:
>> Kernel build failed (on laptop). But siince the build machine had succeeded,
>> I tried "make cleanworld" on the laptop, taht re-tried the build... and
>> it worked.
>> --- machine ---
>> machine -> /root/svn/
On 5/31/16 7:06 AM, David Wolfskill wrote:
> Kernel build failed (on laptop). But siince the build machine had succeeded,
> I tried "make cleanworld" on the laptop, taht re-tried the build... and
> it worked.
> --- machine ---
> machine -> /root/svn/base/sys/amd64/include
> ln: machine/include: Fi
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:
>
>> .
On 5/27/2016 5:16 PM, Bryan Drewery wrote:
> To use this you must either add WITH_META_MODE=yes to your environment
> or add it into /etc/src-env.conf (not /etc/src.conf or /etc/make.conf).
> You will also need to load the filemon(4) module with 'kldload filemon'.
You also need to 'make cleanworld
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.
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)
On Fri, May 27, 2016 at 05:16:25PM -0700, Bryan Drewery wrote:
> The way that "meta mode" works is to enable the bmake "meta mode"
> feature that tracks the build command for each target and uses the
> filemon(4) [1] module to track all files read/written/executed for
> building target. If any of
Buildworld/Buildkernel now supports a working incremental build. Using
-DNO_CLEAN is not needed as it is the default with it (there is no
-DCLEAN for it). The normal -DNO_CLEAN feature is broken and risky
since it does not track a ton of the dependencies in the build such as
the compiler, other b
25 matches
Mail list logo
