> Well, you define the path to the C compiler, but what "make" wants here > is "make". So you also have to use --define "use_make /cw/bin/make" > or --define "use_make /usr/ccs/bin/make". Usually one does not need > use_make because /usr/ccs/bin/make exists, but in your case (Solaris > Core only) this seems to be missing. BTW, I'm not sure whether Solaris > Core is sufficient for all of OpenPKG's packages. At least we develop > OpenPKG on Solaris "Entire Distribution" boxes. So be warned, it could > be that something is not found later, too.
I tried "use_make" without knowing, but this doesn't help. Only the first make will be called correctly, not the recursive one. I got around the problem in making symbolic links from /bin to /cw/bin/make and /cw/bin/ar (needed later). Compiling gcc-current right now... I have my armored Solaris running with a thoroughly tested OpenPKG 1.3, but for production level I prepare for 2.0. I haven't had any problems right now, but indeed 1.3 packages I built on a "Entire Distribution" box. Now I try to REALLY bootstrap, i.e. build on the same distribution as the running boxes will have. This will be necessary in the future, when we have to upgrade packages in source to quickly fix security problems. Thanks Birger Kr�gelin ------ [EMAIL PROTECTED], Network Operations Center, Karlsruhe ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
