nasm-devel — NASM development work

[Nasm-devel] Using NASM for Java Inline Assembler

[Martin K. <mar...@gm...>]

Hi there,

   I started to investigate the potential solution of using a way to inline
ASM in Java.

What I currently managed to do is:

public void myJava() {

      asm("      nop",
              "      nop",
              "      nop");
}

Which results into writing three nop instructions + ret in a memory block
(allocated by mmap),
grand executable rights and call it using JNA and a custom C method.

The compilation is actually just writing to a memory block using Unsafe (or
calling a C function).

What I am looking for is a compiler for those instructions that integrates
nicely. Since you provide
a very sophisticated product, I would like to ask if there is something
like this possible:

1. Giving a string of assembler instruction, compile it.
2. The output of this compiler step should at best do not be a library or
executable and easily extract the
    necessary operations without additional boilerplate or code I do not
want but have to strip off.
3. Place the output preferable into memory (or use sockets or whatever)
avoiding disk access and temporary file access.
4. If possible can the compiler become a library (or does one exist) making
it possible to avoid spawning child processes.
5. Can the messages of the compiler (errors and alike) be easily parsed and
mapped to the input string
    (like number of lines etc).

The real critical condition is only (1) but the rest is nice to have.


In the end I want a solution where I can do the simple change code, run
Java and enjoy a transparent ASM compilation
one on first use of the snippet. The rest about how to access registers
transfer data etc will be totally custom by me.

The target platform is linux but supporting windows and other x86 languages
would be a great options since once this
works it will become an open source project that is likely to be widely
adopted. I dream about this for 15 years straight
and just found enough information and having free time to takle it. Using
existing compilers would also make this a very
short project with a high chance of attracting other developers adopting it
and push it further. I just need memory access
and manipulation using the 256bit registers of the new Intel Xeon v3
instructions (or v2) and just to speed up a research
project (PhD) but have plenty of other ideas what to speed up also.

Also once this works adding C or Fortran or other compilers in the mix in a
similar way would also be a no brainer but
I just need ASM.


Cheers.

Martin (Kersten),
Germany

Re: [Nasm-devel] issue with 2.11.08 - "-f macho64"

[Cyrill G. <gor...@gm...>]

On Sun, Apr 05, 2015 at 10:23:53AM -0400, Frank Kotler wrote:
> I know you guys are busy, but... There's a message on the Forum...
> 
> http://forum.nasm.us/index.php?topic=2101.msg9294#msg9294
> 
> ...reporting an apparent bug in 2.11.08. This may be the same as:
> 

Hi Frank! I saw it. Once I get some time I'll take a look (can't
set time bounds though, too busy).

[Nasm-devel] issue with 2.11.08 - "-f macho64"

[Frank K. <fbk...@my...>]

I know you guys are busy, but... There's a message on the Forum...

http://forum.nasm.us/index.php?topic=2101.msg9294#msg9294

...reporting an apparent bug in 2.11.08. This may be the same as:

http://bugzilla.nasm.us/show_bug.cgi?id=3392306

Here's the example code from the Forum:

;-----------------------
default rel
bits 64

section .rodata ; .data - same result - fbk
data dq 42
; comment out otherdata to make it work
otherdata dw 100

section .text

global _testFunc
_testFunc:
     mov rax, [data]
     ret
;--------------------

Here's my attempt to disassemble the resulting .o files with ndisasm: 
(-b64 -e0x120)

this is with 2.11.06

00000000  488B0500000000    mov rax,[rel 0x7]
00000007  C3                ret

I guess it's "right"?


this is with 2.11.08

00000000  488B05F8000000    mov rax,[rel 0xff]
00000007  C3                ret

Apparently not right.

I've looked at a diff, but I don't know enough C to make much of it. 
Simply removing the "=" in the very first change does not seem to help. :)

Perhaps related... Last I knew, Apple was distributing Nasm-0.98.40. It 
is as if they don't like our 2.x.y series at all. Is Eric Christopher 
still around? Do we have any liaison with Apple at all? Are they mad at 
us? Anyone know?

Thanks to all for all you do!

Best,
Frank

Re: [Nasm-devel] Min Max preprocessor operator

[anonymous c. <nas...@us...>]

> I tried to implement it via macros but this won't work. Any ideas? Maybe
> add the min, max operator to the preprocessor?

you want eval.c support for the x ? y : z
conditional operator

