[fpc-pascal] Cross-building on from Linux/i386 to Linux/x86-64
jonas.maebe at elis.ugent.be
Wed May 8 15:16:02 CEST 2013
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 anything.
>> I don't understand what you mean by this. How does it make it "hard
>> add anything"? Add what to what?
> To the project.
How does deleting decade-old cruft that confuses people make it hard
to add new things to the project? It's not like I or anyone else is
constantly looking for files that haven't been touched in the past
year and deleting them.
> This is the first time that sb makes a comment about it,
Probably because no one else realised it still exists or tried to use
> before I can even look into it, it is deleted? What kind of
> procedure is
I didn't think much of it because of the aforementioned reasons. It
honestly did not occur to me that somebody would still care about the
existence of that particular script, given that it explicitly
contained references to paths with "cvs" in them and hence hasn't even
been used for a long time by anyone.
>> 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
>> was correct).
> It was the best that could be done then.
The best that could have been done was to add -Xd to CROSSOPT, not to
> And it did work, because back then,
> with the exception of darwin, nothing run on host linked to libc,
> thus not
> needing those paths. That has only changed very recently.
You're right. But in that case I don't understand why -Xt was also
present, given that this option only applies to C libraries as well.
More information about the fpc-pascal