Portage wants to emerge several versions of automake.

Message

blaksaga · Post by **blaksaga** » Tue Jan 25, 2005 5:26 am

alf root # emerge -uDpt world

These are the packages that I would merge, in reverse order:

Calculating world dependencies ...done!
[nomerge      ] sys-apps/man-pages-2.00
[nomerge      ]  sys-apps/man-1.5m-r2
[nomerge      ]   sys-apps/sed-4.0.9
[nomerge      ]    sys-libs/glibc-2.3.4.20040808-r1
[nomerge      ]     sys-devel/gcc-3.3.5-r1
[nomerge      ]      sys-devel/gcc-config-1.3.8-r4
[ebuild     U ]       sys-apps/portage-2.0.51-r15 [2.0.51-r14]
[nomerge      ] x11-terms/xterm-197
[nomerge      ]  sys-apps/utempter-0.5.5.5-r1
[nomerge      ]   app-arch/rpm2targz-9.0-r2
[nomerge      ]    sys-apps/which-2.16
[nomerge      ]        dev-lang/python-2.3.4
[nomerge      ]         dev-lang/tk-8.4.6-r1
[nomerge      ]          x11-base/xorg-x11-6.8.0-r4
[nomerge      ]           x11-misc/ttmkfdir-3.0.9-r2
[ebuild     U ]            sys-devel/libtool-1.5.10-r3 [1.5.2-r7]
[nomerge      ]           sys-apps/util-linux-2.12i-r1
[nomerge      ]            sys-apps/pam-login-3.14
[nomerge      ]             sys-libs/pam-0.77-r1
[ebuild  NS   ]              sys-devel/automake-1.9.4
[ebuild  N    ]               sys-devel/automake-wrapper-1
[ebuild  NS   ]                sys-devel/automake-1.4_p6
[ebuild  NS   ]                sys-devel/automake-1.7.9
[ebuild  NS   ]                sys-devel/automake-1.6.3
[ebuild  NS   ]                sys-devel/automake-1.8.5-r2
[ebuild     UD]                sys-devel/automake-1.5 [1.8.5-r1]
[ebuild     U ]              sys-devel/autoconf-2.59-r6 [2.59-r5]
[ebuild  N    ]               sys-devel/autoconf-wrapper-2
[ebuild  NS   ]                sys-devel/autoconf-2.13
[nomerge      ]         dev-libs/openssl-0.9.7d-r2
[nomerge      ]          dev-lang/perl-5.8.5-r2
[nomerge      ]           sys-libs/db-4.1.25_p1-r4
[ebuild  N    ]            dev-java/blackdown-jdk-1.4.2.01
[ebuild  N    ]            dev-java/blackdown-jre-1.4.2.01

I brought it up on #gentoo/freenode and several people seem to be getting this. Someone said that it was slotted and all the different versions are needed. Why are they all suddenly needed when they weren't before? Or is this a bug?

Somebody also mentioned having problems with gtk2 after emerging all these slotted automakes. Until I can be sure that the above is proper portage behavior and that I can emerge -uD world with confidence, can somebody please explain this to me?

fernandotcl · Post by **fernandotcl** » Tue Jan 25, 2005 5:29 am

I smell a rat. They're not slotted yet, they're going to be slotted. I don't think this is something planned. File a bug?

CHAOSACES · Post by **CHAOSACES** » Tue Jan 25, 2005 5:32 am

I'm getting the same thing, but I just figured I'd let portage rock on with it's bad self. I hope that's not a mistake....

psylence · Post by **psylence** » Tue Jan 25, 2005 5:47 am

Same problem, gonna wait a day, doesn't seem right.

mikegpitt · Post by **mikegpitt** » Tue Jan 25, 2005 7:06 am

Just saying another "same here". It seemed like something was fishy... let's wait and see.

mihai.vlad · Post by **mihai.vlad** » Tue Jan 25, 2005 7:32 am

Same here:
mihaiv andi # emerge -Dvpu world

