Gentoo Archives: gentoo-osx

From: m h <sesquile@×××××.com>
To: gentoo-osx@l.g.o
Subject: Re: [gentoo-osx] [PREFIX] portage 2.1.11 bootstraping script
Date: Mon, 20 Mar 2006 18:39:34
In Reply to: Re: [gentoo-osx] [PREFIX] portage 2.1.11 bootstraping script by Kito
On 3/18/06, Kito <kito@g.o> wrote:

> > cd $PORTCODE > > #./configure --prefix=${PREFIX} --with-user=`whoami` > > --with-group=${GROUP} --sysconfdir=${PREFIX}/etc > > --with-rootuser=`whoami` --with-rootuid=`id -u` > > --with-offset-prefix=${PREFIX} > > Why this first configure with the bad ${PREFIX} option? >
debugging. I was trying different options to try and get things working...
> > ./configure --prefix=${PREFIX}/usr --with-user=`whoami` > > --with-group=${GROUP} --sysconfdir=${PREFIX}/etc > > --with-rootuser=`whoami` --with-rootuid=`id -u` > > --with-offset-prefix=${PREFIX} --with-wheelgroup=${GROUP} > > --with-wheelgid=`id -g` > > make > > make install > > > > cd ${PREFIX} > > mkdir -p usr/portage > > cp -r ${TREE}/* usr/portage > > > > export PATH=${PREFIX}/usr/bin:${PREFIX}/usr/sbin:${PATH} > > Keep in mind, setting the PATH in the shell is only for your benefit > and has no effect on the PATHs available to portage. Be sure to set > this using the DEFAULT_PATH var in make.conf or your profile.
Yep. I know that and am setting DEFAULT_PATH
> > > > > mkdir etc > > cp ${PORTCODE}/cnf/make.conf etc/ > > > > Ok, if you are having to manually create ${PREFIX}/etc, the make > install target of portage is failing. Can you run make install again > and log it and/or watch very carefully what is getting installed and > where?
etc/portage is being created.
> > > #SET PREFIX in make.conf > > #PREPEND PREFIX TO A FEW PLACES > > > > mkdir -p ${PREFIX}/etc/portage > > > > This directory should also have been created during make install. >
This directory is NOT being created! Going throught the output of configure, make, make install, the only (somewhat troubling) thing I can see is this: make[2]: Leaving directory `/home/spike/portage/portage-prefix-2.1.11/pym' Making install in cnf make[2]: Entering directory `/home/spike/portage/portage-prefix-2.1.11/cnf' /usr/bin/install -c -d -m 755 -o spike -g spike /tmp/Mar20/etc Portage does not have an arch-specific configuration for this arch. Please notify the arch maintainer about this issue. Using generic. /bin/sh ..//subst-install --installcmd='/usr/bin/install -c -o spike -g spike -m 644' ./make.globals /tmp/Mar20/etc/make.globals /bin/sh ..//subst-install --installcmd='/usr/bin/install -c -o spike -g spike -m 644' ./make.conf /tmp/Mar20/etc/make.conf.example /bin/sh ..//subst-install --installcmd='/usr/bin/install -c -o spike -g spike -m 644' ./etc-update.conf /tmp/Mar20/etc/etc-update.conf /bin/sh ..//subst-install --installcmd='/usr/bin/install -c -o spike -g spike -m 644' ./dispatch-conf.conf /tmp/Mar20/etc/dispatch-conf.conf make[2]: Leaving directory `/home/spike/portage/portage-prefix-2.1.11/cnf' The Makefile in the "cnf" directory is looking for a make.globals.x86 file which isn't there. This seems like the only fishy thing I can spot. Note that there was nothing written to stderr, and no warnings or error other than that above. -- gentoo-osx@g.o mailing list