Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 197391 - Emerging m4 must be deferred on SUSE Enterprise Server 9.3.
Summary: Emerging m4 must be deferred on SUSE Enterprise Server 9.3.
Status: RESOLVED FIXED
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Prefix Support (show other bugs)
Hardware: x86 Linux
: High normal (vote)
Assignee: Gentoo non-Linux Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-29 10:32 UTC by Rabbe Fogelholm
Modified: 2007-12-01 14:17 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
script used to demonstrate the problem (m4-problem.sh,653 bytes, text/plain)
2007-10-29 10:35 UTC, Rabbe Fogelholm
Details
console output that demonstrates the problem (console-output-m4-problem.txt.bz2,40.34 KB, application/octet-stream)
2007-10-29 10:36 UTC, Rabbe Fogelholm
Details
build log of m4 (build.log.bz2,7.51 KB, text/plain)
2007-10-29 10:39 UTC, Rabbe Fogelholm
Details
script that demonstrates workaround (m4-workaround.sh,2.06 KB, text/plain)
2007-10-29 10:40 UTC, Rabbe Fogelholm
Details
final lines of console output (emerge-m4-fails-on-RHEL-3.txt,2.68 KB, text/plain)
2007-11-20 20:02 UTC, Rabbe Fogelholm
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rabbe Fogelholm 2007-10-29 10:32:02 UTC
This problem was discovered when trying to bootstrap Prefix Portage on SUSE Enterprise Server 9.3, following the October 29, 2007 version of http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-linux.xml.

In brief, the problem is that emerging m4 fails if attempted right after emerging bash.

A workaround is to defer emerging m4 until libtool has been emerged. After that it is also necessary to re-emerge some packages that possibly require m4 of version not older than 1.4.10. I have not investigated exactly which packages that have to be re-emerged; since it does not take long I simply re-emerge all autoconfand automake packages, plus texinfo and libtool. Having done so the process is in fine shape for the next step (coreutils).

Artifacts will be enclosed.
Comment 1 Rabbe Fogelholm 2007-10-29 10:35:04 UTC
Created attachment 134615 [details]
script used to demonstrate the problem

script used to demonstrate the problem
Comment 2 Rabbe Fogelholm 2007-10-29 10:36:02 UTC
Created attachment 134616 [details]
console output that demonstrates the problem

console output that demonstrates the problem
Comment 3 Rabbe Fogelholm 2007-10-29 10:39:03 UTC
Created attachment 134618 [details]
build log of m4

build log of m4
Comment 4 Rabbe Fogelholm 2007-10-29 10:40:49 UTC
Created attachment 134620 [details]
script that demonstrates workaround

script that demonstrates workaround
Comment 5 Rabbe Fogelholm 2007-10-29 10:43:13 UTC
Not sure if this is of interest, but typing `m4 --version' on the SUSE server, before attempting bootstrap, yields this response:

    GNU m4 1.4o
Comment 6 Rabbe Fogelholm 2007-11-06 22:29:09 UTC
The workaround described before is overkill. It appears that it is sufficient to insert these three lines before emerging m4:

emerge --oneshot --nodeps "=autoconf-2.6*"
emerge --oneshot --nodeps "autoconf-wrapper"
emerge --oneshot --nodeps texinfo
Comment 7 Rabbe Fogelholm 2007-11-20 20:01:37 UTC
The workaround described in this bug report also works on another oldish platform: "Red Hat Enterprise Linux WS release 3 (Taroon Update 5)".

A straightforward attempt to bootstrap, following the usual webpage (<http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-linux.xml>, October 29, 2007), ends with a failure when the m4 package is to be emerged for the first time. See attachment "emerge-m4-fails-on-RHEL-3.txt".

Applying the workaround gets me past m4 and well into the first `emerge -e system'.
Comment 8 Rabbe Fogelholm 2007-11-20 20:02:27 UTC
Created attachment 136529 [details]
final lines of console output
Comment 9 Fabian Groffen gentoo-dev 2007-12-01 14:17:45 UTC
I committed this as revision 1.3.  I hope it works for all linuxes sort of...  I felt like it greatly cleaned bits up though.

Thanks!