After emerged gawk-3.1.2 and a reboot my system hangs on startup. It hadn't started devfsd, eth0 doesn't started and he couldn't make symlinks to /var/lib/init.d. After some tests (searched for bugs in other ebuilds...) and a re-emerge of gawk-3.1.1-r1 everything worked fine again. I tested to reinstall it again (no other emerges than this one) and problem came again/was solved again by emergeing gawk-3.1.1. I noticed that the header-files installed with 3.1.1-r1 aren't installed with 3.1.2, but I don't know if this has to do anything with the problem...
that was my bump, I'm working on it... what a silly gawk.
Hey, Martin, I get the weirdest "gawk - relocation error: /lib/filefuncs.so undefined symbol dupnode" with the new gawk, any hint as to why that would happen or why it would be linking against that at all or what? Thanks.
ahh... nvm, I think I see whats going on, looks like the awk module of baselayout gets mixed up symbols as compared to the awk executable... or something? testing now.
eek. filefuncs.so needs to be rebuilt on any awk upgrade rather than on any baselayout upgrade... can we move it to the awk ebuild azarah? Thanks!
I'm hearing reports from users that 3.1.2-r2 has the same borkage.
Yes the problem is still there with gawk3.1.2-r2.... The simple test to see (without rebooting) is this. mermaid root # awk '($2 == "devfs") {print "yes"; exit 0 }' /proc/filesystems mermaid root # awk '($2 == "devfs") {print "yes"; exit 0 }' /proc/filesystems yes the command should have returned yes both times. First time it was executed with the 3.1.2-r2 and then reverting back to 3.1.1-r2 This line is from /sbin/rc awk has stopped taking filename as a parameter. because cat /proc/filesystems | awk '($2 == "devfs") {print "yes"; exit 0 }' works in both cases (I havent tested this with 3.1.2-r2 but I tested with 3.1.2-r1 and it worked) Hope this helps. Spundun
*** Bug 18192 has been marked as a duplicate of this bug. ***
*** Bug 18235 has been marked as a duplicate of this bug. ***
*** Bug 18283 has been marked as a duplicate of this bug. ***
Special files like those in /proc, report themselves as regular files of length 0, when in fact they have data in them if you try to read them. The new record-reading code wasn't quite smart enough to deal with such a bizarre case. The following patch fixes the problem, thanks to Arnold D. Robbins (Maintainer of gawk). Anyhow, gawk-3.1.2-r3 should fix this.
This seems fine here Azarah, thanks.
Right, this can be closed.
