Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
emerge portage required EAPI -1, supported EAPI 0, jam fix?
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Gentoo on Alternative Architectures
View previous topic :: View next topic  
Author Message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Tue Nov 17, 2009 9:26 am    Post subject: emerge portage required EAPI -1, supported EAPI 0, jam fix? Reply with quote

hello
i am using a mips.little-endian machine
i can't find any updated stage3 for class1-little-endian, and i have the following situation


Code:
# emerge -p portage

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

Calculating dependencies /
!!! All ebuilds that could satisfy ">=dev-lang/python-2.5" have been masked.
!!! One of the following masked packages is required to complete your request:
- dev-lang/python-2.6.2-r1 (masked by: required EAPI -1, supported EAPI 0)
- dev-lang/python-3.1.1 (masked by: required EAPI -1, supported EAPI 0)
- dev-lang/python-2.5.4-r3 (masked by: required EAPI -1, supported EAPI 0)

For more information, see MASKED PACKAGES section in the emerge man page or
refer to the Gentoo Handbook.
(dependency required by "sys-apps/portage-2.1.6.13" [ebuild])


hot to fix the jam ?


Last edited by ddc on Thu Nov 19, 2009 9:48 pm; edited 1 time in total
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31342
Location: 56N 3W

PostPosted: Tue Nov 17, 2009 8:24 pm    Post subject: Reply with quote

ddc,

What has happened is that your portage is so old, it does not understand EAPI-1, meanwhile the python ebuilds have moved on to require EAPI-1. This leaves you without a straight forward upgrade path.

Sometime in the past there was a Python ebuild that worked with EAPI-0. Its no longer in the tree but it will be in the Gentoo Python Attic

Likewise you need to get a newer version of portage than you have but older than the one on the tree and do an update in steps.

Do you know how to use these old ebuilds ?
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Tue Nov 17, 2009 9:10 pm    Post subject: Reply with quote

yeah, the stage3 is 2007.1, there is no other stage3 for mips1-little-endian since then
so ... i am in the jam: how to emerge a new portage if it depends on python-2.5 that is not eabi-0 ?

i really have to find a lucky portage older then the one in the tree but newer than the sys-apps/portage-2.1.1-r2 i have

what about trying to manually compile a newer python-2.5.4-r3?
if i have success i will update the /var/dp/pkg/dev-lanf/python ... then i could emerge a newer emerge portage

it's amazing work, so any better idea ?
elseway, which portage do you suggest ? 2008? where to find it ?


on this mips system i have
* sys-libs/db-4.2.52_p4-r2
* sys-apps/portage-2.1.1-r2
* dev-lang/python-2.4.4-r5
* gcc-4.1.2/binutils-2.17


Last edited by ddc on Thu Nov 19, 2009 9:47 pm; edited 2 times in total
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31342
Location: 56N 3W

PostPosted: Tue Nov 17, 2009 9:27 pm    Post subject: Reply with quote

ddc,

There are Python ebuilds in the attic that will build with your portage.
With a newer Python, you can build a newer portage that does understand EAPI-0.

Most users went through this upgrade without noticing. Its onlu an issue now for installs that have not been updated in over a year.

Choose a Python ebuild out of the attic that is newer then the one you have and older than the ones in the tree.
Copy it to your overlay, if you have one. Add it to your tree if not.
Run
Code:
ebuild </path/to/Python.ebuild> digest
to create the manifest. The Python sources will be downloaded in this step. You may need to hunt around for them and put them into /usr/portage/distfiles
Now you can emerge your python.

Do the same for portage - get a newer one than the one you have but older than the one in the tree.

Warning:- if you put these old ebuilds into your tree, rather than your overlay, emerge --sync will remove them.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Tue Nov 17, 2009 9:59 pm    Post subject: Reply with quote

yeah, i now about the digest

anyway what do you think about dev-lang/python-2.5.1-r5 ?

