Advanced
Mailing List Archive

Mailing List Archive

  1. Home >
  2. Gentoo>
  3. OSX
[PREFIX] Portage 2.1.6 issues on linux...
sesquile at gmail
Mar 14, 2006, 4:57 PM
Post #1 of 9 (4298 views)
Permalink
This is probably configure issues...

I'm installing portage 2.1.6 on RHEL4 using the following configure:
./configure --prefix=${PREFIX} --with-user=`whoami`
--with-group=${GROUP} --sysconfdir=${PREFIX}/etc
--with-rootuser=`whoami` --with-rootuid=`id -u`
--with-offset-prefix=${PREFIX}

After that I have a stab at a linux prefix profile that I link
etc/make.profile to. I also update etc/make.conf and add PREFIX to it
(and set PORTDIR=${PREFIX}/usr/portage).

Now after setting the path, emerge runs. But I'm getting the following issue:

#emerge -av system
!!! Problem with sandbox binary. Disabling...

These are the packages that would be merged, in order:

Calculating system dependencies
aux_get(): (0) Error in sys-apps/portage-2.1.2-r1 ebuild. (-1)
Check for syntax error or corruption in the ebuild. (--debug)


aux_get(): (0) Error in sys-apps/portage-2.1.4 ebuild. (-1)
Check for syntax error or corruption in the ebuild. (--debug)


aux_get(): (0) Error in sys-apps/portage-2.1.6 ebuild. (-1)
Check for syntax error or corruption in the ebuild. (--debug)


aux_get(): (0) Error in sys-libs/glibc-2.3.5-r2 ebuild. (-1)
Check for syntax error or corruption in the ebuild. (--debug)


aux_get(): (0) Error in app-shells/bash-3.1_p10 ebuild. (-1)
Check for syntax error or corruption in the ebuild. (--debug)


aux_get(): (0) Error in app-shells/bash-3.0-r13 ebuild. (-1)
Check for syntax error or corruption in the ebuild. (--debug)

.....
snip snip
....


aux_get(): (0) Error in sys-libs/readline-5.0-r2 ebuild. (-1)
Check for syntax error or corruption in the ebuild. (--debug)


!!! Packages for the following atoms are either all
!!! masked or don't exist:
>=sys-apps/portage-2.0.53.03 virtual/libc app-shells/bash sys-devel/libtool dev-
lang/perl sys-apps/texinfo sys-apps/findutils sys-devel/make sys-apps/sed app-ar
ch/bzip2 sys-apps/which app-arch/tar sys-devel/patch sys-devel/autoconf-wrapper
sys-devel/flex sys-apps/groff sys-apps/grep net-misc/rsync app-arch/cpio virtual
/pager virtual/baselayout sys-devel/automake-wrapper virtual/ssh sys-devel/gcc s
ys-apps/diffutils virtual/os-headers sys-apps/gawk sys-devel/bison sys-libs/zlib
net-misc/wget sys-apps/file virtual/gzip sys-apps/coreutils sys-libs/ncurses sy
s-devel/m4 virtual/editor sys-devel/gnuconfig sys-apps/debianutils net-misc/iput
ils sys-libs/readline

... done!

Total size of downloads: 0 kB

Nothing to merge; do you want me to auto-clean packages? [Yes/No] n
'

I'm using the latest prefix aware tree that I can find (the nightlies
that kito is posting).

Any hints

thanks

matt

--
gentoo-osx@gentoo.org mailing list
Re: [PREFIX] Portage 2.1.6 issues on linux... [ In reply to ]
ferringb at gmail
Mar 14, 2006, 5:53 PM
Post #2 of 9 (4224 views)
Permalink
Bet you don't
On Tue, Mar 14, 2006 at 03:57:24PM -0800, m h wrote:
> This is probably configure issues...
>
> I'm installing portage 2.1.6 on RHEL4 using the following configure:
> ./configure --prefix=${PREFIX} --with-user=`whoami`
> --with-group=${GROUP} --sysconfdir=${PREFIX}/etc
> --with-rootuser=`whoami` --with-rootuid=`id -u`
> --with-offset-prefix=${PREFIX}
>
> After that I have a stab at a linux prefix profile that I link
> etc/make.profile to. I also update etc/make.conf and add PREFIX to it
> (and set PORTDIR=${PREFIX}/usr/portage).

Do you actually have a usable bash within the prefix? If not, kito
will have to comment on disabling path strictness...

