Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 544688 - 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'
Summary: sys-boot/yaboot-1.3.17-r2 with sys-fs/e2fsprogs-1.42.12 - /usr/lib/libext2fs....
Status: RESOLVED DUPLICATE of bug 527974
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: PPC Linux
: Normal normal (vote)
Assignee: PPC Porters
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-27 17:16 UTC by Nils Holland
Modified: 2015-05-16 15:27 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nils Holland 2015-03-27 17:16:50 UTC
When trying to install yaboot-1.3.17-r2 on a system that has sys-fs/e2fsprogs-1.42.12 and sys-libs/e2fsprogs-libs-1.42.12 (with -fno-stack-protector) installed, I get this:

gcc -Os  -fno-stack-protector  -Wall -I/usr/include -Wno-error -fdiagnostics-show-option -o util/addnote util/addnote.c
ld -Ttext 0x100000 -Bstatic -melf32ppclinux second/crt0.o second/yaboot.o second/cache.o second/prom.o second/file.o second/partition.o second/fs.o second/cfg.o second/setjmp.o second/cmdline.o second/fs_of.o second/fs_ext2.o second/fs_iso.o second/fs_swap.o second/iso_util.o lib/nonstd.o lib/nosys.o lib/string.o lib/strtol.o lib/vsprintf.o lib/ctype.o lib/malloc.o lib/strstr.o lib/ssp.o second/md5.o second/fs_xfs.o second/fs_reiserfs.o -lext2fs `gcc -m32 -print-libgcc-file-name` -o second/yaboot
/usr/lib/libext2fs.a(unix_io.o): In function `raw_write_blk':
(.text+0x1a4): undefined reference to `pwrite64'
/usr/lib/libext2fs.a(unix_io.o): In function `raw_read_blk':
(.text+0x630): undefined reference to `pread64'
Makefile:112: recipe for target 'yaboot' failed
make: *** [yaboot] Error 1

Masking version 1.42.12 of the two e2fs packages and letting portage take version 1.42.11 instead works fine - yaboot will then build and operate nicely.

(Sorry, the machine on which this happened is currently not accessible to me, so I can't include emerge --info output or similar - at least not right now. If any additional information is required, I should be able to provide it by next week.)

Reproducible: Always
Comment 1 Nuno Silva 2015-04-09 14:34:05 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.
Comment 2 Nils Holland 2015-04-09 18:50:31 UTC
(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".
Comment 3 Nuno Silva 2015-04-09 18:58:25 UTC
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
Comment 4 Anthony Basile gentoo-dev 2015-05-15 18:05:43 UTC
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?
Comment 5 Nils Holland 2015-05-15 18:54:22 UTC
> 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
Comment 6 Joe Jezak (RETIRED) gentoo-dev 2015-05-16 15:27:50 UTC

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