42810 – emerge glibc-2.3.3_pre* failed on vmware 4.0.5 build 6030 with gentoo as a guest OS

Bug 42810 - emerge glibc-2.3.3_pre* failed on vmware 4.0.5 build 6030 with gentoo as a guest OS

Summary: emerge glibc-2.3.3_pre* failed on vmware 4.0.5 build 6030 with gentoo as a gu...

Status:	RESOLVED INVALID

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	x86 Linux

Importance:	High normal (vote)
Assignee:	Please assign to toolchain

URL:	http://forums.gentoo.org/viewtopic.ph...
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-02-24 14:39 UTC by Tuan Van (RETIRED)
Modified:	2004-03-19 02:20 UTC (History)
CC List:	1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Tuan Van (RETIRED) gentoo-dev

2004-02-24 14:39:46 UTC

emerge glibc-2.3.3_pre* fail with
!!! FAILED postinst: 2816

after that, most of the shell script will segmentfault. On reboot, system hang with:

init: panic: segmentation violation at 0x804de6d! sleeping for 30 seconds.

no problem with the latest glibc-2.3.2

Reproducible: Always
Steps to Reproduce:
1. Setup Gentoo as guest OS on vmware version 4.0.5 build 6030.
2. ACCEPT_KEYWORDS="~x86" emerge glibc
3.

Comment 1 Martin Holzer (RETIRED) gentoo-dev

2004-03-19 02:20:23 UTC

dont install base system with unstable.

install stable, then change keyword to unstable, then upgrade (see install docs)