(also ebuild digest says "No digest file available and download failed"
/usr/portage/distfiles/python-gentoo-patches-2.5.1-r3.tar.bz2 ...
mmm no file?

http://mirrors.kernel.org/gentoo/distfiles/

python-gentoo-patches-2.3.5-r1.tar.bz2 25-Sep-2006 23:08 9.0K
python-gentoo-patches-2.3.5.tar.bz2 21-Aug-2006 20:08 8.3K
python-gentoo-patches-2.3.6-r4.tar.bz2 24-Oct-2007 22:08 9.9K
python-gentoo-patches-2.3.6-r5.tar.bz2 22-Jan-2008 23:07 11K
python-gentoo-patches-2.3.6-r7.tar.bz2 21-May-2008 08:08 11K
python-gentoo-patches-2.4.4-r3.tar.bz2 11-May-2007 14:08 8.2K
python-gentoo-patches-2.4.4-r4.tar.bz2 24-Oct-2007 22:08 9.3K
python-gentoo-patches-2.4.4-r5.tar.bz2 07-Jan-2008 18:07 9.9K
python-gentoo-patches-2.4.4-r10.tar.bz2 21-May-2008 08:08 11K
python-gentoo-patches-2.4.6.tar.bz2 24-May-2009 03:10 11K
python-gentoo-patches-2.5.4-r2.tar.bz2 21-Aug-2009 02:10 20K
python-gentoo-patches-2.6.2-r2.tar.bz2 15-Nov-2009 04:10 9.7K
python-gentoo-patches-2.6.2-r3.tar.bz2 16-Nov-2009 03:00 9.9K
python-gentoo-patches-2.6.2-r4.tar.bz2 01-Sep-2009 03:00 12K
python-gentoo-patches-2.6.2-r5.tar.bz2 22-Sep-2009 19:00 12K
python-gentoo-patches-2.6.3.tar.bz2 02-Oct-2009 16:10 11K
python-gentoo-patches-2.6.4.tar.bz2 30-Oct-2009 12:10 11K
python-gentoo-patches-2.7_pre.tar.bz2 01-Nov-2009 23:00 10K

)
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Wed Nov 18, 2009 1:08 pm    Post subject: Reply with quote

emerge sys-apps/portage

what does the following mean?

>>> Install portage-2.1.6.13 into /var/tmp/portage/portage-2.1.6.13/image/ category sys-apps
patching file make.conf
QA Notice: USE Flag 'userland_GNU' not in IUSE for sys-apps/portage-2.1.6.13
>>> Completed installing portage-2.1.6.13 into /var/tmp/portage/portage-2.1.6.13/image/

