Thanks. Do I need to use that tag when cloning slim_source? The copy I got was (I assumed) the newest and the README had different packages listed although I hadn't specified a tag while cloning (it lists more IPS packages, but probably they didn't all actually exist yet hence my problem).
Chad On Mon, Jul 26, 2010 at 07:53:35AM -0700, Keith Mitchell wrote: > Hi Chad, > > There are a number of packages that are required dependencies of > building slim_source - they're documented in usr/src/README: > http://src.opensolaris.org/source/xref/caiman/slim_source/usr/src/README#38 > > Depending on which build you're currently running and which repos > you have access to, some of those packages may not be available in > IPS format. SVR4 versions are available in that case from > http://dlc.sun.com/osol/install/downloads/current/ > (See the an older revision of the README for more info: > http://src.opensolaris.org/source/xref/caiman/slim_source/usr/src/README?r=687%3Aaffa28c47b7a) > > - Keith > > On 07/24/10 06:39 PM, Chad Cantwell wrote: > >Hi, > > > >Sorry if this is a lame question, but I'm trying to compile slim_source so I > >can use distro-const to create an snv 145 bootable CD for recovery purposes > >(I > >don't need it now but I'd like to be able to create bootable CDs of new > >builds > >so I can upgrade zfs and zpool versions without losing simple access to them > >from CD in case it's needed later). I couldn't use the older packaged > >version > >because of a liblogsvc bug (Bug 16104 - liblogsvc needs to explicitly link to > >the libraries it uses) but for all I know that version might have only worked > >on build 134 regardless. Anyway, I have slim_source from the mercurial > >repository, and the sunstudio compilers. The problem I'm having is that > >while > >compiling it is looking for several .h files that are only in the build > >directory for ON 145. The first of which is instzones_api.h. On my system > >it is in > >/work/compiling/onnv-b145/proto/root_i386-nd/usr/include/instzones_api.h > >but the nightly.log for slim_source only has the following: > > > >/opt/sunstudio12.1/bin/cc -xc99=%none -O -Xa > >-I/work/compiling/slim_source/proto/root_i386/usr/include -I/usr/include > >-I/usr/include/python2.6 > >-I/work/compiling/slim_source/proto/root_i386/usr/include -I/usr/include > >-I/work/compiling/slim_source/proto/root_i386/usr/include -I/usr/include > >-I/usr/include/python2.6 > >-I/work/compiling/slim_source/proto/root_i386/usr/include -I/usr/include -c > >-o objs/i386/be_activate.o be_activate.c > >"libbe_priv.h", line 32: cannot find include file:<instzones_api.h> > >"libbe_priv.h", line 185: warning: old-style declaration or incorrect type > >for: zoneBrandList_t > >"libbe_priv.h", line 185: syntax error before or at: * > >"libbe_priv.h", line 185: warning: old-style declaration or incorrect type > >for: be_get_supported_brandlist > >"be_activate.c", line 169: undefined symbol: GLOBAL_ZONEID > >"be_activate.c", line 974: undefined symbol: zoneList_t > >"be_activate.c", line 974: syntax error before or at: zone_list > >"be_activate.c", line 975: undefined symbol: brands > >"be_activate.c", line 975: syntax error before or at: = > >"be_activate.c", line 976: warning: declaration can not follow a statement > >"be_activate.c", line 977: warning: declaration can not follow a statement > >"be_activate.c", line 978: warning: declaration can not follow a statement > >"be_activate.c", line 986: warning: improper pointer/integer combination: op > >"=" > >"be_activate.c", line 1023: undefined symbol: zone_list > >"be_activate.c", line 1037: undefined symbol: ZONE_STATE_INSTALLED > >"be_activate.c", line 1040: warning: improper pointer/integer combination: > >op "=" > >cc: acomp failed for be_activate.c > >*** Error code 1 > > > > > >I'm not sure what I did wrong. Should I have copied the header files from my > >145 build somewhere else on my system, or is there a variable in > >developer.sh to > >point to them where they are now? Or, am I somehow supposed to be compiling > >slim_source in the same directory as the on_build so it's root_i386 directory > >would match up with that from the onnv-b145 directory? > > > >Thanks, > >Chad Cantwell > > > >_______________________________________________ > >caiman-discuss mailing list > >[email protected] > >http://mail.opensolaris.org/mailman/listinfo/caiman-discuss > _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
