Re: devdmatch: Can't read linker file.

While making kldxref(8) crossarch-capable would be the best solution, it's also the most time consuming. The kldxref rc script doesn't do anything if the linker.hints file already exists, so it shouldn't be much of a problem. 2018-03-14 17:39 GMT+00:00 Warner Losh : > I wouldn't. It make read-o

Re: devdmatch: Can't read linker file.

I wouldn't. It make read-only root a pain in the back side Better to fix kldxref to be a build tool that can cope. And it isn't something that needs to be done on every boot. On Wed, Mar 14, 2018 at 11:05 AM, Edward Napierala wrote: > Hm. Perhaps we should make kldxref_enable default to YE

Re: devdmatch: Can't read linker file.

Hm. Perhaps we should make kldxref_enable default to YES by default on all platforms, then? The overhead is pretty much none when it has nothing to do - it won't try to recreate the linker.hints if it already exists. 2018-03-14 17:01 GMT+00:00 Steve Wills : > FWIW, I ran into this issue on an i

Re: devdmatch: Can't read linker file.

FWIW, I ran into this issue on an i386 image I built from an amd64 host using poudriere and poudriere image. Steve On 03/13/2018 14:44, Warner Losh wrote: Makes sense. I'd forgotten that kldxref can't do cross-platform stuff One could arrange to build it targeting arch X but running on the

Re: devdmatch: Can't read linker file.

Makes sense. I'd forgotten that kldxref can't do cross-platform stuff One could arrange to build it targeting arch X but running on the native host and fix things that way. Nobody has care enough to do that, though perhaps this gives us a use case for why one might want to try. Warner On Tue,

Re: devdmatch: Can't read linker file.

> On 13 Mar 2018, at 19:12, Edward Napierala wrote: > > I think it's only needed for kernels that are cross-built. That's due to > kldxref(8) being unable to handle kernels for other architectures. > my case exactly. > 2018-03-13 13:34 GMT+00:00 Warner Losh >: > I wo

Re: devdmatch: Can't read linker file.

I think it's only needed for kernels that are cross-built. That's due to kldxref(8) being unable to handle kernels for other architectures. 2018-03-13 13:34 GMT+00:00 Warner Losh : > I wonder why that isn't the default, or why the linker.hints isn't at least > created by the make installkernel s

Re: devdmatch: Can't read linker file.

I wonder why that isn't the default, or why the linker.hints isn't at least created by the make installkernel step... Warner On Tue, Mar 13, 2018 at 2:40 AM, Edward Tomasz Napierała wrote: > FWIW, it seems to be a common problem, see https://reviews.freebsd.org/ > D14534. > > On 0312T1027, Warn

Re: devdmatch: Can't read linker file.

FWIW, it seems to be a common problem, see https://reviews.freebsd.org/D14534. On 0312T1027, Warner Losh wrote: > Well, is there a /boot/kernel/linker.hints? > > Warner > > On Mon, Mar 12, 2018 at 9:56 AM, Daniel Braniss wrote: > > > Hi, > > the above i get on arm/nanopi-neo. (it’s the only pl

Re: devdmatch: Can't read linker file.

> On 12 Mar 2018, at 18:27, Warner Losh wrote: > > Well, is there a /boot/kernel/linker.hints? > no, but that was enough to do a grep and the run kldxref. thanks, danny PS: just remembered: reach out and grep someone > Warner > > On Mon, Mar 12, 2018 at 9:56 AM, Daniel Braniss

Re: devdmatch: Can't read linker file.

Well, is there a /boot/kernel/linker.hints? Warner On Mon, Mar 12, 2018 at 9:56 AM, Daniel Braniss wrote: > Hi, > the above i get on arm/nanopi-neo. (it’s the only platform I run current > :-) > > cheers, > danny > > ___ freebsd-current@freebs

devdmatch: Can't read linker file.

Hi, the above i get on arm/nanopi-neo. (it’s the only platform I run current :-) cheers, danny ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-curr