man:
gzipping man page: portage.5
gzipping man page: xpak.5
gzipping man page: color.map.5
gzipping man page: make.conf.5
gzipping man page: ebuild.5
gzipping man page: dispatch-conf.1
gzipping man page: etc-update.1
gzipping man page: quickpkg.1
gzipping man page: ebuild.1
gzipping man page: egencache.1
gzipping man page: emaint.1
gzipping man page: emerge.1
gzipping man page: repoman.1
gzipping man page: env-update.1
strip: mipsel-unknown-linux-gnu-strip --strip-unneeded
>>> Merging sys-apps/portage-2.1.6.13 to /
--- /etc/
--- /etc/logrotate.d/
>>> /etc/logrotate.d/._cfg0000_elog-save-summary
--- /etc/portage/
cycle
>>> /etc/portage/.keep_sys-apps_portage-0
>>> /etc/etc-update.conf
>>> /etc/._cfg0001_dispatch-conf.conf
--- /usr/
--- /usr/lib/
--- /usr/lib/portage/
--- /usr/lib/portage/bin/
>>> /usr/lib/portage/bin/portageq
>>> /usr/lib/portage/bin/emerge-webrsync
>>> /usr/lib/portage/bin/xpak
>>> /usr/lib/portage/bin/md5check.py
>>> /usr/lib/portage/bin/isolated-functions.sh
>>> /usr/lib/portage/bin/chkcontents
>>> /usr/lib/portage/bin/filter-bash-environment.py
>>> /usr/lib/portage/bin/quickpkg
>>> /usr/lib/portage/bin/repoman
>>> /usr/lib/portage/bin/check-implicit-pointer-usage.py
>>> /usr/lib/portage/bin/env-update
>>> /usr/lib/portage/bin/regenworld
>>> /usr/lib/portage/bin/pkgname
>>> /usr/lib/portage/bin/pemerge.py
>>> /usr/lib/portage/bin/emaint
>>> /usr/lib/portage/bin/ebuild-helpers/
>>> /usr/lib/portage/bin/ebuild-helpers/fperms
>>> /usr/lib/portage/bin/ebuild-helpers/newlib.a
>>> /usr/lib/portage/bin/ebuild-helpers/portageq -> ../portageq
>>> /usr/lib/portage/bin/ebuild-helpers/newenvd
>>> /usr/lib/portage/bin/ebuild-helpers/doinfo
>>> /usr/lib/portage/bin/ebuild-helpers/dosym
>>> /usr/lib/portage/bin/ebuild-helpers/newsbin
>>> /usr/lib/portage/bin/ebuild-helpers/emake
>>> /usr/lib/portage/bin/ebuild-helpers/prepstrip
>>> /usr/lib/portage/bin/ebuild-helpers/ecompressdir
>>> /usr/lib/portage/bin/ebuild-helpers/dobin
>>> /usr/lib/portage/bin/ebuild-helpers/newexe
>>> /usr/lib/portage/bin/ebuild-helpers/newconfd
>>> /usr/lib/portage/bin/ebuild-helpers/dohard
>>> /usr/lib/portage/bin/ebuild-helpers/newlib.so
>>> /usr/lib/portage/bin/ebuild-helpers/doexe
>>> /usr/lib/portage/bin/ebuild-helpers/prepall
>>> /usr/lib/portage/bin/ebuild-helpers/dosbin
>>> /usr/lib/portage/bin/ebuild-helpers/dodir
>>> /usr/lib/portage/bin/ebuild-helpers/doins
>>> /usr/lib/portage/bin/ebuild-helpers/dolib
>>> /usr/lib/portage/bin/ebuild-helpers/prepallstrip
>>> /usr/lib/portage/bin/ebuild-helpers/doman
>>> /usr/lib/portage/bin/ebuild-helpers/dodoc
>>> /usr/lib/portage/bin/ebuild-helpers/newins
>>> /usr/lib/portage/bin/ebuild-helpers/dolib.so
>>> /usr/lib/portage/bin/ebuild-helpers/prepallman
>>> /usr/lib/portage/bin/ebuild-helpers/dolib.a
>>> /usr/lib/portage/bin/ebuild-helpers/ecompress
>>> /usr/lib/portage/bin/ebuild-helpers/elog
>>> /usr/lib/portage/bin/ebuild-helpers/doconfd
>>> /usr/lib/portage/bin/ebuild-helpers/dosed
>>> /usr/lib/portage/bin/ebuild-helpers/doinitd
>>> /usr/lib/portage/bin/ebuild-helpers/prepman
>>> /usr/lib/portage/bin/ebuild-helpers/newdoc
>>> /usr/lib/portage/bin/ebuild-helpers/newinitd
>>> /usr/lib/portage/bin/ebuild-helpers/dohtml
>>> /usr/lib/portage/bin/ebuild-helpers/die
>>> /usr/lib/portage/bin/ebuild-helpers/prepinfo
>>> /usr/lib/portage/bin/ebuild-helpers/prepallinfo
>>> /usr/lib/portage/bin/ebuild-helpers/newbin
>>> /usr/lib/portage/bin/ebuild-helpers/doenvd
>>> /usr/lib/portage/bin/ebuild-helpers/preplib
>>> /usr/lib/portage/bin/ebuild-helpers/newman
>>> /usr/lib/portage/bin/ebuild-helpers/eqawarn -> elog
>>> /usr/lib/portage/bin/ebuild-helpers/prepalldocs
>>> /usr/lib/portage/bin/ebuild-helpers/fowners
>>> /usr/lib/portage/bin/ebuild-helpers/domo
>>> /usr/lib/portage/bin/banned-helper
>>> /usr/lib/portage/bin/clean_locks
>>> /usr/lib/portage/bin/env-update.sh
>>> /usr/lib/portage/bin/etc-update
>>> /usr/lib/portage/bin/find-requires
>>> /usr/lib/portage/bin/md5check.sh
>>> /usr/lib/portage/bin/dispatch-conf
>>> /usr/lib/portage/bin/fixpackages
>>> /usr/lib/portage/bin/fixdbentries
>>> /usr/lib/portage/bin/archive-conf
>>> /usr/lib/portage/bin/emerge
>>> /usr/lib/portage/bin/ebuild
>>> /usr/lib/portage/bin/egencache
>>> /usr/lib/portage/bin/ebuild.sh
>>> /usr/lib/portage/bin/misc-functions.sh
--- /usr/lib/portage/pym/
>>> /usr/lib/portage/pym/repoman/
>>> /usr/lib/portage/pym/repoman/checks.py
>>> /usr/lib/portage/pym/repoman/utilities.py
>>> /usr/lib/portage/pym/repoman/__init__.py
>>> /usr/lib/portage/pym/repoman/errors.py
>>> /usr/lib/portage/pym/_emerge/
>>> /usr/lib/portage/pym/_emerge/__init__.py
>>> /usr/lib/portage/pym/_emerge/help.py
>>> /usr/lib/portage/pym/portage/
>>> /usr/lib/portage/pym/portage/_sets/
>>> /usr/lib/portage/pym/portage/_sets/profiles.py
>>> /usr/lib/portage/pym/portage/_sets/files.py
>>> /usr/lib/portage/pym/portage/_sets/__init__.py
>>> /usr/lib/portage/pym/portage/_sets/base.py
>>> /usr/lib/portage/pym/portage/news.py
>>> /usr/lib/portage/pym/portage/_selinux.py
>>> /usr/lib/portage/pym/portage/mail.py
>>> /usr/lib/portage/pym/portage/const.py
>>> /usr/lib/portage/pym/portage/update.py
>>> /usr/lib/portage/pym/portage/cache/
>>> /usr/lib/portage/pym/portage/cache/sqlite.py
>>> /usr/lib/portage/pym/portage/cache/mappings.py
>>> /usr/lib/portage/pym/portage/cache/ebuild_xattr.py
>>> /usr/lib/portage/pym/portage/cache/anydbm.py
>>> /usr/lib/portage/pym/portage/cache/util.py
>>> /usr/lib/portage/pym/portage/cache/__init__.py
>>> /usr/lib/portage/pym/portage/cache/sql_template.py
>>> /usr/lib/portage/pym/portage/cache/template.py
>>> /usr/lib/portage/pym/portage/cache/flat_hash.py
>>> /usr/lib/portage/pym/portage/cache/fs_template.py
>>> /usr/lib/portage/pym/portage/cache/flat_list.py
>>> /usr/lib/portage/pym/portage/cache/volatile.py
>>> /usr/lib/portage/pym/portage/cache/cache_errors.py
>>> /usr/lib/portage/pym/portage/cache/metadata_overlay.py
>>> /usr/lib/portage/pym/portage/cache/metadata.py
>>> /usr/lib/portage/pym/portage/util.py
>>> /usr/lib/portage/pym/portage/__init__.py
>>> /usr/lib/portage/pym/portage/tests/
>>> /usr/lib/portage/pym/portage/tests/util/
>>> /usr/lib/portage/pym/portage/tests/util/test_stackDicts.py
>>> /usr/lib/portage/pym/portage/tests/util/test_uniqueArray.py
>>> /usr/lib/portage/pym/portage/tests/util/__init__.py
>>> /usr/lib/portage/pym/portage/tests/util/test_stackDictList.py
>>> /usr/lib/portage/pym/portage/tests/util/test_normalizedPath.py
>>> /usr/lib/portage/pym/portage/tests/util/test_varExpand.py
>>> /usr/lib/portage/pym/portage/tests/util/test_stackLists.py
>>> /usr/lib/portage/pym/portage/tests/util/test_grabdict.py
>>> /usr/lib/portage/pym/portage/tests/xpak/
>>> /usr/lib/portage/pym/portage/tests/xpak/__init__.py
>>> /usr/lib/portage/pym/portage/tests/xpak/test_decodeint.py
>>> /usr/lib/portage/pym/portage/tests/versions/
>>> /usr/lib/portage/pym/portage/tests/versions/__init__.py
>>> /usr/lib/portage/pym/portage/tests/versions/test_vercmp.py
>>> /usr/lib/portage/pym/portage/tests/__init__.py
>>> /usr/lib/portage/pym/portage/tests/runTests
>>> /usr/lib/portage/pym/portage/tests/news/
>>> /usr/lib/portage/pym/portage/tests/news/__init__.py
>>> /usr/lib/portage/pym/portage/tests/news/test_NewsItem.py
>>> /usr/lib/portage/pym/portage/tests/bin/
>>> /usr/lib/portage/pym/portage/tests/bin/__init__.py
>>> /usr/lib/portage/pym/portage/tests/bin/test_dodir.py
>>> /usr/lib/portage/pym/portage/tests/bin/test_dobin.py
>>> /usr/lib/portage/pym/portage/tests/bin/setup_env.py
>>> /usr/lib/portage/pym/portage/tests/env/
>>> /usr/lib/portage/pym/portage/tests/env/config/
>>> /usr/lib/portage/pym/portage/tests/env/config/__init__.py
>>> /usr/lib/portage/pym/portage/tests/env/config/test_PackageUseFile.py
>>> /usr/lib/portage/pym/portage/tests/env/config/test_PackageMaskFile.py
>>> /usr/lib/portage/pym/portage/tests/env/config/test_PortageModulesFile.py
>>> /usr/lib/portage/pym/portage/tests/env/config/test_PackageKeywordsFile.py
>>> /usr/lib/portage/pym/portage/tests/env/__init__.py
>>> /usr/lib/portage/pym/portage/tests/dep/
>>> /usr/lib/portage/pym/portage/tests/dep/test_dep_getslot.py
>>> /usr/lib/portage/pym/portage/tests/dep/test_get_operator.py
>>> /usr/lib/portage/pym/portage/tests/dep/test_match_from_list.py
>>> /usr/lib/portage/pym/portage/tests/dep/__init__.py
>>> /usr/lib/portage/pym/portage/tests/dep/test_use_reduce.py
>>> /usr/lib/portage/pym/portage/tests/dep/test_src_uri.py
>>> /usr/lib/portage/pym/portage/tests/dep/test_isjustname.py
>>> /usr/lib/portage/pym/portage/tests/dep/test_isvalidatom.py
>>> /usr/lib/portage/pym/portage/tests/dep/test_dep_getusedeps.py
>>> /usr/lib/portage/pym/portage/tests/dep/test_dep_getcpv.py
>>> /usr/lib/portage/pym/portage/tests/ebuild/
>>> /usr/lib/portage/pym/portage/tests/ebuild/__init__.py
>>> /usr/lib/portage/pym/portage/tests/ebuild/test_spawn.py
>>> /usr/lib/portage/pym/portage/tests/process/
>>> /usr/lib/portage/pym/portage/tests/process/__init__.py
>>> /usr/lib/portage/pym/portage/tests/process/test_poll.py
>>> /usr/lib/portage/pym/portage/dep.py
>>> /usr/lib/portage/pym/portage/checksum.py
>>> /usr/lib/portage/pym/portage/cvstree.py
>>> /usr/lib/portage/pym/portage/data.py
>>> /usr/lib/portage/pym/portage/proxy/
>>> /usr/lib/portage/pym/portage/proxy/objectproxy.py
>>> /usr/lib/portage/pym/portage/proxy/__init__.py
>>> /usr/lib/portage/pym/portage/proxy/lazyimport.py
>>> /usr/lib/portage/pym/portage/locks.py
>>> /usr/lib/portage/pym/portage/env/
>>> /usr/lib/portage/pym/portage/env/loaders.py
>>> /usr/lib/portage/pym/portage/env/__init__.py
>>> /usr/lib/portage/pym/portage/env/config.py
>>> /usr/lib/portage/pym/portage/env/validators.py
>>> /usr/lib/portage/pym/portage/manifest.py
>>> /usr/lib/portage/pym/portage/elog/
>>> /usr/lib/portage/pym/portage/elog/messages.py
>>> /usr/lib/portage/pym/portage/elog/filtering.py
>>> /usr/lib/portage/pym/portage/elog/mod_custom.py
>>> /usr/lib/portage/pym/portage/elog/mod_save.py
>>> /usr/lib/portage/pym/portage/elog/mod_echo.py
>>> /usr/lib/portage/pym/portage/elog/mod_mail_summary.py
>>> /usr/lib/portage/pym/portage/elog/__init__.py
>>> /usr/lib/portage/pym/portage/elog/mod_save_summary.py
>>> /usr/lib/portage/pym/portage/elog/mod_syslog.py
>>> /usr/lib/portage/pym/portage/elog/mod_mail.py
>>> /usr/lib/portage/pym/portage/dispatch_conf.py
>>> /usr/lib/portage/pym/portage/versions.py
>>> /usr/lib/portage/pym/portage/xpak.py
>>> /usr/lib/portage/pym/portage/localization.py
>>> /usr/lib/portage/pym/portage/process.py
>>> /usr/lib/portage/pym/portage/dbapi/
>>> /usr/lib/portage/pym/portage/dbapi/__init__.py
>>> /usr/lib/portage/pym/portage/dbapi/porttree.py
>>> /usr/lib/portage/pym/portage/dbapi/vartree.py
>>> /usr/lib/portage/pym/portage/dbapi/bintree.py
>>> /usr/lib/portage/pym/portage/dbapi/virtual.py
>>> /usr/lib/portage/pym/portage/output.py
>>> /usr/lib/portage/pym/portage/debug.py
>>> /usr/lib/portage/pym/portage/exception.py
>>> /usr/lib/portage/pym/portage/getbinpkg.py
>>> /usr/lib/portage/pym/portage/eclass_cache.py
>>> /usr/lib/portage/pym/portage_exec.py
>>> /usr/lib/portage/pym/portage_compat_namespace.py
>>> /usr/lib/portage/pym/getbinpkg.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/eclass_cache.py -> portage_compat_namespace.py
--- /usr/sbin/
>>> /usr/sbin/emerge-webrsync -> ../lib/portage/bin/emerge-webrsync
>>> /usr/sbin/quickpkg -> ../lib/portage/bin/quickpkg
>>> /usr/sbin/update-etc -> etc-update
>>> /usr/sbin/env-update -> ../lib/portage/bin/env-update
>>> /usr/sbin/regenworld -> ../lib/portage/bin/regenworld
>>> /usr/sbin/emaint -> ../lib/portage/bin/emaint
>>> /usr/sbin/etc-update -> ../lib/portage/bin/etc-update
>>> /usr/sbin/dispatch-conf -> ../lib/portage/bin/dispatch-conf
>>> /usr/sbin/fixpackages -> ../lib/portage/bin/fixpackages
>>> /usr/sbin/archive-conf -> ../lib/portage/bin/archive-conf
>>> /usr/sbin/update-env -> env-update
--- /usr/bin/
>>> /usr/bin/portageq -> ../lib/portage/bin/portageq
>>> /usr/bin/xpak -> ../lib/portage/bin/xpak
>>> /usr/bin/repoman -> ../lib/portage/bin/repoman
>>> /usr/bin/emerge -> ../lib/portage/bin/emerge
>>> /usr/bin/ebuild -> ../lib/portage/bin/ebuild
>>> /usr/bin/egencache -> ../lib/portage/bin/egencache
--- /usr/share/
>>> /usr/share/portage/
>>> /usr/share/portage/config/
>>> /usr/share/portage/config/make.globals
>>> /usr/share/portage/config/make.conf.example
--- /usr/share/doc/
>>> /usr/share/doc/portage-2.1.6.13/
>>> /usr/share/doc/portage-2.1.6.13/ChangeLog.gz
>>> /usr/share/doc/portage-2.1.6.13/RELEASE-NOTES.gz
>>> /usr/share/doc/portage-2.1.6.13/NEWS.gz
--- /usr/share/man/
--- /usr/share/man/man5/
>>> /usr/share/man/man5/color.map.5.gz
>>> /usr/share/man/man5/xpak.5.gz
>>> /usr/share/man/man5/ebuild.5.gz
>>> /usr/share/man/man5/portage.5.gz
>>> /usr/share/man/man5/make.conf.5.gz
--- /usr/share/man/man1/
>>> /usr/share/man/man1/egencache.1.gz
>>> /usr/share/man/man1/env-update.1.gz
>>> /usr/share/man/man1/dispatch-conf.1.gz
>>> /usr/share/man/man1/ebuild.1.gz
>>> /usr/share/man/man1/emaint.1.gz
>>> /usr/share/man/man1/emerge.1.gz
>>> /usr/share/man/man1/repoman.1.gz
>>> /usr/share/man/man1/etc-update.1.gz
>>> /usr/share/man/man1/quickpkg.1.gz
>>> /etc/make.globals -> ../usr/share/portage/config/make.globals
>>> /usr/lib/portage/bin/ebuild-helpers/einfo -> elog
>>> /usr/lib/portage/bin/ebuild-helpers/ewarn -> elog
>>> /usr/lib/portage/bin/ebuild-helpers/eerror -> elog
>>> /usr/lib/portage/pym/portage_data.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_const.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_checksum.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_localization.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_news.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/cvstree.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/emergehelp.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_debug.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_mail.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_dep.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_selinux.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_manifest.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/dispatch_conf.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_update.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/xpak.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_gpg.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_locks.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_versions.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/output.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_util.py -> portage_compat_namespace.py
>>> /usr/lib/portage/pym/portage_exception.py -> portage_compat_namespace.py
* Byte compiling python modules for python-2.5 .. ... [ ok ]
*
* For help with using portage please consult the Gentoo Handbook
* at http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3
*
*
* In portage-2.1.6, the default behavior has changed for `emerge world`
* and `emerge system` commands. These commands will reinstall all
* packages from the given set unless an option such as --noreplace,
* --update, or --newuse is specified.
*
* File collision protection is now enabled by default via make.globals
* with FEATURES=protect-owned. If you want to disable collision
* protection completely (not recommended), then you need to ensure
* that neither protect-owned nor collision-protect are enabled.
*
>>> Regenerating /etc/ld.so.cache...
>>> sys-apps/portage-2.1.6.13 merged.
Traceback (most recent call last):
File "/usr/bin/emerge", line 4049, in <module>

