Gentoo Archives: gentoo-osx

From: Kito <kito@g.o>
To: gentoo-osx@l.g.o
Subject: Re: [gentoo-osx] [PREFIX] Portage 2.1.6 issues on linux...
Date: Wed, 15 Mar 2006 01:05:40
Message-Id: A2D4D098-7055-4D8C-A332-E63C145790F0@gentoo.org
In Reply to: [gentoo-osx] [PREFIX] Portage 2.1.6 issues on linux... by m h
1 On Mar 14, 2006, at 5:57 PM, m h wrote:
2
3 > This is probably configure issues...
4 >
5 > I'm installing portage 2.1.6 on RHEL4 using the following configure:
6 > ./configure --prefix=${PREFIX} --with-user=`whoami`
7 > --with-group=${GROUP} --sysconfdir=${PREFIX}/etc
8 > --with-rootuser=`whoami` --with-rootuid=`id -u`
9 > --with-offset-prefix=${PREFIX}
10 >
11 > After that I have a stab at a linux prefix profile that I link
12 > etc/make.profile to. I also update etc/make.conf and add PREFIX to it
13 > (and set PORTDIR=${PREFIX}/usr/portage).
14 >
15
16 Ok, with that snapshot, you can try setting the ROOTPATH variable in
17 make.conf something like:
18
19 ROOTPATH=/path/to/bash:/path/to/gcc:$PATH
20
21 That *might* work, but I was having trouble with it on solaris last
22 night. exg and/or I are going to refactor the PATH handling again to
23 make this work a little smoother. The variable name will change to
24 just DEFAULT_PATH in the next snapshot ( hooray for disregarding
25 backwards compatibility :p )
26
27 If that doesn't work, you can also try editing the DEFAULT_PATH line
28 in portage.py directly.
29
30 Another hack I thought of was autoconf'ing make.globals and use
31 macros to find the paths to all tools needed
32 (gcc,ld,as,ar,findutils,etc.etc.). This should make getting portage
33 running very easy on most systems.
34
35 --Kito
36
37
38
39
40 --
41 gentoo-osx@g.o mailing list

Replies

Subject Author
Re: [gentoo-osx] [PREFIX] Portage 2.1.6 issues on linux... Michael Haubenwallner <michael.haubenwallner@×××××××.at>