These are the packages that I would merge, in order:

Calculating world dependencies ...done!
[ebuild NS ] sys-devel/autoconf-2.13 0 kB
[ebuild N ] sys-devel/autoconf-wrapper-2 0 kB
[ebuild U ] sys-devel/autoconf-2.59-r6 [2.59-r5] 0 kB
[ebuild UD] sys-devel/automake-1.5 [1.8.5-r1] (-uclibc) 0 kB
[ebuild NS ] sys-devel/automake-1.8.5-r2 (-uclibc) 0 kB
[ebuild NS ] sys-devel/automake-1.6.3 (-uclibc) 0 kB
[ebuild NS ] sys-devel/automake-1.7.9 (-uclibc) 0 kB
[ebuild NS ] sys-devel/automake-1.4_p6 (-uclibc) 0 kB
[ebuild N ] sys-devel/automake-wrapper-1 0 kB
[ebuild NS ] sys-devel/automake-1.9.4 (-uclibc) 734 kB
[ebuild U ] sys-devel/libtool-1.5.10-r3 [1.5.2-r7] (-uclibc) 2,636 kB

Total size of downloads: 3,370 kB

TrueDFX · Post by **TrueDFX** » Tue Jan 25, 2005 7:54 am

automake has been slotted on unstable for quite a while. The slotted versions have been marked stable only recently, so without an emerge --sync it may not happen for you (fernandotcl). It's normal.

Someone said that it was slotted and all the different versions are needed. Why are they all suddenly needed when they weren't before?

They were before, but the different versions were just provided by the same ebuild.

cpdsaorg · Post by **cpdsaorg** » Tue Jan 25, 2005 8:38 am

Just a recap... the different versions of automake and autoconf were always there but simply put under a single e-build. now the new standard is to slot them each with there own e-build.

Does portage know when to remove the older versions that are no longer needed?

R!tman · Post by **R!tman** » Tue Jan 25, 2005 8:53 am

I am still waiting with installing all these versions of automake until someone explains what exactly is going on here.

Please, could someone do that?

TrueDFX · Post by **TrueDFX** » Tue Jan 25, 2005 8:59 am

R!tman wrote:I am still waiting with installing all these versions of automake until someone explains what exactly is going on here.

Please, could someone do that?

Your current system:
portage knows you have automake-1.8.5-r1 (guessing) installed. This ebuild really installs all of automake 1.4_p6, 1.5, 1.6.3, 1.7.9 and 1.8.5-r1. When you need to upgrade one version, portage will recompile all versions, since it can only handle packages, not parts of packages.
The new system:
portage installs all these different versions from different ebuilds, allowing you to upgrade automake 1.9.3 to automake 1.9.4 (example version numbers) without recompiling automake 1.4-1.8.

Genone · Post by **Genone** » Tue Jan 25, 2005 9:04 am

The only thing that has changed is the distribution of automake. Up to now there was only one SLOT for automake that installed multiple versions, now each version is installed in its own SLOT. This was done as the previous solution was confusing if you wanted to know exactly which automake version you had installed (you had to run `automake-x.y --version` for all x.y). From a user point of view nothing has changed really.
The reason why multiple automake versions are required is because newer versions are often not fully backwards compatible and can cause problems when building packages designed for older versions.
Same situation for autoconf.

xsteadfastx · Post by **xsteadfastx** » Tue Jan 25, 2005 9:11 am

Genone wrote:The only thing that has changed is the distribution of automake. Up to now there was only one SLOT for automake that installed multiple versions, now each version is installed in its own SLOT. This was done as the previous solution was confusing if you wanted to know exactly which automake version you had installed (you had to run `automake-x.y --version` for all x.y). From a user point of view nothing has changed really.
The reason why multiple automake versions are required is because newer versions are often not fully backwards compatible and can cause problems when building packages designed for older versions.
Same situation for autoconf.

thank you alot for the informations..so its safe to update?

