Re: Problem building -current kernel with read-only /usr/src.
hi, there! On Sat, 23 Dec 2000, Chris wrote: Actually, last time I checked, I think stable did not install with a RO /usr/src either. Anyone know if this is still the case? I have no problems with 'make installworld' with RO obj and src on latest -stable /fjoe To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem building -current kernel with read-only /usr/src.
:On Sat, Dec 23, 2000 at 11:24:50AM -0800, Matt Dillon wrote:
:
:I will fix it today.
Works like a charm now, thanks! My -current source is broken out on
my -stable machine, so the only way to compile it is via an NFS mount
to a -current machine which, for obvious reasons, needs to be read-only.
In regards to your commit message backing out the change. I kinda liked
the change (if it could be made to work). What about modifying 'make'
itself to provide a MAKEOBJDIRBASE environment variable in addition
to the MAKEOBJDIRPREFIX environment variable? Kinda messy, but I think
it would work.
What you would do is generate a MAKEOBJDIRBASE environment by running
`pwd` inside /usr/src/sys/compile/BLAH. The make program would adjust
it's use of MAKEOBJDIRPREFIX:
1. ${MAKEOBJDIRPREFIX}/`pwd`
By taking MAKEOBJDIRBASE into account. Specifically, it would take the
`pwd` that *it* runs and it would chop of MAKEOBJDIRBASE, leaving us
with:
${MAKEOBJDIRPREFIX}/(`pwd` with MAKEOBJDIRBASE chopped off at the head)
I believe this would produce the correct path. But it does require
modifying the 'make' program.
The only other alternative is to generate an appropriate MAKEOBJDIR
variable for each module directory. That might require ripping up too
much stuff though.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Problem building -current kernel with read-only /usr/src.
On Sat, Dec 23, 2000 at 12:24:51AM -0800, Matt Dillon wrote: While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got: === 3dfx @ - /FreeBSD/FreeBSD-current/src/sys ln: @: Read-only file system *** Error code 1 Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx. *** Error code 1 It looks like it's trying to mess around with something in /usr/src, which is a read-only NFS mount. Needless to say we do not want to break being able to have a read-only /usr/src! Anyone been messing with the 3dfx module recently ? Myself and a few others found debris in our /usr/src/sys recently. Looks like it might be what you have there. None of us were sure if it was us messing it up or trouble somewhere else. Do a 'make cleandir' in your _source tree_ and try the build again. -- Crist J. Clark [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem building -current kernel with read-only /usr/src.
While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got: === 3dfx @ - /FreeBSD/FreeBSD-current/src/sys ln: @: Read-only file system *** Error code 1 Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx. *** Error code 1 It looks like it's trying to mess around with something in /usr/src, which is a read-only NFS mount. Needless to say we do not want to break being able to have a read-only /usr/src! Anyone been messing with the 3dfx module recently ? All the modules do this. Remove "MODULES_WITH_WORLD" from your /etc/make.conf; they're not compatible with a read-only source tree. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem building -current kernel with read-only /usr/src.
On Sat, Dec 23, 2000 at 12:24:51AM -0800, Matt Dillon wrote: While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got: === 3dfx @ - /FreeBSD/FreeBSD-current/src/sys ln: @: Read-only file system *** Error code 1 Wouldn't using the buildkernel/installkernel targets be more appropriate for a read-only source-tree? -- Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem building -current kernel with read-only /usr/src.
: :On Sat, Dec 23, 2000 at 12:24:51AM -0800, Matt Dillon wrote: : While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got: : : === 3dfx : @ - /FreeBSD/FreeBSD-current/src/sys : ln: @: Read-only file system : *** Error code 1 : : :Wouldn't using the buildkernel/installkernel targets be more appropriate :for a read-only source-tree? : :-- :Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED] Tried using the buildkernel target, doesn't work either. I don't have MODULES_WITH_WORLD set in /etc/make.conf. I tried 'make cleandir' in /usr/src and that does not fix the problem either. Something got broken in the last week or two, it never did this sort of thing before. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem building -current kernel with read-only /usr/src.
: : While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got: : : === 3dfx : @ - /FreeBSD/FreeBSD-current/src/sys : ln: @: Read-only file system : *** Error code 1 : : Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx. : *** Error code 1 : : It looks like it's trying to mess around with something in /usr/src, : which is a read-only NFS mount. Needless to say we do not want to : break being able to have a read-only /usr/src! : : Anyone been messing with the 3dfx module recently ? : :All the modules do this. Remove "MODULES_WITH_WORLD" from your :/etc/make.conf; they're not compatible with a read-only source tree. I've partially tracked it down to the ILINKS target in kmod.mk being run while in the wrong directory. It SHOULD be in /FreeBSD/FreeBSD-current/src/sys/compile/TEST4/modules/3dfx (aka /usr/src/sys/compile/TEST4/modules/3dfx). But instead, when I echo `pwd` in the ILINKS target it appears to be cd'd into the main modules source directory: mv -f .newdep .depend find ../../modules -type d -a ! -name CVS | sed -e "s|../../modules|modules|g" | xargs mkdir -p ; cd ../../modules ; env MAKEOBJDIRPREFIX=/FreeBSD/FreeBSD-current/src/sys/compile/TEST4/modules KMODDIR=/boot/kernel make depend === 3dfx @ - /FreeBSD/FreeBSD-current/src/sys /FreeBSD/FreeBSD-current/src/sys/modules/3dfx ln: @: Read-only file system *** Error code 1 Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx. *** Error code 1 Stop in /FreeBSD/FreeBSD-current/src/sys/modules. This is not right. Someone did something to change the compile dir as of the time the dependancies are run. The cd in the 'find' sequence is correct It looks like someone blew up the making of the object directories under compile/TEST4/modules. Under 4.x I had paths like this: /usr/src/sys/compile/TEST4/modules/FreeBSD/FreeBSD-current/usr/src/sys/modules/tx/ Under -current they are like this: /usr/src/sys/compile/TEST4/modules/tx/... The 'make' program can't find the object module directory any more. Ahh.. so maybe I should remake the make program, eh? Tried that, doesn't work. Whoever 'fixed' object directory creation under /usr/src/sys/compile/BLAH for modules broke it instead. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
found the fragger. Re: Problem building -current kernel with read-only /usr/src.
Ok, I found it. /usr/src/sys/conf/Makefile.i386 is broken. It looks
like either you or David O'Brien (I'm guessing, your guys names are
prominent in the CVS logs but I haven't tracked it down exactly)
screwed up the object directory creation while trying to optimize it.
It looks like it is trying to create short object directory names.
But the make program can't find them when looking for object directories.
This breaks MAKEOBJDIRPREFIX. The 'make' program looks in:
1. ${MAKEOBJDIRPREFIX}/`pwd`
2. ${MAKEOBJDIR}
3. obj.${MACHINE}
4. obj
5. /usr/obj/`pwd`
(taken from the 'make' man page)
And NONE of these is the object path you create in the Makefile.
This causes the make system to revert to tring to create the files
in the source directory rather then the object directory.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: found the fragger. Re: Problem building -current kernel with read-only /usr/src.
On Sat, Dec 23, 2000 at 11:24:50AM -0800, Matt Dillon wrote: like either you or David O'Brien (I'm guessing, your guys names are I will fix it today. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem building -current kernel with read-only /usr/src.
On Sat, Dec 23, 2000 at 09:43:29AM -0800, Matt Dillon wrote: [snip] I tried 'make cleandir' in /usr/src and that does not fix the problem either. Sorry, I was not clear enough. You need to do, # cd /usr/src/sys/modules # make cleandir A 'cleandir' from /usr/src will not climb up into the modules. -- Crist J. Clark [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: found the fragger. Re: Problem building -current kernel with read-only /usr/src.
:I will fix it today. : Thanks a lot Dave! -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem building -current kernel with read-only /usr/src.
Hi, On Sat, Dec 23, 2000 at 09:43:29AM -0800, Matt Dillon wrote: Something got broken in the last week or two, it never did this sort of thing before. David's speedup commits to sys/conf/Makefile.*. I informed him of the problem, and asked him to back out the hacks, but he wants the speedup... Regards, -Jeremy -- FreeBSD - Because the best things in life are free... http://www.freebsd.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem building -current kernel with read-only /usr/src.
Actually, last time I checked, I think stable did not install with a RO /usr/src either. Anyone know if this is still the case? Chris It looks like it's trying to mess around with something in /usr/src, which is a read-only NFS mount. Needless to say we do not want to break being able to have a read-only /usr/src! Anyone been messing with the 3dfx module recently ? -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem building -current kernel with read-only /usr/src.
Actually, last time I checked, I think stable did not install with a RO /usr/src either. Anyone know if this is still the case? I have installed -stable many times with /usr/src mounted readonly via NFS. Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Problem building -current kernel with read-only /usr/src.
: : Actually, last time I checked, I think stable did not install with a RO : /usr/src either. Anyone know if this is still the case? : :I have installed -stable many times with /usr/src mounted readonly :via NFS. : :Steinar Haug, Nethelp consulting, [EMAIL PROTECTED] Yah, -stable is fine. I've done the same. Most recently two days ago. -Matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