File "/usr/bin/emerge", line 4044, in emerge_main

File "/usr/bin/emerge", line 3584, in action_build

File "/usr/bin/emerge", line 2048, in merge

File "/usr/lib/portage/pym/portage.py", line 3017, in doebuild
vartree=vartree, prev_mtimes=prev_mtimes)
File "/usr/lib/portage/pym/portage.py", line 3236, in merge
mydbapi=mydbapi, prev_mtimes=prev_mtimes)
File "/usr/lib/portage/pym/portage.py", line 6424, in merge
cleanup=cleanup, mydbapi=mydbapi, prev_mtimes=prev_mtimes)
File "/usr/lib/portage/pym/portage.py", line 6112, in treewalk
elog_process(self.mycpv, self.settings)
File "/usr/lib/portage/pym/portage.py", line 404, in elog_process
msgfunction, msgtype = f.split(".")
ValueError: need more than 1 value to unpack
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31342
Location: 56N 3W

PostPosted: Wed Nov 18, 2009 8:27 pm    Post subject: Reply with quote

ddc,
Code:
>>> Regenerating /etc/ld.so.cache...
>>> sys-apps/portage-2.1.6.13 merged.
means portage built correctly but the install phase failed.

I don't know portage well enough to say why or what to do about it.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Wed Nov 18, 2009 10:38 pm    Post subject: Reply with quote