Rammoth · Post by **Rammoth** » Tue Jan 25, 2005 9:37 am

I've emerged the updates

qpkg -I -v | grep auto

sys-devel/automake-1.8.5-r2 *
sys-devel/autoconf-2.59-r6 *
sys-devel/automake-1.5 *
sys-devel/automake-1.4_p6 *
sys-devel/automake-1.6.3 *
sys-devel/automake-1.7.9 *
sys-devel/automake-1.9.4 *
sys-devel/automake-wrapper-1 *
sys-devel/autoconf-2.13 *
sys-devel/autoconf-wrapper-2 *

I now have lots of versions of automake.

Interesting.

R!tman · Post by **R!tman** » Tue Jan 25, 2005 9:43 am

@Genone & TrueDFX

Thanks for the info!

hq4ever · Post by **hq4ever** » Tue Jan 25, 2005 10:21 am

My post was dumped while I was editing it to avoid confusion with this post

I was asking "generally" not specifically for this incident.
Never mind, I'll just ask my questions here in the hope that it will not be considered "Post Spam".
--

From the man page I see that NS means "New Slot" so the questions are :

a. What is a slot ? (I know that it's explained in the doc's but not too detailed for me

)
b. Did each autumake-* created it's own slot or did they all go to only 1 new slot ?
c. Is it safe to remove the old automake('s) & it slot('s) ? In the same way I removed gcc 3.3.5 when upgraded to 3.4.3 even though it had it's own slot ?

Genone or anyone else, please spend 1 minute & explain it to me.

Thank you very much for your comment's.
Cheers, Maxim.

xchris · Post by **xchris** » Tue Jan 25, 2005 10:35 am

anyway...
is it normal that automake-1.8.5-r1 is in slot 1.5?

Code: Select all

*  sys-devel/automake :
        [   ] 1.4_p6 (1.4)
        [   ] 1.5 (1.5)
        [   ] 1.6.3 (1.6)
        [   ] 1.7.9 (1.7)
        [  I] 1.8.5-r1 (1.5)
        [   ] 1.8.5-r2 (1.8)
        [   ] 1.9.4 (1.9)

bye

mhodak · Post by **mhodak** » Tue Jan 25, 2005 3:42 pm

I have noticed this too, but at least on my machine, 1.8.5-r1 will be removed after the upgrade

Code: Select all

[ebuild     UD] sys-devel/automake-1.5 [1.8.5-r1] (-uclibc) 0 kB

and only versions with correct slotting will be installed.

morbus · Post by **morbus** » Tue Jan 25, 2005 4:02 pm

Hi,
I've got some problems with it. I'm running a x86-System and synced today. If I try a emerge -pu system, portage will give

Code: Select all

!!! All ebuilds that could satisfy "sys-devel/autoconf-wrapper" have been masked.
!!! One of the following masked packages is required to complete your request:
- sys-devel/autoconf-wrapper-2 (masked by: ~x86 keyword)
- sys-devel/autoconf-wrapper-1-r1 (masked by: ~x86 keyword)

For more information, see MASKED PACKAGES section in the emerge man page or
section 2.2 "Software Availability" in the Gentoo Handbook.
!!!    (dependency required by "sys-devel/autoconf-2.59-r6" [ebuild])


