Gentoo Archives: gentoo-osx

From: Michael Haubenwallner <michael.haubenwallner@×××××××.at>
To: gentoo-osx@l.g.o
Subject: Re: [gentoo-osx] [PREFIX] Portage 2.1.6 issues on linux...
Date: Wed, 15 Mar 2006 08:25:34
Message-Id: 1142411053.1054.41.camel@sapc154
In Reply to: Re: [gentoo-osx] [PREFIX] Portage 2.1.6 issues on linux... by Kito
1 Hi all,
2
3 have just installed 2.1.6 on a rhel-as4 for interest, though won't have
4 time yet to do real work on it - however, some cents from me:
5
6 On Tue, 2006-03-14 at 19:04 -0600, Kito wrote:
7 <snip>
8 >
9 > ROOTPATH=/path/to/bash:/path/to/gcc:$PATH
10
11 for bash, i quickly did a softlink: PREFIX/usr/bin/bash -> /bin/bash
12
13 > Another hack I thought of was autoconf'ing make.globals and use
14 > macros to find the paths to all tools needed
15 > (gcc,ld,as,ar,findutils,etc.etc.). This should make getting portage
16 > running very easy on most systems.
17
18 In my first implementation, i did some similar in isolated-functions.sh:
19 For each coreutil/diffutil/findutil/grep/patch i added a
20 shell-wrapper-function, which calls the real executable with an absolute
21 path identified by configure, having some fallbacks if configured paths
22 are out of date.
23
24 Setting a PATH to them might be the better idea for the toolchain, but
25 having a bash-function xargs(), calling '/path/to/gxargs -r' (identified
26 by configure), 'xargs -r' or 'xargs' (as fallbacks) instead of having a
27 variable $XARGS looks also nice to me...
28
29 Same for egrep ('grep -E', 'egrep'), fgrep and others...
30
31 Well, the xargs() function will work for 'find | xargs', but fex egrep()
32 will not work within 'find -exec egrep {} \;' ...
33
34 Also for bash and python i used autoconf'd '@CU_BASH@' and '@PYTHON@'
35 (substituted while installing) in the first line of the scripts.
36
37 -- haubi
38
39 --
40 gentoo-osx@g.o mailing list