rb532b ~ # myemerge-log

(*) myemerge's log @ rb532b
--------------------------------------------
2009-11-17--23:00 - emerge dev-lang/python <--- it is the lash in the tree, hacked ebuild
2009-11-18--***** - emerge dev-util/ccache
2009-11-18--***** - emerge sys-apps/portage <--- it is the last in the tree
2009-11-18--***** - emerge app-admin/procinfo
2009-11-18--15-13 - emerge app-portage/gentoolkit
2009-11-18--20-06 - emerge app-shells/bash
2009-11-18--20-23 - emerge sys-apps/coreutils <--- it needs app-arch/lzma-utils
2009-11-18--21-30 - emerge sys-apps/util-linux <--- it needs app-arch/lzma-utils
2009-11-18--21-36 - emerge app-arch/lzma-utils <--- configure: error: cannot run C++ compiled programs.
2009-11-18--21-55 - emerge app-portage/ufed
2009-11-18--22-51 - emerge sys-apps/portage <--- it works but "preprocess_ebuild_env || die "error processing environment"
2009-11-18--23-03 - emerge app-admin/procinfo


"myemerge-log" is a tool i designed in order to log what emerge does, it simply logs what (args[]) you pass to "/bin/emege"


mmm i am now stopped about in emerging app-arch/lzma-utils
---> configure: error: cannot run C++ compiled programs.


