In our previous episode, Jonas Maebe said:
I also don't know where the -Xd comes from in the above compiler
invocation. If you added that yourself, remove it again.
I inherited it from the buildcrosssnapshot script found in
fpcbuild-2.6.2.zip, and never even thought about its effect.
On 08 May 2013, at 14:01, Marco van de Voort wrote:
In our previous episode, Jonas Maebe said:
I also don't know where the -Xd comes from in the above
compiler invocation. If you added that yourself, remove it again.
I inherited it from the buildcrosssnapshot script found in
In our previous episode, Jonas Maebe said:
That script probably hasn't been used for ages. It's probably best to
remove it in order to prevent confusion like you are encountering.
Please don't, since that just makes it hard to add anything.
I don't understand what you mean by this. How
On 08 May 2013, at 14:57, Marco van de Voort wrote:
In our previous episode, Jonas Maebe said:
That script probably hasn't been used for ages. It's probably
best to
remove it in order to prevent confusion like you are encountering.
Please don't, since that just makes it hard to add
In our previous episode, Jonas Maebe said:
svn) and probably hasn't worked correctly in 10 years or so (if it
ever worked really correctly, given that adding -Xd to OPT never
never
was correct).
It was the best that could be done then.
The best that could have been done was to add
On 08/05/13 16:45, Marco van de Voort wrote:
In our previous episode, Jonas Maebe said:
svn) and probably hasn't worked correctly in 10 years or so (if it
ever worked really correctly, given that adding -Xd to OPT never
never
was correct).
It was the best that could be done then.
The best
Continuation of discussion from Cross-building on from Linux/x86-64 to
Linux/i386 (was: Win64 release of FPC 2.6.2 missing)
On 07/05/13 19:34, Jonas Maebe wrote:
On 07 May 2013, at 18:17, patspiper wrote:
Cross compiler building is broken for FPC 2.7.1 on Ubuntu and Fedora. I had
submitted
On 07 May 2013, at 19:27, patspiper wrote:
It is the other way round. My OS is 32 bit Ubuntu and one of the targets is
Linux/x86-64, so I assume you mean the 64 bit paths and not the 32 bit ones.
I tried setting CROSSOPT (CROSSOPT=-XR/usr/lib64
-Fl/usr/lib/gcc/i686-linux-gnu/4.7/64), but
On 07/05/13 21:01, Jonas Maebe wrote:
On 07 May 2013, at 19:27, patspiper wrote:
It is the other way round. My OS is 32 bit Ubuntu and one of the targets is
Linux/x86-64, so I assume you mean the 64 bit paths and not the 32 bit ones.
I tried setting CROSSOPT (CROSSOPT=-XR/usr/lib64
On 07 May 2013, at 22:43, patspiper wrote:
On 07/05/13 21:01, Jonas Maebe wrote:
That is by design. fpmake runs on the host, not on the target.
/home/user1/Programs/fpc/fpsrc/exported/2.7.1/compiler/ppc is a native
compiler (so i386-i386 in your case). Options specific to compiling fpmake
On 08/05/13 00:01, Jonas Maebe wrote:
Cross compiling for Linux/x86_64 with
FPCMAKEOPT=-Fl/usr/lib/gcc/i686-linux-gnu/4.7 went past the previous error
point, but yet yielded another error:
./fpmake compile --localunitdir=.. --os=linux --cpu=x86_64 -o -Px86_64 -o
-XPx86_64-linux- -o -Xr -o
11 matches
Mail list logo