http://sourceforge.net/p/nasm/feature-requests/29/
http://sourceforge.net/p/nasm/patches/3/

[Nasm-devel] Min Max preprocessor operator

[Lars M. <lar...@te...>]

Hello,
today i stumbled upon the following problem: imagine you'r defining a 
struct via constants and you want to use a c union-like layout, for example:

%define TYPE_ARRAY_OFFSET_DATA_TYPE     0x0000
%define TYPE_ARRAY_OFFSET_LENGTH        0x0004
%define TYPE_ARRAY_SIZE                 0x0008

%define TYPE_STRUCT_ .... [and so on]

%define TYPE_OFFSET_INDEX               0x0000
%define TYPE_OFFSET_LAYOUT 0x0004                              ; union 
of type_array, type_struct
%define TYPE_SIZE                       max TYPE_ARRAY_SIZE, 
TYPE_STRUCT_SIZE

%define TYPE_LAYOUT_ARRAY_DATA_TYPE     ( TYPE_OFFSET_LAYOUT + 
TYPE_ARRAY_OFFSET_DATA_TYPE )
%define TYPE_LAYOUT_ARRAY_LENGTH        ( TYPE_OFFSET_LAYOUT + 
TYPE_ARRAY_OFFSET_LENGTH )


thus you have a full type_array or type_struct structure at 
TYPE_OFFSET_LAYOUT. Now I need the max-macro to get the maximum size of 
both structures.
I could calc this value manually, but this is not the sense of a 
preprocessor.

I tried to implement it via macros but this won't work. Any ideas? Maybe 
add the min, max operator to the preprocessor?

Best wishes!

Re: [Nasm-devel] nasm-2.11.07 tar files still do not exist months after release

[Cyrill G. <gor...@gm...>]

On Mon, Feb 16, 2015 at 03:51:38PM +0700, Somchai Smythe wrote:
> Hello,
> 
> http://nasm.us/ lists nasm-2.11.06 as the latest.
> 
> http://www.nasm.us/pub/nasm/releasebuilds/ has no 2.11.07 subdirectory.
> 
> http://repo.or.cz/w/nasm.git says nasm-2.11.07 was tagged on 2014-12-09.
> 
> Is there a different website URL I should be using now to find the
> 2.11.07 release tar files?

We've a problem in our build farm for now, sorry for inconvenience.
Hopefully get fixed more-less soon.

[Nasm-devel] nasm-2.11.07 tar files still do not exist months after release

[Somchai S. <bur...@gm...>]

Hello,

http://nasm.us/ lists nasm-2.11.06 as the latest.

http://www.nasm.us/pub/nasm/releasebuilds/ has no 2.11.07 subdirectory.

http://repo.or.cz/w/nasm.git says nasm-2.11.07 was tagged on 2014-12-09.

Is there a different website URL I should be using now to find the
2.11.07 release tar files?

Re: [Nasm-devel] NASM and LCC; x86nasm.md

[H. P. A. <hp...@zy...>]

On 01/26/2015 01:31 PM, Yuri Zaporozhets wrote:
> Hi guys,
> 
> Does somebody know what happened to John Coffman?
> 
> I noticed that Dave Hanson's LCC is now on github, and was wandering
> how to incorporate x86nasm.md into it. John originally wrote this file.
> 

I haven't heard from him since Dec 2008, but I do have his email address
from that time.

	-hpa

[Nasm-devel] NASM and LCC; x86nasm.md

[Yuri Z. <r_...@ya...>]

Hi guys,

Does somebody know what happened to John Coffman?

I noticed that Dave Hanson's LCC is now on github, and was wandering
how to incorporate x86nasm.md into it. John originally wrote this file.

-- 
Regards,
Yuri

[Nasm-devel] All the programmers of machine code that complained about Assembly changed their minds about the Assembly?

[françai s <rom...@gm...>]

According to Richard Hamming in the book The Art of doing science and
engineering, page 26, one of the main complaints of programmers of machine
code of  1st generation that did not accept the Assembly was that you never
know where the Assembly puts things.

The original of statement that I said above says (my emphasis):

