https://sourceware.org/bugzilla/show_bug.cgi?id=29547
--- Comment #2 from Sergei Trofimovich <slyich at gmail dot com> --- (In reply to Nick Alcock from comment #1) > Adding an exit status test seems like a good idea, yes. I'll do that in the > next few days (busy, but this is easy and machine time is cheap). > > I don't have access to a Darwin machine and the compile farm obviously > doesn't have any -- could you check that the result works once I have > something? Yeah, I should be able to test possible fixes. > (The reason for the oddness of this test is simply that we have to run nm on > *something*, and many implementations forbid running it on /dev/null, and > *correct* output on every implementation I have seen includes the file name. > Of course, multi-line error messages might too... oops. I hope an exit > status test will suffice to avoid that.) Oh, would it also fail if nm happens to be a shell wrapper itself? I was about to wrap it for another unrelated reason. -- You are receiving this mail because: You are on the CC list for the bug.
