Hello all,
in freepascal.ru forum a problem has been discussed. FPC 2.1 does not
understand DllProc predefined variable presenting in Delphi RTL:
> Unit
>
> System
>
> Category
>
> miscellaneous routines
>
> var DLLProc: Pointer;
>
> Description
>
> DLLProc is used to specify a procedure that is
Hello Marco,
Thursday, November 10, 2005, 10:53:09 AM, you wrote:
>> Some files of RTL core are under the "full" GPL license, not a LGPL. Is it
>> a new politics of FPC?
MvdV> No. Must have been an oversight/bad copy/paste.
MvdV> If you have more files, don't hesitate to name them. The syscall
Hello all,
I didn't discuss about this idea but now I would say something. Is it
really important, to integrate templates support into compiler? Maybe
an external preprocessing utility should be better? I think, an
integrated complex preprocessor can slow the compiling process very
much even if a s
Hello Peter,
Thursday, April 28, 2005, 11:37:30 AM, you wrote:
PV> No time, we all have other jobs. Providing a complete diff helps. It can
PV> be verified quicker.
I see a potential problem i my yesterday's solution. Now I use an
initialized variable (or typized constant) which changes its val
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]
Hello all,
It seems, I solved the smartlink problem.
Solution:
1) in pexports.pas, I added into interface part of unit
var
BinaryContainsExports: boolean = false;
2) in pexports.pas, in first line of main body of read_exports
procedure, I added
begin
BinaryContainsExp
Hello all,
I found something that explains a loss of reference from PASCALMAIN
module to edata module. In pmodules.pas, in proc_program procedure an
inserting of this reference is provided.
if assigned(exportlib) and
(target_info.system in [system_i386_win32,system_i386_wdosx
Hello Peter,
PVO> I'm not sure that you are right. There were a solution found that
I can explain that reported smartlink problem is not a binutils
problem. I fixed generated asm code and got correct dll.
EDATA module:
**
.section .bss
.section .edata
.globl _$PROGRAM$_L1
_$PROGRAM$
Hello Peter,
PV> Since the problem is not in FPC code we can't fix it.
I'm not sure that you are right. There were a solution found that
was based on a code generated by compiler. An asm/obj module with
PASCALMAIN conained a reference to a label which was located in an
asm/obj module contained expo
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 b
Hello Marco,
Wednesday, February 16, 2005, 1:32:58 PM, you wrote:
>Currently FPC has special code that forbids property in objects for delphi
>mode.
At least Delphi versions from 2 to 7 support propereties for old-style
objects. This feature is used BTW in KOL library. Some years ago I
implemente
Hello Jonas,
Wednesday, February 16, 2005, 11:24:00 AM, you wrote:
>> 1) Properties for Object type.
Should already work with {$mode Delphi} - if this feature is not
broken again now.
___
fpc-devel maillist - fpc-devel@lists.freepascal.org
http://
Hello all,
10 years ago I programmed a little on ThinkPascal therefore could
point to some inconveniences that seem to be reproduced in FPC.
As is known, common file names are not enough in MacOS to comfortable
file access via shell, they need also two hiden extensions, type and
creator. Think pas
Hello all,
Today I built last compiler (1.9.5) from sources. Then I tried to compile a
small test win32 dll with -CX -XX and got a binary without export
functions entries. That is interesting that using -a option (using
external assembler) solves this problem.
--
Best regards,
Pavel
Hello Peter,
Wednesday, April 28, 2004, 4:02:59 PM, you wrote:
>> Hello all,
>>
>> I have some ideas about the bug #2363 (Unfixed Error export problem).
>> Second way: storing exported items info in PPU.
PV> That is possible. It needs a new ppuentry that will contain the following
PV> items per
Hello all,
I have some ideas about the bug #2363 (Unfixed Error export problem).
I see two ways to solve this problem but I'm not sure that I'm able to
realize them.
First way (may be wrong):
generating edata sections (or their analogs for non-Windows platforms)
vor every unit that contains export
Hello Jonas,
Now I use three E-Mail addresses: [EMAIL PROTECTED],
[EMAIL PROTECTED] and [EMAIL PROTECTED] (the third may
be not included into your mailing list but the first and the second must be
included). If there are exist posts sent from other addreses which are
subscribed by my name please re
Hello all,
I found also a problem with TIniFile (1.9, win32). If I try to read an
information from the same .ini file using standard TIniFile methods
from several instances of application at the same time, sometimes I
get an error opening .INI file. I think, INI file creation flags should
be supple
Hello all,
I found a problem with dynamic arrays of shortstrings and of static
arrays. These structures are not supported in Delphi but usually work
normally in FPC (except this case). But if a dynamic array is declared
as typized constant or a variable with initial value then trying to
resize this
Hello Ingmar,
Wednesday, December 24, 2003, 1:21:32 PM, you wrote:
IT> Bad news :(
IT> Is this true for all {$mode }'s or only {$mode delphi} ?
Why bad, Try to add {$calling oldfpccall} into your source
--
Best regards,
Pavelmailto:[EMAIL PROTECTED]
I try to download last 1.9 sources but cannot access FPC archives via FTP, your
server (ftp://ftp.freepascal.org) seems to be down. What is happened with it?
--
Best regards,
Pavelmailto:[EMAIL PROTECTED]
___
fpc-devel mai
Hello,
After I replaced in t_win32.pas unit a line 698 - from
exportsSection.concat(Tai_symbol.Create(edatalabel,0));
to
exportsSection.concat(Tai_symbol.Create_Global(edatalabel,0));
the smartlinking of Win32 dlls main modules became possible again.
Sincerely, Pavel
Hello,
I'm suspecting that current 1.1 compiler forgets to make public the
label that used to bind .edata to win32 dlls by smartlinking. At
least, the linker cannot find `$PROGRAM$_L1' until I add `.globl
$PROGRAM$_L1' before `$PROGRAM$_L1:' in source of obj module with
.edata.
Best regards,
Pave
Hello Jeff,
Wednesday, April 02, 2003, 3:44:37 AM, you wrote:
JP> I finally decided to make an attmept at compiling fpc from the CVS sources.
JP> (fixes branch, 2003-04-01)
JP> Everything went smooth, except for one small problem:
JP> fpgtk.pp(3032,57) Error: Illegal parameter list
JP> The c
Hello all,
I tried to use some set types as fields in database.
I would put into datebase a structure
tInfo=packed record
date:set of 1..36;
hour:set of 0..23;
end;
Of cource, I must reserve correct count of bytes for database field.
Therefore I checked SizeOf value for this structure. Bu
25 matches
Mail list logo