!!! Problem with ebuild sys-devel/autoconf-2.59-r6
!!! Possibly a DEPEND/*DEPEND problem.

I found this rather strange, since I actually don't intend using ~x86 software. any suggestions ?

mfg
morbus

fernandotcl · Post by **fernandotcl** » Tue Jan 25, 2005 4:59 pm

Well, I think it's pretty much explained, thanks. Anyways, maybe an announcement at GWN would be a good idea.

oberyno · Post by **oberyno** » Tue Jan 25, 2005 4:59 pm

hq4ever wrote:a. What is a slot ? (I know that it's explained in the doc's but not too detailed for me )

Ok, I'll try to explain it. SLOTs are used for packages that need to have multiple versions installed. As Genome said, automake versions are not backwards compatible. So, if an upstream dev writes his Makefile.in's and such with an older automake, every person who wants to compile his source has to have a similar automake version.

So, when an ebuild calls automake, the script am-wrapper.sh is called(as automake is a symlink). That script then determines which automake is requested( ebuilds that need a specific automake export a "WANT_AUTOMAKE" variable that is set to the needed version). am-wrapper.sh then points the calling process to a versioned automake in /usr/bin (i.e. /usr/bin/automake-1.7). As you can see, portage handles slotted packages by installing a bunch of versioned files. So, all the automakes have their version appended to automake. Gcc installs to /usr/lib/gcc-lib/i686-pc-linux-gnu/$GCC_VERSION. This way, version 1.8 won't overwrite version 1.7's files.

Also, portage handles some slotted packages on it's own, while not so with others. If you want to use a different kernel, you'll have to point the symlink /usr/src/linux to a new kernel. Gcc needs gcc-config to change slots. Autoconf, automake, and db are a few examples of slotted programs that don't need user intervention to switch between slotted implementions(well, it doesn't appear that db needs special handling as there is no generic /usr/bin/db).

b. Did each autumake-* created it's own slot or did they all go to only 1 new slot ?

The different versions go into different SLOTs. Equery(part of gentoolkit) shows which slot each version is in(the number in parentheses at the end).

Code: Select all

equery list automake
[ Searching for package 'automake' in all categories among: ]
 
[I--] [  ] sys-devel/automake-1.4_p6 (1.4)
[I--] [  ] sys-devel/automake-1.8.5-r2 (1.8)
[I--] [  ] sys-devel/automake-wrapper-1 (0)
[I--] [  ] sys-devel/automake-1.6.3 (1.6)
[I--] [  ] sys-devel/automake-1.9.3 (1.9)
[I--] [  ] sys-devel/automake-1.5 (1.5)
[I--] [  ] sys-devel/automake-1.7.9 (1.7)

c. Is it safe to remove the old automake('s) & it slot('s) ? In the same way I removed gcc 3.3.5 when upgraded to 3.4.3 even though it had it's own slot ?

No, it's probably not safe to remove old versions of automake/autoconf. Sooner or later(probably sooner) you'll emerge a package that _requires_ an older automake and you'll be screwed. Multiple versions of gcc are not needed however. A good rule of thumb would be don't unmerge slotted packages that portage takes care of(automake, autoconf, db, ...). If portage doesn't take care of a slotted package, it's probably a good indication that only 1 package is absolutely required and the slot mechanism is provided for convenience.

landon · Post by **landon** » Tue Jan 25, 2005 5:13 pm

I'm getting the same emerge output. Also, it appears that gcc 3.4.3 (via package.keywords) constantly wants to be downgraded/upgraded to 20050110 or -r1, respectively.

rabbit · Post by **rabbit** » Tue Jan 25, 2005 6:29 pm

I believe my current issues are because of this update. Autoconf was updated to 2.59-r6. Now, when portage tries to compile automake, it can't -- it says it can't find an autoconf version greater than 2.58.

Any ideas?

qpkg -I -v | grep auto:

Code: Select all

# qpkg -I -v | grep auto
sys-devel/automake-1.8.5-r2 *
sys-devel/autoconf-2.59-r6 *
sys-devel/automake-1.5 *
sys-devel/automake-1.4_p6 *
sys-devel/automake-1.6.3 *
sys-devel/automake-1.7.9 *
sys-devel/automake-1.9.3 *
sys-devel/automake-wrapper-1 *
sys-devel/autoconf-2.13 *
sys-devel/autoconf-wrapper-2 *

ebuild error:

Code: Select all

-- SNIP --
checking for tex... tex
checking whether autoconf is installed... no
configure: error: Autoconf 2.58 or better is required.
    Please make sure it is installed and in your PATH.

/var/tmp/portage/automake-1.9.4/work/automake-1.9.4/config.log:

Code: Select all

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by GNU Automake configure 1.9.4, which was
generated by GNU Autoconf 2.59a.  Invocation command line was

  $ ./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib

## --------- ##
## Platform. ##
## --------- ##

hostname = yoda
uname -m = i686
uname -r = 2.6.10-gentoo-r4
uname -s = Linux
uname -v = #2 Thu Jan 13 17:11:54 EST 2005

/usr/bin/uname -p = Intel(R) Pentium(R) M processor 1300MHz
/bin/uname -X     = unknown

/bin/arch              = i686
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
hostinfo               = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /usr/lib/ccache/bin
PATH: /sbin
PATH: /usr/sbin
PATH: /usr/lib/portage/bin
PATH: /bin
PATH: /usr/bin
PATH: /opt/bin
PATH: /usr/i686-pc-linux-gnu/gcc-bin/3.3.5
PATH: /opt/Acrobat5
PATH: /usr/X11R6/bin
PATH: /opt/blackdown-jdk-1.4.2.01/bin
PATH: /opt/blackdown-jdk-1.4.2.01/jre/bin


## ----------- ##
## Core tests. ##
## ----------- ##

configure:1510: checking build system type
configure:1528: result: i686-pc-linux-gnu
configure:1557: checking for a BSD-compatible install
configure:1612: result: /bin/install -c
configure:1623: checking whether build environment is sane
configure:1666: result: yes
configure:1731: checking for gawk
configure:1747: found /bin/gawk
configure:1757: result: gawk
configure:1767: checking whether make sets $(MAKE)
configure:1787: result: yes
configure:1863: checking for i686-pc-linux-gnu-strip
configure:1879: found /usr/bin/i686-pc-linux-gnu-strip
configure:1889: result: i686-pc-linux-gnu-strip
configure:1988: checking for perl
configure:2006: found /usr/bin/perl
configure:2018: result: /usr/bin/perl
configure:2039: checking for tex
configure:2055: found /usr/bin/tex
configure:2065: result: tex
configure:2079: checking whether autoconf is installed
configure:2084: eval autoconf --version
./configure: line 2085: autoconf: command not found
configure:2087: $? = 127
configure:2095: result: no
configure:2099: error: Autoconf 2.58 or better is required.
    Please make sure it is installed and in your PATH.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_build=i686-pc-linux-gnu
ac_cv_build_alias=i686-pc-linux-gnu
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=set
ac_cv_env_host_alias_value=i686-pc-linux-gnu
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_path_PERL=/usr/bin/perl
ac_cv_path_install='/bin/install -c'
ac_cv_prog_AWK=gawk
ac_cv_prog_STRIP=i686-pc-linux-gnu-strip
ac_cv_prog_TEX=tex
ac_cv_prog_make_make_set=yes
am_cv_autoconf_installed=no

## ----------------- ##
## Output variables. ##
## ----------------- ##

ACLOCAL='perllibdir=/var/tmp/portage/automake-1.9.4/work/automake-1.9.4"/lib:./lib" /var/tmp/portage/automake-1.9.4/work/automake-1.9.4/aclocal --acdir=m4'
AMTAR='${SHELL} /var/tmp/portage/automake-1.9.4/work/automake-1.9.4/lib/missing --run tar'
APIVERSION='1.9'
AUTOCONF='${SHELL} /var/tmp/portage/automake-1.9.4/work/automake-1.9.4/lib/missing --run autoconf'
AUTOHEADER='${SHELL} /var/tmp/portage/automake-1.9.4/work/automake-1.9.4/lib/missing --run autoheader'
AUTOMAKE='perllibdir=/var/tmp/portage/automake-1.9.4/work/automake-1.9.4"/lib:./lib" /var/tmp/portage/automake-1.9.4/work/automake-1.9.4/automake --libdir=lib'
AWK='gawk'
CYGPATH_W='echo'
DEFS=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
FGREP=''
GREP=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='${SHELL} $(install_sh) -c -s'
LIBOBJS=''
LIBS=''
LN=''
LTLIBOBJS=''
MAKEINFO='${SHELL} /var/tmp/portage/automake-1.9.4/work/automake-1.9.4/lib/missing --run makeinfo'
MODIFICATION_DELAY=''
PACKAGE='automake'
PACKAGE_BUGREPORT='bug-automake@gnu.org'
PACKAGE_NAME='GNU Automake'
PACKAGE_STRING='GNU Automake 1.9.4'
PACKAGE_TARNAME='automake'
PACKAGE_VERSION='1.9.4'
PATH_SEPARATOR=':'
PERL='/usr/bin/perl'
SET_MAKE=''
SHELL='/bin/sh'
STRIP='i686-pc-linux-gnu-strip'
TEX='tex'
VERSION='1.9.4'
ac_ct_STRIP=''
am_AUTOCONF='autoconf'
am__leading_dot='.'
am__tar='${AMTAR} chof - "$$tardir"'
am__untar='${AMTAR} xf -'
bindir='${exec_prefix}/bin'
build='i686-pc-linux-gnu'
build_alias=''
build_cpu='i686'
build_os='linux-gnu'
build_vendor='pc'
datadir='/usr/share'
exec_prefix='NONE'
host_alias='i686-pc-linux-gnu'
includedir='${prefix}/include'
infodir='/usr/share/info'
install_sh='/var/tmp/portage/automake-1.9.4/work/automake-1.9.4/lib/install-sh'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
localstatedir='/var/lib'
mandir='/usr/share/man'
mkdir_p='mkdir -p --'
oldincludedir='/usr/include'
pkgvdatadir='${datadir}/automake-1.9'
prefix='/usr'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

             
#define PACKAGE "automake"
#define PACKAGE_BUGREPORT "bug-automake@gnu.org"
#define PACKAGE_NAME "GNU Automake"
#define PACKAGE_STRING "GNU Automake 1.9.4"
#define PACKAGE_TARNAME "automake"
#define PACKAGE_VERSION "1.9.4"
#define VERSION "1.9.4"

configure: exit 1

I'm sure I could just symlink /usr/bin/autoconf-2.59 to /usr/bin/autoconf, but that just seems hackish.

blaksaga · Post by **blaksaga** » Tue Jan 25, 2005 6:39 pm

You guys have pretty much answered my questions. Now I at least have a vague idea of what's happening. Thanks for the help.

brullonulla · Post by **brullonulla** » Tue Jan 25, 2005 10:44 pm

I don't know if it's on topic or if it needs a separate thread, but emerging autoconf I am stuck on the following error :

make[3]: Leaving directory `/var/tmp/portage/autoconf-2.59-r6/work/autoconf-2.59/lib/emacs'
make[2]: Leaving directory `/var/tmp/portage/autoconf-2.59-r6/work/autoconf-2.59/lib/emacs'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/autoconf-2.59-r6/work/autoconf-2.59/lib'
make: *** [all-recursive] Error 1

!!! ERROR: sys-devel/autoconf-2.59-r6 failed.
!!! Function src_compile, Line 25, Exitcode 2

My CFLAGS are all but aggressive:

CFLAGS="-O3 -pipe -march=athlon-xp -fomit-frame-pointer -mmmx -msse -m3dnow"

Any help?

mhill · Post by **mhill** » Wed Jan 26, 2005 12:24 am

oberyno, thanks for the good explanation. I had kinda figured out most of that from emerge(1), but it was good to have the gaps filled in.

I appear to have three gcc versions (I thought it was more than that, but maybe I was thinking of automake versions): gcc-3.3.4-r1, gcc-3.4.3-r1, and gcc-3.4.3.20050110. Is it safe to unmerge all but the last one (which is the most recent)? When I try, I get the warning

!!! Trying to unmerge package(s) in system profile. 'sys-devel/gcc'
!!! This could be damaging to your system.