Re[6]: [fpc-devel] is smartlink of Win32 DLLs broken again? And a old FreeBSD port problem additionaly

2005-04-28 Thread Pavel V. Ozerski
Hello FPC Team,

Please explain me why my yesterday's work remained be ignored?
Practically, I think, I solved a problem at fixed a bug. Are you
discordant with my way of solution or are waiting for diff?


-- 
Best regards,
 Pavelmailto:[EMAIL PROTECTED]



___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


[fpc-devel] is smartlink of Win32 DLLs broken again? And a old FreeBSD port problem additionaly

2005-04-27 Thread Pavel V. Ozerski
Hello all,

1) I tried now to build a dll with {$smartlink on} using 1.9.9 compiler
built at beginning of April. The created DLL did not contain export
names. An analysis of generated asm code pointed that although a
global label at beginning of .rva-containing asm-file has been
correctly created but the PASCALMAIN module did not contain a
reference to this label. At result, all EDATAs sould be eliminated at
linking stage.

2) Because I braced up, to write this letter :), I would also report a
old problem which I got using an old 1.1 FreeBSD port. I needed to
build a shared UDF library for MySQL. While loading created .so file,
I got an error message - something like main entry point not found.
An analysis of asm code demonstated that global main function mas
named not main but had a name combined from a shared module name and
_main, therefore the dynamic linker could not find main entry point.
At that time I solved this problem editing the asm code but this way
seems to be not normal.

Sincerely, Pavel



___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel


Re: [fpc-devel] is smartlink of Win32 DLLs broken again? And a old FreeBSD port problem additionaly

2005-04-27 Thread Peter Vreman
 Hello all,

 1) I tried now to build a dll with {$smartlink on} using 1.9.9 compiler
 built at beginning of April. The created DLL did not contain export
 names. An analysis of generated asm code pointed that although a
 global label at beginning of .rva-containing asm-file has been
 correctly created but the PASCALMAIN module did not contain a
 reference to this label. At result, all EDATAs sould be eliminated at
 linking stage.

Maybe a problem with binutils. The stripping of .stabs sections (ld -s
or using strip) is also broken with recent binutils. We can't use old
binutils since they can't link with recent cygwin libraries.

Since the problem is not in FPC code we can't fix it.




___
fpc-devel maillist  -  fpc-devel@lists.freepascal.org
http://lists.freepascal.org/mailman/listinfo/fpc-devel