| 1 |
On 3/18/06, Kito <kito@g.o> wrote: |
| 2 |
|
| 3 |
> > cd $PORTCODE |
| 4 |
> > #./configure --prefix=${PREFIX} --with-user=`whoami` |
| 5 |
> > --with-group=${GROUP} --sysconfdir=${PREFIX}/etc |
| 6 |
> > --with-rootuser=`whoami` --with-rootuid=`id -u` |
| 7 |
> > --with-offset-prefix=${PREFIX} |
| 8 |
> |
| 9 |
> Why this first configure with the bad ${PREFIX} option? |
| 10 |
> |
| 11 |
|
| 12 |
debugging. I was trying different options to try and get things working... |
| 13 |
|
| 14 |
> > ./configure --prefix=${PREFIX}/usr --with-user=`whoami` |
| 15 |
> > --with-group=${GROUP} --sysconfdir=${PREFIX}/etc |
| 16 |
> > --with-rootuser=`whoami` --with-rootuid=`id -u` |
| 17 |
> > --with-offset-prefix=${PREFIX} --with-wheelgroup=${GROUP} |
| 18 |
> > --with-wheelgid=`id -g` |
| 19 |
> > make |
| 20 |
> > make install |
| 21 |
> > |
| 22 |
> > cd ${PREFIX} |
| 23 |
> > mkdir -p usr/portage |
| 24 |
> > cp -r ${TREE}/* usr/portage |
| 25 |
> > |
| 26 |
> > export PATH=${PREFIX}/usr/bin:${PREFIX}/usr/sbin:${PATH} |
| 27 |
> |
| 28 |
> Keep in mind, setting the PATH in the shell is only for your benefit |
| 29 |
> and has no effect on the PATHs available to portage. Be sure to set |
| 30 |
> this using the DEFAULT_PATH var in make.conf or your profile. |
| 31 |
|
| 32 |
Yep. I know that and am setting DEFAULT_PATH |
| 33 |
|
| 34 |
> |
| 35 |
> > |
| 36 |
> > mkdir etc |
| 37 |
> > cp ${PORTCODE}/cnf/make.conf etc/ |
| 38 |
> > |
| 39 |
> |
| 40 |
> Ok, if you are having to manually create ${PREFIX}/etc, the make |
| 41 |
> install target of portage is failing. Can you run make install again |
| 42 |
> and log it and/or watch very carefully what is getting installed and |
| 43 |
> where? |
| 44 |
|
| 45 |
etc/portage is being created. |
| 46 |
|
| 47 |
> |
| 48 |
> > #SET PREFIX in make.conf |
| 49 |
> > #PREPEND PREFIX TO A FEW PLACES |
| 50 |
> > |
| 51 |
> > mkdir -p ${PREFIX}/etc/portage |
| 52 |
> > |
| 53 |
> |
| 54 |
> This directory should also have been created during make install. |
| 55 |
> |
| 56 |
|
| 57 |
This directory is NOT being created! |
| 58 |
|
| 59 |
Going throught the output of configure, make, make install, the only |
| 60 |
(somewhat troubling) thing I can see is this: |
| 61 |
|
| 62 |
|
| 63 |
make[2]: Leaving directory `/home/spike/portage/portage-prefix-2.1.11/pym' |
| 64 |
Making install in cnf |
| 65 |
make[2]: Entering directory `/home/spike/portage/portage-prefix-2.1.11/cnf' |
| 66 |
/usr/bin/install -c -d -m 755 -o spike -g spike /tmp/Mar20/etc |
| 67 |
|
| 68 |
Portage does not have an arch-specific configuration for this arch. |
| 69 |
Please notify the arch maintainer about this issue. Using generic. |
| 70 |
|
| 71 |
/bin/sh ..//subst-install --installcmd='/usr/bin/install -c -o spike |
| 72 |
-g spike -m 644' ./make.globals /tmp/Mar20/etc/make.globals |
| 73 |
/bin/sh ..//subst-install --installcmd='/usr/bin/install -c -o spike |
| 74 |
-g spike -m 644' ./make.conf /tmp/Mar20/etc/make.conf.example |
| 75 |
/bin/sh ..//subst-install --installcmd='/usr/bin/install -c -o spike |
| 76 |
-g spike -m 644' ./etc-update.conf /tmp/Mar20/etc/etc-update.conf |
| 77 |
/bin/sh ..//subst-install --installcmd='/usr/bin/install -c -o spike |
| 78 |
-g spike -m 644' ./dispatch-conf.conf |
| 79 |
/tmp/Mar20/etc/dispatch-conf.conf |
| 80 |
make[2]: Leaving directory `/home/spike/portage/portage-prefix-2.1.11/cnf' |
| 81 |
|
| 82 |
The Makefile in the "cnf" directory is looking for a make.globals.x86 |
| 83 |
file which isn't there. This seems like the only fishy thing I can |
| 84 |
spot. |
| 85 |
|
| 86 |
Note that there was nothing written to stderr, and no warnings or |
| 87 |
error other than that above. |
| 88 |
|
| 89 |
-- |
| 90 |
gentoo-osx@g.o mailing list |
Archives