~harring
Re: [PREFIX] Portage 2.1.6 issues on linux... [ In reply to ]
kito at gentoo
Mar 14, 2006, 6:04 PM
Post #3 of 9 (4222 views)
Permalink
On Mar 14, 2006, at 5:57 PM, m h wrote:

> This is probably configure issues...
>
> I'm installing portage 2.1.6 on RHEL4 using the following configure:
> ./configure --prefix=${PREFIX} --with-user=`whoami`
> --with-group=${GROUP} --sysconfdir=${PREFIX}/etc
> --with-rootuser=`whoami` --with-rootuid=`id -u`
> --with-offset-prefix=${PREFIX}
>
> After that I have a stab at a linux prefix profile that I link
> etc/make.profile to. I also update etc/make.conf and add PREFIX to it
> (and set PORTDIR=${PREFIX}/usr/portage).
>

Ok, with that snapshot, you can try setting the ROOTPATH variable in
make.conf something like:

ROOTPATH=/path/to/bash:/path/to/gcc:$PATH

That *might* work, but I was having trouble with it on solaris last
night. exg and/or I are going to refactor the PATH handling again to
make this work a little smoother. The variable name will change to
just DEFAULT_PATH in the next snapshot ( hooray for disregarding
backwards compatibility :p )

If that doesn't work, you can also try editing the DEFAULT_PATH line
in portage.py directly.

Another hack I thought of was autoconf'ing make.globals and use
macros to find the paths to all tools needed
(gcc,ld,as,ar,findutils,etc.etc.). This should make getting portage
running very easy on most systems.

--Kito




--
gentoo-osx@gentoo.org mailing list
Re: [PREFIX] Portage 2.1.6 issues on linux... [ In reply to ]
sesquile at gmail
Mar 14, 2006, 6:06 PM
Post #4 of 9 (4217 views)
Permalink
On 3/14/06, Brian Harring <ferringb@gmail.com> wrote:
> Bet you don't
> On Tue, Mar 14, 2006 at 03:57:24PM -0800, m h wrote:
> > This is probably configure issues...
> >
> > I'm installing portage 2.1.6 on RHEL4 using the following configure:
> > ./configure --prefix=${PREFIX} --with-user=`whoami`
> > --with-group=${GROUP} --sysconfdir=${PREFIX}/etc
> > --with-rootuser=`whoami` --with-rootuid=`id -u`
> > --with-offset-prefix=${PREFIX}
> >
> > After that I have a stab at a linux prefix profile that I link
> > etc/make.profile to. I also update etc/make.conf and add PREFIX to it
> > (and set PORTDIR=${PREFIX}/usr/portage).
>
> Do you actually have a usable bash within the prefix? If not, kito
> will have to comment on disabling path strictness...
>

I'm using the native bash and prepending the
$PREFIX/bin:$PREFIX/usr/bin:$PREFIX/sbin:$PREFIX/usr/sbin to it....

--
gentoo-osx@gentoo.org mailing list
Re: [PREFIX] Portage 2.1.6 issues on linux... [ In reply to ]
kito at gentoo
Mar 14, 2006, 6:08 PM
Post #5 of 9 (4216 views)
Permalink
On Mar 14, 2006, at 7:06 PM, m h wrote:

> On 3/14/06, Brian Harring <ferringb@gmail.com> wrote:
>> Bet you don't
>> On Tue, Mar 14, 2006 at 03:57:24PM -0800, m h wrote:
>>> This is probably configure issues...
>>>
>>> I'm installing portage 2.1.6 on RHEL4 using the following configure:
>>> ./configure --prefix=${PREFIX} --with-user=`whoami`
>>> --with-group=${GROUP} --sysconfdir=${PREFIX}/etc
>>> --with-rootuser=`whoami` --with-rootuid=`id -u`
>>> --with-offset-prefix=${PREFIX}
>>>
>>> After that I have a stab at a linux prefix profile that I link
>>> etc/make.profile to. I also update etc/make.conf and add PREFIX
>>> to it
>>> (and set PORTDIR=${PREFIX}/usr/portage).
>>
>> Do you actually have a usable bash within the prefix? If not, kito
>> will have to comment on disabling path strictness...
>>
>
> I'm using the native bash and prepending the
> $PREFIX/bin:$PREFIX/usr/bin:$PREFIX/sbin:$PREFIX/usr/sbin to it....

I you are only doing this in your env it won't work. Portage will
automatically cleanse the PATHs to include the $PREFIX.

>
> --
> gentoo-osx@gentoo.org mailing list
>

--Kito




