| 1 |
On Mar 15, 2006, at 3:36 PM, m h wrote: |
| 2 |
|
| 3 |
> So I tried using Kito's solaris configure code this morning. I don't |
| 4 |
> think it changed much. |
| 5 |
> |
| 6 |
|
| 7 |
First thing is the ${PREFIX}/etc/make.profile symlink is invalid, |
| 8 |
note the `!` . |
| 9 |
|
| 10 |
> Here's my emerge --info: |
| 11 |
> $ emerge --info |
| 12 |
> !!! Problem with sandbox binary. Disabling... |
| 13 |
> |
| 14 |
> !!! Relying on the shell to locate gcc, this may break |
| 15 |
> !!! DISTCC, installing gcc-config and setting your current gcc |
| 16 |
> !!! profile will fix this |
| 17 |
> Portage 2.1.6 (!/home/spike/portage/portage-alt-prefix/profiles/ |
| 18 |
> linux/x86/fc3, |
| 19 |
> gcc-3.4.3, unavailable, 2.6.9-5.EL i686) |
| 20 |
> ================================================================= |
| 21 |
> System uname: 2.6.9-5.EL i686 i686 |
| 22 |
> Unknown Host Operating System |
| 23 |
> dev-lang/python: [Not Present] |
| 24 |
> sys-apps/sandbox: [Not Present] |
| 25 |
> sys-devel/autoconf: [Not Present] |
| 26 |
> sys-devel/automake: [Not Present] |
| 27 |
> sys-devel/binutils: [Not Present] |
| 28 |
> sys-devel/libtool: [Not Present] |
| 29 |
> sys-devel/odcctools: [Not Present] |
| 30 |
> virtual/os-headers: [Not Present] |
| 31 |
> ACCEPT_KEYWORDS="x86" |
| 32 |
> AUTOCLEAN="yes" |
| 33 |
> CBUILD="i686-pc-linux-gnu" |
| 34 |
> CFLAGS="-O2 -mcpu=i686 -pipe" |
| 35 |
> CHOST="i686-pc-linux-gnu" |
| 36 |
> CONFIG_PROTECT="/etc /tmp/Mar15/etc /usr/kde/2/share/config |
| 37 |
> /usr/kde/3/share/config /usr/share/config /var/qmail/control" |
| 38 |
> CONFIG_PROTECT_MASK="/etc/gconf /tmp/Mar15/etc/env.d" |
| 39 |
> CXXFLAGS="-O2 -mcpu=i686 -pipe" |
| 40 |
> DISTDIR="/tmp/Mar15/usr/portage/distfiles" |
| 41 |
> FEATURES="autoconfig distlocks metadata-transfer sfperms strict" |
| 42 |
> GENTOO_MIRRORS="http://distfiles.gentoo.org |
| 43 |
> http://distro.ibiblio.org/pub/linux/distributions/gentoo" |
| 44 |
> LANG="en_US.UTF-8" |
| 45 |
> PKGDIR="/tmp/Mar15/usr/portage/packages" |
| 46 |
> PORTAGE_TMPDIR="/tmp/Mar15/var/tmp" |
| 47 |
> PORTDIR="/tmp/Mar15/usr/portage" |
| 48 |
> PREFIX="/tmp/Mar15" |
| 49 |
> SYNC="rsync://rsync.gentoo.org/gentoo-portage" |
| 50 |
> USE="x86 berkdb crypt ipv6 ncurses nls pam perl python readline ssl |
| 51 |
> tcpd zlib elibc_glibc kernel_linux userland_GNU" |
| 52 |
> Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LC_ALL, LDFLAGS, |
| 53 |
> LINGUAS, MAKEOPTS, PORTDIR_OVERLAY |
| 54 |
> |
| 55 |
> I have a package.provided containing: |
| 56 |
> |
| 57 |
> dev-lang/python-2.3.4 |
| 58 |
> sys-devel/autoconf-2.59 |
| 59 |
> sys-devel/automake-1.9.2 |
| 60 |
> sys-devel/binutils-2.15.92 |
| 61 |
> sys-devel/libtools-1.5.6 |
| 62 |
> |
| 63 |
> These are the rpm versions of these packages. These versions aren't |
| 64 |
> in the prefix portage tree. What is the correct way to deal with |
| 65 |
> these? |
| 66 |
> |
| 67 |
|
| 68 |
Provided packages don't necessarily need an existing ${PV} in the |
| 69 |
tree, so to start it is usually best to document which versions are |
| 70 |
actually available on the host as opposed to which versions are in |
| 71 |
PORTDIR. Take a look the 'packages' files in other profiles to see |
| 72 |
examples of excluding/including system packages to a profile and |
| 73 |
locking down specific versions. |
| 74 |
|
| 75 |
Also, try the portage-prefix-2.1.10 snapshot, it adds the |
| 76 |
DEFAULT_PATH variable in make.globals, this allows you to set the |
| 77 |
PATH available to portage. It defaults to only ${PREFIX} paths, but |
| 78 |
it can be overridden in the profiles or make.conf. |
| 79 |
|
| 80 |
|
| 81 |
--Kito |
| 82 |
|
| 83 |
|
| 84 |
|
| 85 |
|
| 86 |
-- |
| 87 |
gentoo-osx@g.o mailing list |
Archives