Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 480528

Summary: sys-libs/glibc-2.15-r3 [ia64]: error: redefinition of 'struct ia64_fpreg'
Product: Gentoo Linux Reporter: Émeric Maschino <emeric.maschino>
Component: [OLD] Core systemAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED DUPLICATE    
Severity: major CC: emeric.maschino
Priority: High    
Version: unspecified   
Hardware: IA64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: Failed compilation of systemd-201 with error: redefinition of 'struct ia64_fpreg'
systemd-201 build environment

Description Émeric Maschino 2013-08-10 19:56:57 UTC
While trying to compile sys-apps/systemd, I'm getting error: redefinition of 'struct ia64_fpreg'.

[1] https://bugs.gentoo.org/show_bug.cgi?id=480218

Reproducible: Always

Steps to Reproduce:
1. Unmask systemd
2. emerge --ask systemd
3.
Actual Results:  
emerge --ask systemd failed during compile phase

Expected Results:  
emerge --ask systemd should successfully install systemd

I initially though this was a bug in systemd, and was asked to report upstream [1]. But comments there quickly oriented my research on glibc. I finally discovered this is indeed a known issue with glibc for 10 years now [2]. This also explains why systemd can be successfully compiled on Debian ia64, as they ship eglibc rather than glibc. While this glibc issue is there, other ebuilds may fail, hence the severity set to major as glibc is a central component of Gentoo Linux.

[1] https://bugs.freedesktop.org/show_bug.cgi?id=67960
[2] http://sourceware.org/bugzilla/show_bug.cgi?id=762
Comment 1 Émeric Maschino 2013-08-10 19:58:58 UTC
Created attachment 355632 [details]
Failed compilation of systemd-201 with error: redefinition of 'struct ia64_fpreg'
Comment 2 Émeric Maschino 2013-08-10 19:59:39 UTC
Created attachment 355634 [details]
systemd-201 build environment
Comment 3 Pacho Ramos gentoo-dev 2013-08-11 07:41:21 UTC

*** This bug has been marked as a duplicate of bug 480218 ***