Re: Custom Kernel Fail
On Tue, 2017-08-29 at 19:54 -0400, Monty Chaney-Geib wrote: > I'm getting a failure building a custom kernel on arm64. > > "/usr/src/sys/dev/mii/smcphy.c:49:10: fatal error: 'miidevs.h' file > not > found" > > Let me know what you guys recommend. > -Monty Add "device mii" to your config. -- Ian ___ 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: custom kernel
> >> # diff -u2 /usr/src/Makefile.inc1.orig /usr/src/Makefile.inc1
> >> --- /usr/src/Makefile.inc1.origMon Apr 29 20:42:50 2002
> >> +++ /usr/src/Makefile.inc1 Tue Jun 25 20:05:28 2002
> >> @@ -402,9 +402,10 @@
> >> KRNLCONFDIR= ${KRNLSRCDIR}/${TARGET}/conf
> >> KRNLOBJDIR=${OBJTREE}${KRNLSRCDIR}
> >> +KERNCONFDIR?= ${KRNLCONFDIR}
> I asked only if is possible to back-port to 4.x STABLE tree...
> The whole Makefile.inc1 is very different, but this functionality
> can be obtained with only 3 lines of changes.
I've been using the above for months in -stable, as well as the
native -current functionality, to build kernels with read-only
/usr/src and no config file within (instead off in /usr/local
somewhere), and it's worked great. I've had to reapply the above
patch anytime the -stable Makefile.inc1 changes, so I second the
request that 4.x get the above patch MFC applied to bring its ability
to that of -current for alternative kernel config file locations,
and I can't see that it would cause any problems (I've never
experienced any)
barry bouwsma
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: custom kernel
On Tue, Jun 25, 2002 at 08:14:30PM +0200, Riccardo Torrini wrote:
> # diff -u2 /usr/src/Makefile.inc1.orig /usr/src/Makefile.inc1
> --- /usr/src/Makefile.inc1.origMon Apr 29 20:42:50 2002
> +++ /usr/src/Makefile.inc1 Tue Jun 25 20:05:28 2002
> @@ -402,9 +402,10 @@
> KRNLCONFDIR= ${KRNLSRCDIR}/${TARGET}/conf
> KRNLOBJDIR=${OBJTREE}${KRNLSRCDIR}
> +KERNCONFDIR?= ${KRNLCONFDIR}
Why do we need yet another knob? Why not just ?= KRNLCONFDIR, or default
KERNCONFDIR to ${KRNLSRCDIR}/${TARGET}/conf ?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: custom kernel
On 24-Jun-2002 (11:36:34/GMT) Makoto Matsushita wrote:
>> The only (I think) user configurable file under /usr/src tree is
>> the custom kernel file, pointed by KERNCONF in /etc/make.conf.
> "cd /usr/src; make {build,install}kernel" with
> KERNCONF=YOUR_KERNEL_CFG
> KERNCONFDIR=/path/to/dir/of/YOUR_KERNEL_CFG/file/mentioned/above
> seems working (but I don't test it).
Thanks to all hints (also to who link it out of /usr/src tree).
This one is what I prefer but it doesn't work on -STABLE, can we
back port this 3 lines of diffs also to 4.x ?
# diff -u2 /usr/src/Makefile.inc1.orig /usr/src/Makefile.inc1
--- /usr/src/Makefile.inc1.origMon Apr 29 20:42:50 2002
+++ /usr/src/Makefile.inc1 Tue Jun 25 20:05:28 2002
@@ -402,9 +402,10 @@
KRNLCONFDIR= ${KRNLSRCDIR}/${TARGET}/conf
KRNLOBJDIR=${OBJTREE}${KRNLSRCDIR}
+KERNCONFDIR?= ${KRNLCONFDIR}
BUILDKERNELS=
INSTALLKERNEL=
.for _kernel in ${KERNCONF}
-.if exists(${KRNLCONFDIR}/${_kernel})
+.if exists(${KERNCONFDIR}/${_kernel})
BUILDKERNELS+= ${_kernel}
.if empty(INSTALLKERNEL)
@@ -440,5 +441,6 @@
cd ${KRNLCONFDIR}; \
PATH=${TMPPATH} \
- config ${CONFIGARGS} -d ${KRNLOBJDIR}/${_kernel} ${_kernel}
+ config ${CONFIGARGS} -d ${KRNLOBJDIR}/${_kernel} \
+ ${KERNCONFDIR}/${_kernel}
.endif
.if !defined(NOCLEAN) && !defined(NO_KERNELCLEAN)
Riccardo.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: custom kernel
On Mon, Jun 24, 2002 at 10:29:14PM -0700 I heard the voice of Doug Barton, and lo! it spake thus: > > > > Well, what I do is place symlinks in /usr/src/sys/i386/conf, pointing to > > the "real" kernel config file(s), which are in a different hierarchy, > > and in the "local" part of my CVS repository (vs. the FreeBSD part). > > > > It may be a hack, but it's been a fairly effective one for some time > > now. :-} > > That is also useful if you're prone to do 'rm -rm /usr/src' periodically > :) Indeed. I keep mine in /usr/local/kernel (I sometimes have to copy them over, such as when doing a kernel build over NFS on another box, but life isn't perfect), and I newfs /usr/src and re-co the src tree between builds (nice quick and easy way to cleanup, that). -- Matthew Fuller (MF4839) | [EMAIL PROTECTED] Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet" To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: custom kernel
David Wolfskill wrote: > > >Date: Mon, 24 Jun 2002 10:33:23 +0200 (CEST) > >From: Riccardo Torrini <[EMAIL PROTECTED]> > > >To avoid unwanted removal can we locate that file under any other > >place and point it (also by KERNCONF or some new black magic) with > >full path? Is this possible (or already done) ? > > Well, what I do is place symlinks in /usr/src/sys/i386/conf, pointing to > the "real" kernel config file(s), which are in a different hierarchy, > and in the "local" part of my CVS repository (vs. the FreeBSD part). > > It may be a hack, but it's been a fairly effective one for some time > now. :-} That is also useful if you're prone to do 'rm -rm /usr/src' periodically :) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: custom kernel
>Date: Mon, 24 Jun 2002 10:33:23 +0200 (CEST) >From: Riccardo Torrini <[EMAIL PROTECTED]> >To avoid unwanted removal can we locate that file under any other >place and point it (also by KERNCONF or some new black magic) with >full path? Is this possible (or already done) ? Well, what I do is place symlinks in /usr/src/sys/i386/conf, pointing to the "real" kernel config file(s), which are in a different hierarchy, and in the "local" part of my CVS repository (vs. the FreeBSD part). It may be a hack, but it's been a fairly effective one for some time now. :-} Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill [EMAIL PROTECTED] Trying to support or use Microsoft products makes about as much sense as painting the outside of a house with watercolors. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
