When compiling sys-fs/e2fsprogs-1.41.9 it failed with making all in debugfs make[2]: Entering directory `/var/tmp/portage/sys-fs/e2fsprogs-1.41.9/work/e2fsprogs-1.41.9/debugfs' MK_CMDS debug_cmds.c CC debugfs.c /usr/bin/mk_cmds: line 51: /usr/bin/sed: No such file or directory CC util.c CC ncheck.c CC icheck.c CC ls.c CC lsdel.c CC dump.c CC set_fields.c CC logdump.c CC htree.c CC unused.c SUBST debugfs.8 CC debug_cmds.c debug_cmds.c:1: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'ssu00001' debug_cmds.c:5: warning: data definition has no type or storage class debug_cmds.c:5: error: 'ssu00001' undeclared here (not in a function) debug_cmds.c:5: warning: excess elements in scalar initializer debug_cmds.c:5: warning: (near initialization for 'ss_request_table') make[2]: *** [debug_cmds.o] Error 1 What made me suspicious was that it tried to execute /usr/bin/sed as sed is located in /bin/sed and configure correctly finds it. With a symlink /usr/bin/sed -> /bin/sed e2fsprogs emerges fine. So probably easy to reproduce.
Can you attach your emerge --info and the full build.log, please? I'm not getting this error here on amd64.
(In reply to comment #1) > Can you attach your emerge --info and the full build.log, please? I'm not > getting this error here on amd64. > I should have checked the message better. There was a hardcoded sed in /usr/bin/mk_cmds which belongs to sys-libs/e2fsprogs-libs. Apparently sys-libs/e2fsprogs-libs preferres the symlink /usr/bin/sed over /bin/sed when emerging and after upgrading/cleaning the system (and removing the orphan /usr/bin/sed), /usr/bin/mk_cmds stopped working because of the hardcoded path. Reemerging sys-libs/e2fsprogs-libs solved the problem as the path there is now pointing to /bin/sed (line 9). I don't know why the absolute path is used for sed as for awk it relies on proper search path. I'm not sure if using absolute paths should be considered as a bug.