--
gentoo-osx@gentoo.org mailing list
Re: [PREFIX] Portage 2.1.6 issues on linux... [ In reply to ]
sesquile at gmail
Mar 14, 2006, 6:17 PM
Post #6 of 9 (4215 views)
Permalink
> >
> > I'm using the native bash and prepending the
> > $PREFIX/bin:$PREFIX/usr/bin:$PREFIX/sbin:$PREFIX/usr/sbin to it....
>
> I you are only doing this in your env it won't work. Portage will
> automatically cleanse the PATHs to include the $PREFIX.
>
>
Thanks. I put it in portage_const.py
Now I'm getting:
$ emerge -av system
!!! Problem with sandbox binary. Disabling...


These are the packages that would be merged, in order:

Calculating system dependencies /
aux_get(): (0) Error in sys-devel/patch-2.5.9-r1 ebuild. (-1)
Check for syntax error or corruption in the ebuild. (--debug)


!!! All ebuilds that could satisfy "sys-devel/patch" have been masked.
!!! One of the following masked packages is required to complete your request:

aux_get(): (0) Error in sys-devel/patch-2.5.9-r1 ebuild. (-1)
Check for syntax error or corruption in the ebuild. (--debug)

Traceback (most recent call last):
File "/tmp/Mar10/bin/emerge", line 3184, in ?
if not mydepgraph.xcreate(myaction):
File "/tmp/Mar10/bin/emerge", line 1395, in xcreate
if not self.select_dep(portage.root, mydep, raise_on_missing=True):
File "/tmp/Mar10/bin/emerge", line 1323, in select_dep
if not self.create(myk,myparent,"--onlydeps" not in
myopts,myuse=binpkguseflags):
File "/tmp/Mar10/bin/emerge", line 1020, in create
if not self.select_dep("/",mydep["/"],myparent=mp,myuse=myuse):
File "/tmp/Mar10/bin/emerge", line 1318, in select_dep
if not self.create(myk,myparent,myuse=binpkguseflags):
File "/tmp/Mar10/bin/emerge", line 1020, in create
if not self.select_dep("/",mydep["/"],myparent=mp,myuse=myuse):
File "/tmp/Mar10/bin/emerge", line 1318, in select_dep
if not self.create(myk,myparent,myuse=binpkguseflags):
File "/tmp/Mar10/bin/emerge", line 1020, in create
if not self.select_dep("/",mydep["/"],myparent=mp,myuse=myuse):
File "/tmp/Mar10/bin/emerge", line 1263, in select_dep
mreasons = portage.getmaskingstatus(p)
File "/tmp/Mar10/lib/portage/pym/portage.py", line 3633, in getmaskingstatus
mygroups, eapi = portdb.aux_get(mycpv, ["KEYWORDS", "EAPI"])
File "/tmp/Mar10/lib/portage/pym/portage.py", line 4895, in aux_get
raise KeyError

....

--
gentoo-osx@gentoo.org mailing list
Re: [PREFIX] Portage 2.1.6 issues on linux... [ In reply to ]
kito at gentoo
Mar 14, 2006, 7:01 PM
Post #7 of 9 (4203 views)
Permalink
On Mar 14, 2006, at 7:17 PM, m h wrote:

>>>
>>> I'm using the native bash and prepending the
>>> $PREFIX/bin:$PREFIX/usr/bin:$PREFIX/sbin:$PREFIX/usr/sbin to it....
>>
>> I you are only doing this in your env it won't work. Portage will
>> automatically cleanse the PATHs to include the $PREFIX.
>>
>>
> Thanks. I put it in portage_const.py
> Now I'm getting:
> $ emerge -av system


Try just starting with `emerge --info` first. Its still not finding
the basic utils.

