Summary: | sys-boot/yaboot-1.3.17-r2 with sys-fs/e2fsprogs-1.42.12 - /usr/lib/libext2fs.a(unix_io.o): In function `raw_write_blk': (.text+0x1a4): undefined reference to `pwrite64' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Nils Holland <nholland> |
Component: | [OLD] Core system | Assignee: | PPC Porters <ppc> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | njsg, ppc64 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | PPC | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=548950 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Nils Holland
2015-03-27 17:16:50 UTC
Does portage actually take 1.42.11? Here on a fresh stage3, those are ~ppc, and I'm getting compile failures with 1.42.11. (In reply to Nuno Silva from comment #1) > Does portage actually take 1.42.11? Here on a fresh stage3, those are ~ppc, > and I'm getting compile failures with 1.42.11. Right, I didn't mention properly that I observed the problem on ~ppc, where 1.42.12 was actually supposed to be installed but wouldn't work, while 1.42.11 would. There's a chance that the build failures you are seeing with 1.42.11 on ppc can be fixed by having a look at https://bugs.gentoo.org/show_bug.cgi?id=527974 and emerging sys-fs/e2fsprogs and sys-fs/e2fsprogs-libs with "-fno-stack-protector". Unfortunately, I still can't compile yaboot even after compiling e2fsprogs{,-libs} with -fno-stack-protector or with gcc:4.7. -fno-stack-protector solves the undefined reference from bug 527974, but I still get another undefined reference: /usr/lib/libext2fs.a(unix_io.o): In function `unix_open': (.text+0x10f4): undefined reference to `fcntl' Makefile:112: recipe for target 'yaboot' failed No comments 1, 2, and 3 are missing the mark. The problem was introduced by an upstream commit between 1.42.11 and 1.42.12. See bug #548950 for a different problem that this commit caused. I don't have enough details from comment 0, but it looks like the -m32 is causing the problem. It looks like your building 32-bit userland on a 64-bit kernel? > I don't have enough details from comment 0, but it looks like the -m32 is > causing the problem. It looks like your building 32-bit userland on a > 64-bit kernel? (Being the author of comment 0): No, actually I'm running both 32 bit userland and kernel. It's a G4-based Apple Mac Mini that somehow found the way into my hands and that I've observed this issue with: nils@ppc-nas ~ $ lscpu Architecture: ppc CPU op-mode(s): 32-bit Byte Order: Big Endian CPU(s): 1 On-line CPU(s) list: 0 Thread(s) per core: 1 Core(s) per socket: 1 Socket(s): 1 Model: PowerMac10,2 BogoMIPS: 83.20 L1d cache: 32K L1i cache: 32K L2 cache: 512K nils@ppc-nas ~ $ uname -a Linux ppc-nas.tisys.local 3.19.3-gentoo #1 Sat Mar 28 17:27:07 CET 2015 ppc 7447A, altivec supported PowerMac10,2 GNU/Linux *** This bug has been marked as a duplicate of bug 527974 *** |