Re: proper way or unworkable idea ? [SOLVED]

2015-07-23 Thread Jeffrey Bouquet


On Tue, 30 Jun 2015 20:54:07 +0200, Willem Jan Withagen w...@digiware.nl 
wrote:

 On 30/06/2015 17:32, Simon J. Gerraty wrote:
  Jeffrey Bouquet jbt...@iherebuywisely.com wrote:
  
  If I've a spare /mnt/usr/src , it seems buildworld quite soon fails,
  where it otherwise may succeed in /usr/src. Any CLI parameters or the
  build system is hardcoded enough so that there will always be
  problems?
  
  The only thing hard coded is the default MAKEOBJDIRPREFIX (it isn't
  called that but it works the same way), but even that should work for any
  location. I always have MAKEOBJDIRPREFIX when doing buildworld etc,
  and have never used /usr/src.
  
  Is there perhaps something interesting about /mnt/usr/src (like
  ancient?)
 
 On some of the systems where I use different versions, I have
   /usr/srcs
 mounted of the NFS-server. in which I have.
   /usr/srcs/src8/src
   /usr/srcs/src9/src
   /usr/srcs/src10/src
   /usr/srcs/head/src
 
 Then also have /usr/objs mounted, with the same setup
 
 And on the remote systems link /usr/src - /usr/srcs/src??/src and same
 for obj
 
 I have yet to run into trouble when I do the normal things. It gets
 messy if I'd like to build both i386 and amd64 in the same obj-tree.
 That does not always work, but adding a differentiating i386 and amd64
 to the hierarchy seemed to fix it. But I retired all but one i386, and
 that is soon to follow.
 
 --WjW
 
 
 
 
 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Using a r285418 (july 12), rsynced /usr/obj and /usr/src  ( precise howto
found in the motd where I store stuff... cp -Rp that is) 

# cp -Rp /mnt_usr/obj/usr/src /usr/obj/usr  # /usr as a seperate filesystem
  ... note 4  3
# cp -Rp /mnt_usr/src /usr # /usr as a seperate filesystem
 ... note  2  1 

the MAKEOBJDIRPREFIX seems to be working for the first time ever.  Cntl-c'd it 
since
the installkernel/installworld did the upgrade...  so something was fixed.  
Could probably
comtinue with the MAKEOBJDIRPREFIX  buildworld if I was sure (doubly sure) 
how to install from
the different location to the usual one...  without a hitch.  So that may 
come later this
year... unless something else breaks the specific build environment which 
caused this
thread, which appears SOLVED...
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: proper way or unworkable idea ?

2015-06-30 Thread Benjamin Kaduk
On Tue, 30 Jun 2015, John-Mark Gurney wrote:

 Jeffrey Bouquet wrote this message on Mon, Jun 29, 2015 at 04:10 -0700:
  If I've a spare /mnt/usr/src , it seems buildworld quite
  soon fails, where it otherwise may succeed in /usr/src. Any CLI parameters 
  or
  the build system is hardcoded enough so that there will always be problems?

 Doing a buildworld from a source tree not located in /usr/src works
 and I do it all the time...  There is nothing special, simple
 buildworld just works...

Indeed.  There is a slight catch if you want to perform installworld and
the upgrade procedure from that location, namely that the -m argument to
mergemaster is needed, but the buildworld itself just works.

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


Re: proper way or unworkable idea ?

2015-06-30 Thread Simon J. Gerraty
Jeffrey Bouquet jbt...@iherebuywisely.com wrote:

 If I've a spare /mnt/usr/src , it seems buildworld quite soon fails,
 where it otherwise may succeed in /usr/src. Any CLI parameters or the
 build system is hardcoded enough so that there will always be
 problems?

The only thing hard coded is the default MAKEOBJDIRPREFIX (it isn't
called that but it works the same way), but even that should work for any
location. I always have MAKEOBJDIRPREFIX when doing buildworld etc,
and have never used /usr/src.

Is there perhaps something interesting about /mnt/usr/src (like
ancient?)


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


Re: proper way or unworkable idea ?

2015-06-30 Thread Willem Jan Withagen
On 30/06/2015 17:32, Simon J. Gerraty wrote:
 Jeffrey Bouquet jbt...@iherebuywisely.com wrote:
 
 If I've a spare /mnt/usr/src , it seems buildworld quite soon fails,
 where it otherwise may succeed in /usr/src. Any CLI parameters or the
 build system is hardcoded enough so that there will always be
 problems?
 
 The only thing hard coded is the default MAKEOBJDIRPREFIX (it isn't
 called that but it works the same way), but even that should work for any
 location. I always have MAKEOBJDIRPREFIX when doing buildworld etc,
 and have never used /usr/src.
 
 Is there perhaps something interesting about /mnt/usr/src (like
 ancient?)

On some of the systems where I use different versions, I have
/usr/srcs
mounted of the NFS-server. in which I have.
/usr/srcs/src8/src
/usr/srcs/src9/src
/usr/srcs/src10/src
/usr/srcs/head/src

Then also have /usr/objs mounted, with the same setup

And on the remote systems link /usr/src - /usr/srcs/src??/src and same
for obj

I have yet to run into trouble when I do the normal things. It gets
messy if I'd like to build both i386 and amd64 in the same obj-tree.
That does not always work, but adding a differentiating i386 and amd64
to the hierarchy seemed to fix it. But I retired all but one i386, and
that is soon to follow.

--WjW




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


Re: proper way or unworkable idea ?

2015-06-30 Thread John-Mark Gurney
Jeffrey Bouquet wrote this message on Mon, Jun 29, 2015 at 04:10 -0700:
 If I've a spare /mnt/usr/src , it seems buildworld quite
 soon fails, where it otherwise may succeed in /usr/src. Any CLI parameters or 
 the build system is hardcoded enough so that there will always be problems? 

Doing a buildworld from a source tree not located in /usr/src works
and I do it all the time...  There is nothing special, simple
buildworld just works...

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 All that I will do, has been done, All that I have, has not.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


proper way or unworkable idea ?

2015-06-29 Thread Jeffrey Bouquet
If I've a spare /mnt/usr/src , it seems buildworld quite
soon fails, where it otherwise may succeed in /usr/src. Any CLI parameters or 
the build system is hardcoded enough so that there will always be problems? 
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org