Finally, the more complete, and more useful, Symbolic Assembly Program
(SAP) was devised-after more years than you are apt to believe During Which
most programmers continued Their heroic absolute binary programming. At the
SAP team first Appeared I would guess about 1% of the older programmers
Were interested in it-using SAP was "sissy stuff" and the real programmers
would not stoop to wasting machine capacity to do the assembly.Yes!
Programmers wanted at part of it, though pressed When They Had to admit
Their old methods used more machine time in locating and fixing up errors
than the SAP program ever used. One of the main complaints was When using
the symbolic system you do not know where anything was in storage - though
in the early days we supplied the mapping of symbolic to current storage,
and believe it or not they later lovingly pored over such sheets rather
than They did not realize a need to know information que if They stuck to
operating Within the system -no! When correcting errors They preferred to
do it in absolute binary.
Reference:
http://worrydream.com/refs/Hamming-TheArtOfDoingScienceAndEngineering.pdf

I do not understand why 1% of programmers that coded in machine code that
did not accept the Assembly then changed his mind about the Assembly.

I asked the question based on the following part: One of the main
complaints was When using the symbolic system you do not know where
anything was in storage.

I do not understand why 1% of machine code programmers who believed that
the Assembly was heresy changed their minds about the Assembly.

All the programmers of machine code that complained about Assembly changed
their minds about the Assembly?

Re: [Nasm-devel] Build robot problems

[Cyrill G. <gor...@gm...>]

