PureBasic Forums - English

Demonio,

thanks for your response!

At first, I was also quite surprised, when I saw SYS_FreeString to be referenced rather than _SYS_FreeString. Then, however, I found a bunch of other functions which were also referenced without a leading underscore (e.g., PB_Blue, PB_Green, PB_Red) without causing any linker errors.

I am also afraid that I ran across a PB bug although I do net yet see how I can isolate it...

Is it possible to modify the assembler listing and continue from that (i.e. running the assembler and linker)?

That would proove our ideas - or not.

well, you could try changing all the SYS_FreeString's to the underscored version and use the reassemble command line option (/REASM on windows - unsure about OS X)

Demonio,

thanks for the hint - unfortunately, I can't see how to reassemble under MacOS X (--reasm does not work and --help does not mention reassembly)

Even inspecting the "PureBasic" program folder did not help further...

Does anybody else know how to "reassemble" under Mac OS X?

PB Help wrote:This file can be re-assembled later when the needed modifications have been made

perhaps this means mac os x pbcompiler can't reassemble yet...

I looked at the pbcompiler -h screen too, and I can't see it either...

Ok, I found the origin of the linker errors

Today, I had some time to isolate the problem using a binary division approach (plus some heuristics .

And I found that the FTP-related functions are the reason for the undefined external SYS_FreeString - without FTP functions, everything compiles and links fine.

What I haven't done, however, is to check the situation the other way round: will the error occur when I use FTP-related functions *only* (i.e. without the bunch of other functions I am using)

At least, I have a part of my system running now (sigh)

Ok,

I just tried to run the FTP example which comes with PB - and I got the same error!

Now it's time to submit a bug report...

Thanks for all your help!

great news, nice hunting