Proper solution to nasm compilation problems in Borland context.

diff --git a/crypto/perlasm/x86nasm.pl b/crypto/perlasm/x86nasm.pl
index 5009acb4b315566a7ca187be718a30959d9949b4..4bdb3fe1809c13155ddcdcacbaced01fb3f934f8 100644 (file)
--- a/crypto/perlasm/x86nasm.pl
+++ b/crypto/perlasm/x86nasm.pl
@@ -221,7 +221,15 @@ sub using486
 
 sub main'file
        {
-       push(@out, "segment .text use32\n");
+       local $tmp;
+       $tmp=<<___;
+%ifdef __omf__
+section        code    use32 class=code
+%else
+section        .text
+%endif
+___
+       push(@out,$tmp);
        }
 
 sub main'function_begin

diff --git a/util/pl/BC-32.pl b/util/pl/BC-32.pl
index 897ae9d8249c1fc44a9f32a7a25787f39271d21f..9de2d417d91097123830ac7aa356084e9c1f65ca 100644 (file)
--- a/util/pl/BC-32.pl
+++ b/util/pl/BC-32.pl
@@ -51,7 +51,7 @@ $lfile='';
 $shlib_ex_obj="";
 $app_ex_obj="c0x32.obj"; 
 
-$asm='nasmw -f obj';
+$asm='nasmw -f obj -d__omf__';
 $asm.=" /Zi" if $debug;
 $afile='-o';