Hello
With fpc for linux, I need to include a build-id to my executable but I
don't see any option for this.
I found that
http://lists.fedoraproject.org/pipermail/devel/2007-October/112754.html
but it's rather old, maybe something have been done on the subject until
today.
Any
Hi
I'm trying to install fpc 2.4.2 using yum on centos 5.5 :
yum localinstall fpc-2.4.2-1.x86_64.rpm
It fires an error :
Missing dependency : libtinfo.so.5()(64bit) is needed by package
fpc-2.4.2-1.x86_64 (/fpc-2.4.2-1.x86_64)
My searches make me understand that it was part of
Ok, so now it compiles but, I still an an error while linking :
ld.exe: cannot find -lpthread
This is basic crosslinking stuff. You must transfer all the required
libraries from the target system, to be able to crosscompile it to
there(In this case libpthread.so)
On 28 Jan 2011, at 14:33, Julien Devillers wrote:
no here's the end of the -va log :
[0.609] procedure/function Unassigned:UnicodeString;
[0.609] ENDIF FPCOLEVARIANT found
[0.625] Internal error 2006012201
The problem with -va is that the time stamps (the numbers between the square
---
OK, I replaced the -va by -vewunchilbdrqpv (everything except
timestamps).
With that, the error message reports the last line of the unit.
I removed a lot of code to find out that issue happens here
function RoundTo(const AValue: Double; const ADigit: TRoundToRange):
My guess is that it's related to 80bit constants. Win64 doesn't support
80bit extended(according to some of the code, yet other places it
defined pbestrealtype to s80bit). A crosscompiler should defined
FPC_HAS_TYPE_EXTENDED for x86_64-linux, so I don't know whether this is
actually the problem
FPC 2.4.0. Note that simply compiling the compiler is never enough, you
have to perform a full build (make all in the top level fpc directory)
- Yes, That's what I did .
-make OS_TARGET=linux CPU_TARGET=x86_64 clean all
-make OS_TARGET=linux CPU_TARGET=x86_64 install
However, the
However, the internalerror you are getting is inside the external
assembler writer. Since you are compiling for Linux/x86-64, the compiler
should default to using the internal assembler. Are you using a variant
of the -a or -Aas command line options?
Without the -Aas, the unit compiles correctly.
However, the internalerror you are getting is inside the external
assembler writer. Since you are compiling for Linux/x86-64, the compiler
should default to using the internal assembler. Are you using a variant
of the -a or -Aas command line options?
Without the -Aas, the unit compiles correctly.
-pascal] Internal error 2006012201 while cross compiling
Didn't it give a filename and a line number?
Den 27-01-2011 15:34, Julien Devillers skrev:
Hello
I'm building an app from win64 to linux64.
The compilation fires an Internal error 2006012201.
Any idea ?
Regards
Julien
previous episode, Julien Devillers said:
Should I consider that this is a bug of gmkdir ? I get this file with
getGnuWin32.
Use the binutils that come with FPC, not the ones from mingw. mingw's coreutils
package has afaik moved in a different direction since it moved from mingw to
msys.
That also
Hello
I'm building an app from win64 to linux64.
The compilation fires an Internal error 2006012201.
Any idea ?
Regards
Julien
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
Hi
I have a linking error with the following compile command :
è d:\pp\bin\x86_64-win64\fpc lib\snip\snip.dpr -Tlinux -n -va -Mdelphi
-FuD:\pp\bin\x86_64-win64/../../units/$FPCTARGET/
In the above line, I removed lots of includes. The error is (founded in the
below log)
è
Hi
i'm trying to compile fpc 2.4.2 under windows 7 64 bits.
It raises the following error :
make[5]: entrant dans le répertoire « C:/FPC/2.4.2/fpc-2.4.2/rtl/win32 »
c:/gnuwin32/bin/gmkdir.exe -p C:/FPC/2.4.2/fpc-2.4.2/rtl/units/i386-win32
d:/pp_/bin/i386-win32/ppc386.exe -Ur -Xs -O2
Hello
Please can you tell me if :
ppc386 in intend to be used on a i386 platform and ppcx64 on a 64bits
platform regarless the type of app to build
or
both are intend to be used on any plateform. ppc386 to build apps for
i386 systems and ppcx64 to build 64bits apps.
Thanks
Julien
thecross
compiler ?
Am 03.11.2010 18:24, schrieb Julien Devillers:
Ok, I Found them.
thanks
Julien
Out of curiosity and maybe for others that have the same problem:
Where did you find them?
Regards,
Sven
Julien Devillers:
Hello
Please can you tell me if :
ppc386 in intend to be used on a i386 platform and ppcx64 on a 64bits
platform regarless the type of app to build
or
both are intend to be used on any plateform. ppc386 to build apps for
i386 systems and ppcx64 to build 64bits apps
Hello
I'm working on a project which cross compile from win32 to linux64.
Today it uses FPC-2.1.5.
I need to move to fpc 2.4.0.
I downloaded fpc-2.4.0.i386-win32.exe and after some attemps, I
understood that I did not have everything
to cross compile (units dir and some exes). I tried with
-Message d'origine-
De : fpc-pascal-boun...@lists.freepascal.org
[mailto:fpc-pascal-boun...@lists.freepascal.org] De la part de Julien Devillers
Envoyé : mercredi 3 novembre 2010 17:27
À : FPC-Pascal users discussions
Objet : RE: [fpc-pascal] Cross-Compiling win32 - Linux 64,how to get
, at 17:24, Julien Devillers wrote:
The above code returns 1, 2, 3, 3, 4 while it should return 1, 2, 3,
4, 5.
I Built a TMyBits class using strictly the TBits.inc file from fpc
and... the bug does
not appear... !
I'm using lazarus 0.9.28.2 beta and fpc 2.2.4 with linux 64.
Did I miss
Hello
I found a strange behaviour of TBits. Example :
procedure TForm1.Button1Click(Sender: TObject);
var
x:TBits;
begin
x:=TBits.Create();
x[0] := true;
showmessage(inttostr( x.size));
x[1] := false;
showmessage(inttostr( x.size));
x[2] := false;
21 matches
Mail list logo
