[sr #108558] libtool nm test does not really work for W32 versions of nm

Update of sr#108558 (group libtool): Open/Closed:Open => Closed ___ Reply to this item at: ___

[sr #108558] libtool nm test does not really work for W32 versions of nm

Follow-up Comment #11, sr #108558 (project libtool): Don't you want to close this bug? ___ Reply to this item at: http://savannah.gnu.org/support/?108558 ___ Message sent via/by Savannah

[sr #108558] libtool nm test does not really work for W32 versions of nm

Update of sr #108558 (project libtool): Status:None = Done ___ Follow-up Comment #10: Patch pushed. Cheers, Peter ___

Re: [sr #108558] libtool nm test does not really work for W32 versions of nm

On 2014-05-06 15:30, Peter Rosin wrote: Follow-up Comment #8, sr #108558 (project libtool): I have attached a patch that does the safe-safe-safe version. Does it work for you? *snip* http://savannah.gnu.org/support/?108558 To not force everyone to follow the link, here's the patch in

[sr #108558] libtool nm test does not really work for W32 versions of nm

Follow-up Comment #8, sr #108558 (project libtool): I have attached a patch that does the safe-safe-safe version. Does it work for you? Cheers, Peter (file #31318) ___ Additional Item Attachment: File name:

[sr #108558] libtool nm test does not really work for W32 versions of nm

Follow-up Comment #9, sr #108558 (project libtool): I have attached a patch that does the safe-safe-safe version. Does it work for you? Yes, it seems that it does. ___ Reply to this item at: http://savannah.gnu.org/support/?108558

Re: [sr #108558] libtool nm test does not really work for W32 versions of nm

On 2014-05-06 15:30, Peter Rosin wrote: Follow-up Comment #8, sr #108558 (project libtool): I have attached a patch that does the safe-safe-safe version. Does it work for you? *snip* http://savannah.gnu.org/support/?108558 To not force everyone to follow the link, here's the patch in

[sr #108558] libtool nm test does not really work for W32 versions of nm

Follow-up Comment #1, sr #108558 (project libtool): Thanks for the report. Just a quick note, Cygwin is not affected. This happens on MSYS/MinGW only. On Cygwin, the Windows (or should I say DOS?) NUL device is never involved. cygwin$ /bin/nm -B /dev/null /bin/nm: Warning: '/dev/null' is not an

[sr #108558] libtool nm test does not really work for W32 versions of nm

Follow-up Comment #2, sr #108558 (project libtool): I was not aware of the extent to which Cygwin is mangling commandlines of pure-W32 programs it runs (since i don't really use Cygwin; i do know it does some kind of conversion; apparently, only in one direction). Evidently, it does not replace

[sr #108558] libtool nm test does not really work for W32 versions of nm

Follow-up Comment #3, sr #108558 (project libtool): Well, in MSYS2 you can simply do: nm -B /dev/thisfilebetternotexistotherwiseyoullbeintrouble and get satisfactory results (file name and 'No such file' in the output). Can't say anything about MSYS1, haven't used it for some time. That

[sr #108558] libtool nm test does not really work for W32 versions of nm

Follow-up Comment #4, sr #108558 (project libtool): Well, in MSYS2 you can simply do: nm -B /dev/thisfilebetternotexistotherwiseyoullbeintrouble and get satisfactory results (file name and 'No such file' in the output). Can't say anything about MSYS1, haven't used it for some time. That

[sr #108558] libtool nm test does not really work for W32 versions of nm

Follow-up Comment #5, sr #108558 (project libtool): Hmm, on second thought, that depends on MSYS (and MSYS2) still thinking that an argument starting with more than two slashes is a UNC path (or a switch). That might change if someone points out that ///foo and /foo should be equivalent and that

[sr #108558] libtool nm test does not really work for W32 versions of nm

Follow-up Comment #6, sr #108558 (project libtool): Crap. How about just opening a file that is known to not to exist? Alternatively, give nm a real file that is at least 1 byte long (binutils nm checks for filesize being 1 and fails quietly; having 1 byte makes it say filename (which is

[sr #108558] libtool nm test does not really work for W32 versions of nm

Follow-up Comment #7, sr #108558 (project libtool): Ok, something like this seems safer: mkdir conftest.dir case `$tmp_nm -B conftest.dir/nofile` in *conftest.dir/nofile*) blablabla esac rm -rf conftest.dir But I don't know how non-GNU nm behaves, so the safe-safe-safe version only does the

[sr #108558] libtool nm test does not really work for W32 versions of nm

URL: http://savannah.gnu.org/support/?108558 Summary: libtool nm test does not really work for W32 versions of nm Project: GNU Libtool Submitted by: lrn Submitted on: Fri 02 May 2014 05:10:04 AM GMT Category: None