rb532b ~ # gcc -v
Quote:
Using built-in specs.
Target: mipsel-unknown-linux-gnu
Configured with: /var/tmp/portage/sys-devel/gcc-4.1.2/work/gcc-4.1.2/configure --prefix=/usr --bindir=/usr/mipsel-unknown-linux-gnu/gcc-bin/4.1.2 --includedir=/usr/lib/gcc/mipsel-unknown-linux-gnu/4.1.2/include --datadir=/usr/share/gcc-data/mipsel-unknown-linux-gnu/4.1.2 --mandir=/usr/share/gcc-data/mipsel-unknown-linux-gnu/4.1.2/man --infodir=/usr/share/gcc-data/mipsel-unknown-linux-gnu/4.1.2/info --with-gxx-include-dir=/usr/lib/gcc/mipsel-unknown-linux-gnu/4.1.2/include/g++-v4 --host=mipsel-unknown-linux-gnu --build=mipsel-unknown-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --enable-secureplt --disable-libunwind-exceptions --disable-multilib --enable-libmudflap --disable-libssp --disable-libgcj --enable-languages=c,c++,treelang,fortran --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix
gcc version 4.1.2 (Gentoo 4.1.2 p1.0.2)



i dunno about the original stage3 i find from radhatter web (the only stage3 i could find about mips-iii-littleendian), i know it is 2007.1 and gcc is 4.1.2 and it has "--enable-languages=c,c++,treelang,fortran"

