Emerging elilo fails on the gnu-efi build Reproducible: Always Steps to Reproduce: 1.Emerge elilo 2. 3. Actual Results: ERROR: sys-boot/gnu-efi-3a failed runtime/vm.c:56: warning: dereferencing type-punned pointer will break strict- aliasing rules runtime/vm.c:57: warning: dereferencing type-punned pointer will break strict- aliasing rules runtime/vm.c:59: warning: dereferencing type-punned pointer will break strict- aliasing rules runtime/vm.c:60: warning: dereferencing type-punned pointer will break strict- aliasing rules runtime/vm.c: At top level: runtime/vm.c:67: warning: ignoring #pragma RUNTIME_CODE runtime/rtdata.c:29: warning: ignoring #pragma BEGIN_RUNTIME_DATA ia64/math.c:26: warning: ignoring #pragma RUNTIME_CODE ia64/math.c:27: warning: ignoring #pragma RUNTIME_CODE ia64/math.c:28: warning: ignoring #pragma RUNTIME_CODE ia64/math.c:29: warning: ignoring #pragma RUNTIME_CODE ia64/salpal.c: In function `LibInitSalAndPalProc': ia64/salpal.c:76: warning: dereferencing type-punned pointer will break strict- aliasing rules ia64/salpal.c: In function `LibGetSalIoPortMapping': ia64/salpal.c:123: warning: dereferencing type-punned pointer will break strict-aliasing rules reloc_ia64.S: Assembler messages: reloc_ia64.S:128: Warning: Use of 'setf.sig' may violate RAW dependency 'GR%, % in 1 - 127' (impliedf), specific resource number is 17 reloc_ia64.S:128: Warning: Only the first path encountering the conflict is reported reloc_ia64.S:127: Warning: This is the location of the conflicting usage ar: creating libgnuefi.a t.c:51: warning: 'a2u' defined but not used ld: .data has both ordered and unordered sections ld: final link failed: Bad value make[1]: *** [t.so] Error 1 make: *** [apps] Error 2 !!! ERROR: sys-boot/gnu-efi-3.0a failed. !!! Function src_compile, Line 31, Exitcode 2 !!! emake failed !!! If you need support, post the topmost build error, NOT this status message.
Richard: Please use New -> Gentoo Linux -> Component: Ebuilds. Infrastructure is not the correct addressee.
Ok, this was caused by 2.1.95 binutils getting marked as ~IA64 by somebody *cough* vapier *cough* with little testing, now marked -IA64. Closing bug.
not really, been running 2.15.92.0.2 in my chroot since Nov 13 2004 and havent noticed any noticed regressions, plus it passed `make check` ... seemed like a pretty good candidate for ~ia64 :P
*** Bug 87422 has been marked as a duplicate of this bug. ***
