| 1 |
Hi, |
| 2 |
|
| 3 |
I've been working in and on AIX since 1988 and have built many open source packages. Recently I wanted a structure to help me out and I discovered Gentoo's Portage and the postfix port of it. What follows is a small log of what I have done so far hoping it will help others in the future. I have a few questions at the end. |
| 4 |
|
| 5 |
I now have three levels in my path. The first is the prefix area e.g. $EPREFIX/bin, the second is a previous area where I put open source packages I'll call $R. This would be like /usr/local in most machines. Then the normal /usr/bin directory. |
| 6 |
|
| 7 |
I am roughly following the sets in the instructions for Solaris but I've hit a few very minor bumps in the road. |
| 8 |
|
| 9 |
First, I put these packages, built by "hand" into my $R area: |
| 10 |
|
| 11 |
> Python-2.7.1 gcc-4.5.0 make-3.82 tar-1.25 |
| 12 |
> bash-4.1 gettext-0.18.1.1 mpc-0.8.2 wget-1.12 |
| 13 |
> expat-2.0.1 gmp-5.0.1 mpfr-2.4.2 |
| 14 |
> gawk-3.1.8 libiconv-1.13.1 sed-4.2.1 |
| 15 |
|
| 16 |
|
| 17 |
This is gmp, mpfr, and mpc to make GCC along with iconv, expat, and gettext. After that, I added wget, bash, and make. I then started to try to do the bootstrap sequence but hit problems with the versions of sed, Python, and gawk so I built those two packages "by hand" in the $R area too. I have copious notes about how these steps were done but I'll post them somewhere else. This list doesn't seem quite the place. |
| 18 |
|
| 19 |
The issue I hit with sed is described here: |
| 20 |
|
| 21 |
http://www.mail-archive.com/hlfs-dev@××××××××××××××××.org/msg01740.html |
| 22 |
|
| 23 |
The issue I hit with gawk is described here: |
| 24 |
|
| 25 |
https://trac.macports.org/ticket/4447 |
| 26 |
|
| 27 |
In both cases, I just pulled down the latest version and built them without incident. Python did not really come close to building in the bootstrap sequence but the latest 2.7.1 builds using an "in tree" build method with the normal configure, make, make install sequence. |
| 28 |
|
| 29 |
I am still progressing through the Solaris bring up instructions. I'm doing the sequence of: emerge --oneshot <xyz> and things are going ok. |
| 30 |
|
| 31 |
My questions: |
| 32 |
|
| 33 |
1) The version of sed and gawk used in the bootstrap are fairly old. I assume they are used because they are "stable" but they did not work for me which is why I got the latest version. I get the idea that Python might fall into the same category. If the latest version was used, it might built and work. Should that be changed or is the boot strap process not really something folks want to spend a great deal of time fixing or modifying? |
| 34 |
|
| 35 |
2) The one really weird thing that happened was I had a new version of sed in my $R area and when I tried to do: |
| 36 |
|
| 37 |
emerge --oneshot sed |
| 38 |
|
| 39 |
somehow, it used the sed from AIX and not the one in my $R area -- despite the fact that it was in the path. This process must somehow modify the PATH briefly. I guess? The way I got around this was adding a symbolic link from the $EPREFIX area to the sed in the $R area. |
| 40 |
|
| 41 |
3) My biggest question, before I get too deep is about binutils. I see it coming up on the todo list. I'm sure that I want to use AIX's ld(1) and as(1). Should I not install binutils? I know this is new territory but thought I would ask for some advice. |
| 42 |
|
| 43 |
Thank you, |
| 44 |
Perry |
Archives