i dunno about the libc* & friends

i ve now noted that i have no "sys-libs/libstdc++-v3-" installed, so i am emerging it (could it fix?)
the new portage "seems" to be working good, even if it says ""preprocess_ebuild_env || die "error processing environment" (what does it mean ?)




what an amazing work =P
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31342
Location: 56N 3W

PostPosted: Thu Nov 19, 2009 7:16 pm    Post subject: Reply with quote

ddc,

For your C++ error, check
Code:
gcc-config -l
reselect a gcc and run the command it tells you.

Another possibility is your CXXFLAGS.

What is your profile set to?
Code:
preprocess_ebuild_env || die "error processing environment
maybe because you have a profile set that has been removed from the tree. Look at
Code:
eselect profile list

_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Thu Nov 19, 2009 9:36 pm    Post subject: Reply with quote

Quote:

gcc-config -l


re-set to gcc-4.1.2, that is the choice 1, the only one compiler installed
also i had already source /etc/profile

as you can see i emerged a lot of ebuils

Quote:

Another possibility is your CXXFLAGS.


ummm, this is the /etc/make.conf for my mips1 machine

Quote:
ARCH="mips"

CFLAGS="-O2 -mabi=32 -pipe -mips1"
CXXFLAGS="-O2 -mabi=32 -pipe -mips1"

