1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 <2008> 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 <2008> 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Build Question |
From: | Susanna Jacobson <[email protected]> |
To: | [email protected] |
Date: | Thu, 07 Aug 2008 12:10:54 -0700 |
Andrew Johnson wrote: ...
You might be able to use some kind of overlay filesystem to provide the local writable directories; Linux has this capability, and I believe Solaris does too but I don't know how to set one up.
I'm building for 3 different architectures, and I'd like to put the EPICS source on a single (hopefully!) write protected NFS server, and link to it when I need access to build, but would rather not have the client machine writing directories on the server if I can get away with it.
Unfortunately we didn't design the EPICS build system for that particular model; the model we *did* design for is the one where your install directories are elsewhere, but in our model the build hosts have to be able to write to the source filesystem. If you don't want to allow writes to the NFS filesystem it might be simpler to have three separate copies of the source code (which you could copy or rsync off the NFS server).
- Andrew
-- ======================================================================== Susanna Jacobson MS 7-222 [email protected] Lawrence Berkeley National Laboratory VOICE: (510) 486-7801 1 Cyclotron Road FAX: (510) 486-7374 Berkeley, CA 94720-8225 ========================================================================