[Nasm-bugs] [Bug 3392374] NASM is confused by its argument list when called with %1 %2 %3 parameters

no-reply at bugzilla-nasm.gorcunov.org no-reply at bugzilla-nasm.gorcunov.org
Mon Nov 28 02:09:46 PST 2016


https://bugzilla.nasm.us/show_bug.cgi?id=3392374

--- Comment #1 from Mateusz Viste <mateusz at nospam.viste.fr> ---
Created attachment 411571
  --> https://bugzilla.nasm.us/attachment.cgi?id=411571&action=edit
demonstration of the problem

By re-reading this report today I realized it's highly obscure - I'm sorry for
that. Here I attach a screenshot that should be self-explanatory.

After some additional research, it would appear that the problem is not related
to nasm after all, but to some odd behavior of FreeDOS. In the example shown on
the attached screenshot, nasm complains about 'too many input files'. In fact,
it complains because apparently FreeCOM splits the parameter "-DXCPU=86" into
two arguments when calling nasm from within a batch file, so nasm effectively
gets one argument "-DXCPU" and another one "86". Not sure why exactly this
happens, nor whether this is a bug or a feature, but I don't see how possibly
this could be nasm's problem. Please disregard this bug report.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are watching all bug changes.


More information about the Nasm-bugs mailing list