CHOST="mipsel-unknown-linux-gnu"

USE="apache2 berkdb bzip2 cobalt fortran gdbm gpm gzip2 libwww mips ncurses
nls nptl nptlonly pam perl python readline sdl slang ssl tcpd -isdnlog
-sandbox"

ARCH="mips"

ACCEPT_KEYWORDS="mips ppc"
# ~mips"

# Sandbox is broken on mips (Bug #45814)
FEATURES="-sandbox ccache autoconfig"





Quote:

profile been removed from the tree


no, ls -l /etc/make.profile is not brokern
i am using my profile cause mips is ~mips

my profile is based on default-linux/mips/2007.1-dev/cobalt/o32
(as you can see reading this forum, i do not trust newer profiles for mips)




i wrote easy tests for C and C++, see https://forums.gentoo.org/viewtopic-t-803267.html
C (-> gcc) is working
C++ (-> g++) is not, i see "symbol lookup error: /usr/lib/gcc/mipsel-unknown-linux-gnu/4.1.2/libgcc_s.so.1: undefined symbol: GCC_3.0, version GCC_3.0"
Back to top
View user's profile Send private message
NeddySeagoon
Administrator
Administrator


Joined: 05 Jul 2003
Posts: 31342
Location: 56N 3W

PostPosted: Fri Nov 20, 2009 3:26 pm    Post subject: Reply with quote

ddc,

Try to
Code:
emerge dev-util/lafilefixer
and run
Code:
lafilefixer --justfixit


... but I don't know why gcc-4.x.x is looking for gcc-3.x.x libs.

As you say, everything else looks ok
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Back to top
View user's profile Send private message
ddc
Guru
Guru


Joined: 29 Aug 2006
Posts: 527

PostPosted: Fri Nov 27, 2009 12:21 pm    Post subject: Reply with quote

yeahhh, thank you, this finally fixed all the issues !

i have a pretty updated system & world now: i am very happy cause i can emerge everything i need for my project

thank you for your help =)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo on Alternative Architectures All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum