[fpc-pascal] fpc and intel vtune (now about gprof)

Tomas Hajny XHajT03 at mbox.vol.cz
Tue Apr 25 15:19:37 CEST 2006

>> đŁÔŇ ëĎÓÁŇĹ×ÓËÉĘ wrote:
>> No, except that you have to provide its runtime libraries.
> Well (guess), if you mean, that libc.dll is a part of cygwin, it's not a
> bad idea, but "-lc" thing doesn't look like a rebus or a charade, it's
> like an enigma:)

The error message is an output of ld.exe, not FPC. ld.exe shouldn't be
hopefully needed any more with the internal linker.

>> > Is it sufficient to build 2.1.x and rename one of "fpc.exe" to operate
>> > both release and development versions (I didn't try, but it seems that
>> the
>> > one ppc386 would be run)?
>> That depends. It could work if you provide proper fpc.cfg in the
>> compiler
>> directory (and no other fpc.cfg exists in other directories) and if you
>> make sure to use different output directories for compilation of your
>> own
>> units.
> I just wanted to avoid experiments and asked for solution:)

If you want to stay on the safe side, change your PATH setting to only
refer to one version at a time (e.g. by calling fpc.exe from a script).
You still need to fulfill the conditions mentioned above. Is there still
something which should be clarified in more detail?



More information about the fpc-pascal mailing list