> !!! Problem with sandbox binary. Disabling...
>
>
> These are the packages that would be merged, in order:
>
> Calculating system dependencies /
> aux_get(): (0) Error in sys-devel/patch-2.5.9-r1 ebuild. (-1)
> Check for syntax error or corruption in the ebuild.
> (--debug)
>
>
> !!! All ebuilds that could satisfy "sys-devel/patch" have been masked.
> !!! One of the following masked packages is required to complete
> your request:
>
> aux_get(): (0) Error in sys-devel/patch-2.5.9-r1 ebuild. (-1)
> Check for syntax error or corruption in the ebuild.
> (--debug)
>
> Traceback (most recent call last):
> File "/tmp/Mar10/bin/emerge", line 3184, in ?
> if not mydepgraph.xcreate(myaction):
> File "/tmp/Mar10/bin/emerge", line 1395, in xcreate
> if not self.select_dep(portage.root, mydep,
> raise_on_missing=True):
> File "/tmp/Mar10/bin/emerge", line 1323, in select_dep
> if not self.create(myk,myparent,"--onlydeps" not in
> myopts,myuse=binpkguseflags):
> File "/tmp/Mar10/bin/emerge", line 1020, in create
> if not self.select_dep("/",mydep["/"],myparent=mp,myuse=myuse):
> File "/tmp/Mar10/bin/emerge", line 1318, in select_dep
> if not self.create(myk,myparent,myuse=binpkguseflags):
> File "/tmp/Mar10/bin/emerge", line 1020, in create
> if not self.select_dep("/",mydep["/"],myparent=mp,myuse=myuse):
> File "/tmp/Mar10/bin/emerge", line 1318, in select_dep
> if not self.create(myk,myparent,myuse=binpkguseflags):
> File "/tmp/Mar10/bin/emerge", line 1020, in create
> if not self.select_dep("/",mydep["/"],myparent=mp,myuse=myuse):
> File "/tmp/Mar10/bin/emerge", line 1263, in select_dep
> mreasons = portage.getmaskingstatus(p)
> File "/tmp/Mar10/lib/portage/pym/portage.py", line 3633, in
> getmaskingstatus
> mygroups, eapi = portdb.aux_get(mycpv, ["KEYWORDS", "EAPI"])
> File "/tmp/Mar10/lib/portage/pym/portage.py", line 4895, in aux_get
> raise KeyError
>
> ....
>
> --
> gentoo-osx@gentoo.org mailing list
>

--Kito




--
gentoo-osx@gentoo.org mailing list
Re: [PREFIX] Portage 2.1.6 issues on linux... [ In reply to ]
kito at gentoo
Mar 14, 2006, 7:24 PM
Post #8 of 9 (4211 views)
Permalink
On Mar 14, 2006, at 5:57 PM, m h wrote:

> This is probably configure issues...
>
> I'm installing portage 2.1.6 on RHEL4 using the following configure:
> ./configure --prefix=${PREFIX} --with-user=`whoami`
> --with-group=${GROUP} --sysconfdir=${PREFIX}/etc
> --with-rootuser=`whoami` --with-rootuid=`id -u`
> --with-offset-prefix=${PREFIX}
>

I would probably try:

./configure --prefix=${PREFIX}/usr --with-offset-prefix=${PREFIX} \
--with-user=`whoami` --with-group=`id -g` \
--with-rootuser=`whoami` --with-rootuid=`id -un` \
--with-wheelgroup=`id -g` --with-wheelgid=`id -gn`

I used exactly this last night using 2.1.6 on solaris nv31a and it
worked.

--Kito




--
gentoo-osx@gentoo.org mailing list
Re: [PREFIX] Portage 2.1.6 issues on linux... [ In reply to ]
michael.haubenwallner at salomon
Mar 15, 2006, 1:24 AM
Post #9 of 9 (4218 views)
Permalink
Hi all,

have just installed 2.1.6 on a rhel-as4 for interest, though won't have
time yet to do real work on it - however, some cents from me:

On Tue, 2006-03-14 at 19:04 -0600, Kito wrote:
<snip>
>
> ROOTPATH=/path/to/bash:/path/to/gcc:$PATH

for bash, i quickly did a softlink: PREFIX/usr/bin/bash -> /bin/bash

> Another hack I thought of was autoconf'ing make.globals and use
> macros to find the paths to all tools needed
> (gcc,ld,as,ar,findutils,etc.etc.). This should make getting portage
> running very easy on most systems.

In my first implementation, i did some similar in isolated-functions.sh:
For each coreutil/diffutil/findutil/grep/patch i added a
shell-wrapper-function, which calls the real executable with an absolute
path identified by configure, having some fallbacks if configured paths
are out of date.

Setting a PATH to them might be the better idea for the toolchain, but
having a bash-function xargs(), calling '/path/to/gxargs -r' (identified
by configure), 'xargs -r' or 'xargs' (as fallbacks) instead of having a
variable $XARGS looks also nice to me...

Same for egrep ('grep -E', 'egrep'), fgrep and others...

Well, the xargs() function will work for 'find | xargs', but fex egrep()
will not work within 'find -exec egrep {} \;' ...

Also for bash and python i used autoconf'd '@CU_BASH@' and '@PYTHON@'
(substituted while installing) in the first line of the scripts.

-- haubi

--
gentoo-osx@gentoo.org mailing list

©2024 GT.net. A Gossamer Threads company.
5th Floor, 455 Granville St., Vancouver, BC V6C 1T1, Canada | Legal