On Fri, Dec 19, 2014 at 10:36:50PM +0900, NAKAI Yuta wrote:
> Hi, it seems that this is related to '-Werror=missing-declarations'.
> At this commit (http://repo.or.cz/w/nasm.git/commit/236f7949e44434f19a3f72fa4650362f612da735), '-Werror=missing-declarations' was added to CFLAGS.
> When '-Werror=missing-declarations' is specified, it seems that configure defines 'inline' mistakenly.
> 
> config.h when -Werror=missing-declarations is specified
> /* Define to `__inline__' or `__inline' if that's what the C compiler
>    calls it, or to nothing if 'inline' is not supported under any name.  */
> #ifndef __cplusplus
> #define inline 
> #endif
> 
> config.log
> configure:5169: checking for inline
> configure:5185: x86_64-w64-mingw32-gcc -c -march=x86-64 -mtune=generic -pipe -Os -foptimize-strlen -fstack-protector-strong --param=ssp-buffer-size=4 -D__USE_MINGW_ANSI_STDIO=1 -D_FORTIFY_SOURCE=2 -W -Wall -std=c99 -pedantic -Werror=implicit -Werror=missing-braces -Werror=return-type -Werror=trigraphs -Werror=pointer-arith -Werror=missing-prototypes -Werror=missing-declarations -Werror=comment -Werror=vla  conftest.c>&5
> conftest.c:32:14: error: no previous declaration for 'foo' [-Werror=missing-declarations]
>  inline foo_t foo () {return 0; }
>               ^
> cc1.exe: some warnings being treated as errors
> configure:5185: $? = 1
> 
> On the contrary, config.h when -Werror=missing-declarations is 'not' specified
> /* Define to `__inline__' or `__inline' if that's what the C compiler
>    calls it, or to nothing if 'inline' is not supported under any name.  */
> #ifndef __cplusplus
> /* #undef inline */
> #endif
> 
> I think putting PA_ADD_CFLAGS([-Werror=missing-declarations]) after AC_C_INLINE in configure.in fixes this problem.
> 
> Yuta

Many thanks for info. I'll take a look.

	Cyrill

Re: [Nasm-devel] Build robot problems

[NAKAI Y. <na...@li...>]

Hi, it seems that this is related to '-Werror=missing-declarations'.
At this commit (http://repo.or.cz/w/nasm.git/commit/236f7949e44434f19a3f72fa4650362f612da735), '-Werror=missing-declarations' was added to CFLAGS.
When '-Werror=missing-declarations' is specified, it seems that configure defines 'inline' mistakenly.

config.h when -Werror=missing-declarations is specified
/* Define to `__inline__' or `__inline' if that's what the C compiler
   calls it, or to nothing if 'inline' is not supported under any name.  */
#ifndef __cplusplus
#define inline 
#endif

config.log
configure:5169: checking for inline
configure:5185: x86_64-w64-mingw32-gcc -c -march=x86-64 -mtune=generic -pipe -Os -foptimize-strlen -fstack-protector-strong --param=ssp-buffer-size=4 -D__USE_MINGW_ANSI_STDIO=1 -D_FORTIFY_SOURCE=2 -W -Wall -std=c99 -pedantic -Werror=implicit -Werror=missing-braces -Werror=return-type -Werror=trigraphs -Werror=pointer-arith -Werror=missing-prototypes -Werror=missing-declarations -Werror=comment -Werror=vla  conftest.c>&5
conftest.c:32:14: error: no previous declaration for 'foo' [-Werror=missing-declarations]
 inline foo_t foo () {return 0; }
              ^
cc1.exe: some warnings being treated as errors
configure:5185: $? = 1

On the contrary, config.h when -Werror=missing-declarations is 'not' specified
/* Define to `__inline__' or `__inline' if that's what the C compiler
   calls it, or to nothing if 'inline' is not supported under any name.  */
#ifndef __cplusplus
/* #undef inline */
#endif

I think putting PA_ADD_CFLAGS([-Werror=missing-declarations]) after AC_C_INLINE in configure.in fixes this problem.

Yuta

>On 12/17/2014 05:01 PM, H. Peter Anvin wrote:
>> There seems to be some bizarre mingw problem that is keeping the build
>> robot from working.  It keeps complaining about duplicate symbols, but
>> all those duplicate symbols seem to come from the standard library.
>> 
>> Trying to figure out what is going on.
>> 
>
>I can't tell for sure if this is a NASM bug or a Mingw bug.  If I remove
>-std=c99 from the Makefile it works, but I can't reproduce the error.
>
>    -hpa 		 	   		  

Re: [Nasm-devel] Build robot problems

[H. P. A. <hp...@zy...>]

On 12/17/2014 05:01 PM, H. Peter Anvin wrote:
> There seems to be some bizarre mingw problem that is keeping the build
> robot from working.  It keeps complaining about duplicate symbols, but
> all those duplicate symbols seem to come from the standard library.
> 
> Trying to figure out what is going on.
> 

I can't tell for sure if this is a NASM bug or a Mingw bug.  If I remove
-std=c99 from the Makefile it works, but I can't reproduce the error.

	-hpa

[Nasm-devel] Build robot problems

[H. P. A. <hp...@zy...>]

There seems to be some bizarre mingw problem that is keeping the build
robot from working.  It keeps complaining about duplicate symbols, but
all those duplicate symbols seem to come from the standard library.

Trying to figure out what is going on.

	-hpa

Re: [Nasm-devel] [nasm:master] ndisasm: Prevent nil dereference on registerd decoding

[anonymous c. <nas...@us...>]

> So the right thing is to extend the bounds register array to include
> these non-registers.

+1 for bnd0-15 in regs.dat

Re: [Nasm-devel] [nasm:master] ndisasm: Prevent nil dereference on registerd decoding

[H. P. A. <hp...@zy...>]

On 12/14/2014 11:48 AM, nasm-bot for Cyrill Gorcunov wrote:
> Commit-ID:  9b05974022da69c12b8b190c6ad100402771e5ad
> Gitweb:     http://repo.or.cz/w/nasm.git?a=commitdiff;h=9b05974022da69c12b8b190c6ad100402771e5ad
> Author:     Cyrill Gorcunov <gor...@gm...>
> AuthorDate: Sun, 14 Dec 2014 22:44:54 +0300
> Committer:  Cyrill Gorcunov <gor...@gm...>
> CommitDate: Sun, 14 Dec 2014 22:44:54 +0300
> 
> ndisasm: Prevent nil dereference on registerd decoding
> 
> The sequence | 0x0F 0x1B 0x75 | get matched into
> one of BNDx instruction which register value 6
> which is of course out of possible BND registers
> implemented in hardware at the moment leading to
> nil dereference.
> 
> Instead lets use a macro in whichreg() helper
> which would test the registers bounds and force
> the caller to try another template if register is
> out of range. In the case above it simply means
> ndisasm instead of crashing outputs
> 
>  | 00000000  0F                db 0x0f
>  | 00000001  1B                db 0x1b
>  | 00000002  75                db 0x75
> 
> http://bugzilla.nasm.us/show_bug.cgi?id=3392289
> 
> Reported-by: Hanno Boeck <ha...@hb...>
> Signed-off-by: Cyrill Gorcunov <gor...@gm...>
> 

I don't agree with this.  We normally decode even unimplemented
registers, for example:

	mov eax,cr5

... is handled correctly by NASM even though cr5 doesn't exist.
Similarly segment registers 6 and 7 are supported.

So the right thing is to extend the bounds register array to include
these non-registers.

	-hpa

Re: [Nasm-devel] Syslinux 6.03 build is broken by nasm upgrade 2.11.05 to 2.11.06

[suresh b. <k_s...@ya...>]

Hi,
vmovd works only in 32-bit with xmm1, if you want same thing to work in 64-bit you need to use the vmovq instruction with xmm1.
regards,sureshbk.
 

     On Tuesday, December 2, 2014 6:21 AM, Frank Kotler <fbk...@my...> wrote:
   

 H. Peter Anvin wrote:

...
> ... at which point we should make a 2.11.07.

Wait, wait, we have another one.

http://forum.nasm.us/index.php?topic=2004.new#new

Claims "vmovd rdx, xmm0" won't assemble, but the Intel compiler 
generates it.

I have no idea - I'm on a 32-bit machine... Thanks to all for your efforts!

Best,
Frank


------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Nasm-devel mailing list
Nas...@li...
https://lists.sourceforge.net/lists/listinfo/nasm-devel


    

Re: [Nasm-devel] Syslinux 6.03 build is broken by nasm upgrade 2.11.05 to 2.11.06

[Frank K. <fbk...@my...>]

H. Peter Anvin wrote:

...
> ... at which point we should make a 2.11.07.

Wait, wait, we have another one.

http://forum.nasm.us/index.php?topic=2004.new#new

Claims "vmovd rdx, xmm0" won't assemble, but the Intel compiler 
generates it.

I have no idea - I'm on a 32-bit machine... Thanks to all for your efforts!

Best,
Frank

Re: [Nasm-devel] Syslinux 6.03 build is broken by nasm upgrade 2.11.05 to 2.11.06

[H. P. A. <hp...@zy...>]

On 11/30/2014 12:54 PM, Cyrill Gorcunov wrote:
> On Tue, Nov 25, 2014 at 12:15:13AM -0500, Frank Kotler wrote:
>> suresh babu wrote:
>>> Hi,
>>>
>>>
>>> I have not found any source code link in http://www.nasm.us/ .
>>
>> http://www.nasm.us/pub/nasm/releasebuilds/2.11.05/nasm-2.11.05.zip
>>
>> Other extensions are the same thing in different compression formats. 
>> Take your pick. Not too clearly labeled as source archives, I guess. 
>> 2.11.06 is up, if you want to work with the latest...
>>
>> Thanks for your interest!
> 
> Should be fixed in latest snapshot. Please verify once time permit.
> 

... at which point we should make a 2.11.07.

	-hpa

Re: [Nasm-devel] Syslinux 6.03 build is broken by nasm upgrade 2.11.05 to 2.11.06

[Cyrill G. <gor...@gm...>]

On Tue, Nov 25, 2014 at 12:15:13AM -0500, Frank Kotler wrote:
> suresh babu wrote:
> > Hi,
> > 
> > 
> > I have not found any source code link in http://www.nasm.us/ .
> 
> http://www.nasm.us/pub/nasm/releasebuilds/2.11.05/nasm-2.11.05.zip
> 
> Other extensions are the same thing in different compression formats. 
> Take your pick. Not too clearly labeled as source archives, I guess. 
> 2.11.06 is up, if you want to work with the latest...
> 
> Thanks for your interest!

Should be fixed in latest snapshot. Please verify once time permit.

Re: [Nasm-devel] [PATCH] Fix 256-bit vmovntps

[suresh b. <k_s...@ya...>]

The change made is correct.
 

     On Sunday, November 30, 2014 2:50 AM, Cyrill Gorcunov <gor...@gm...> wrote:
   

 On Sat, Nov 29, 2014 at 09:53:15PM +0100, Henrik Gramner wrote:
> Ping. Can anyone get this pushed?
> 

Ouch. sorry, managed to miss it. Will do, thanks a lot!

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Nasm-devel mailing list
Nas...@li...
https://lists.sourceforge.net/lists/listinfo/nasm-devel


    

Re: [Nasm-devel] [PATCH] Fix 256-bit vmovntps

[Cyrill G. <gor...@gm...>]

On Sat, Nov 29, 2014 at 09:53:15PM +0100, Henrik Gramner wrote:
> Ping. Can anyone get this pushed?
> 

Ouch. sorry, managed to miss it. Will do, thanks a lot!

Re: [Nasm-devel] [PATCH] Fix 256-bit vmovntps

[Henrik G. <he...@gr...>]

Ping. Can anyone get this pushed?

Henrik

On Wed, Nov 12, 2014 at 6:49 PM, Henrik Gramner <he...@gr...> wrote:
> Signed-off-by: Henrik Gramner <he...@gr...>
> ---
>  insns.dat | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/insns.dat b/insns.dat
> index 4191075..baa7b9d 100644
> --- a/insns.dat
> +++ b/insns.dat
> @@ -2490,7 +2490,7 @@ VMOVNTDQA xmmreg,mem128                   [rm:    vex.128.66.0f38 2a /r]                  AVX,SANDYBRIDGE
>  VMOVNTPD       mem128,xmmreg                   [mr:    vex.128.66.0f 2b /r]                    AVX,SANDYBRIDGE
>  VMOVNTPD       mem256,ymmreg                   [mr:    vex.256.66.0f 2b /r]                    AVX,SANDYBRIDGE
>  VMOVNTPS       mem128,xmmreg                   [mr:    vex.128.0f 2b /r]                       AVX,SANDYBRIDGE
> -VMOVNTPS       mem128,ymmreg                   [mr:    vex.256.0f 2b /r]                       AVX,SANDYBRIDGE
> +VMOVNTPS       mem256,ymmreg                   [mr:    vex.256.0f 2b /r]                       AVX,SANDYBRIDGE
>  VMOVSD         xmmreg,xmmreg*,xmmreg           [rvm:   vex.nds.lig.f2.0f 10 /r]                AVX,SANDYBRIDGE
>  VMOVSD         xmmreg,mem64                    [rm:    vex.lig.f2.0f 10 /r]                    AVX,SANDYBRIDGE
>  VMOVSD         xmmreg,xmmreg*,xmmreg           [mvr:   vex.nds.lig.f2.0f 11 /r]                AVX,SANDYBRIDGE
> --
> 1.8.3.2
>

Re: [Nasm-devel] Syslinux 6.03 build is broken by nasm upgrade 2.11.05 to 2.11.06

[Frank K. <fbk...@my...>]

suresh babu wrote:
> Hi,
> 
> 
> I have not found any source code link in http://www.nasm.us/ .

http://www.nasm.us/pub/nasm/releasebuilds/2.11.05/nasm-2.11.05.zip

Other extensions are the same thing in different compression formats. 
Take your pick. Not too clearly labeled as source archives, I guess. 
2.11.06 is up, if you want to work with the latest...

Thanks for your interest!

Best,
Frank

Re: [Nasm-devel] Syslinux 6.03 build is broken by nasm upgrade 2.11.05 to 2.11.06

[suresh b. <k_s...@ya...>]

Hi,

I have not found any source code link in http://www.nasm.us/ . So I got 2.07 nasm from source forge.net   Can anyone send me the latest source of nasm?
Let me build to produce this build error?

regards,sureshbk.


     On Monday, November 24, 2014 4:49 PM, Cyrill Gorcunov <gor...@gm...> wrote:
   

 On Mon, Nov 24, 2014 at 11:06:54AM +0000, Andrew Walrond wrote:
> Don't know if this is syslinux or nasm problem, but since HPA seems 
> active in both, I thought I'd post it here. Build fails like this:
> 
> nasm -f elf -Ox  -g -F dwarf -DDATE_STR="'6.03'" \
>          -DHEXDATE="0x54730e41" \
>          -Di386 \
>          -I/source/sys/syslinux/core/ \
>          -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d 
> /source/sys/syslinux/core/ldlinux.asm
> diskstart.inc:438: error: symbol references not supported in 
> preprocess-only mode
> diskstart.inc:438: error: non-constant value given to `%if'
> diskstart.inc:439: error: symbol references not supported in 
> preprocess-only mode
> diskstart.inc:439: error: non-constant value given to `%assign'
> /source/sys/syslinux/core/ldlinux.asm:26: fatal: unable to open include 
> file `head.inc'
> /source/sys/syslinux/core/Makefile:156: recipe for target 'ldlinux.o' failed
> 
> Hope that's useful.

Looks like -M option get screwed. Thanks for report I will try to
take a look in a couple of days.

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Nasm-devel mailing list
Nas...@li...
https://lists.sourceforge.net/lists/listinfo/nasm-devel