Re: [fpc-pascal] Can't configure fppkg

2013-02-14 Thread Krzysztof
Ok, I changed GlobalPrefix to fpc source path (it is /usr/lib/codetyphon/fpcsrc/) but still same result. So my files looks like: fpconf.cfg [Defaults] ConfigVersion=4 GlobalPrefix=/usr/lib/codetyphon/fpcsrc/ LocalPrefix={LocalRepository} Compiler=/usr/lib/codetyphon/fpc/bin/x86_64-linux/fpc

Re: [fpc-pascal] Can't configure fppkg

2013-02-14 Thread Sven Barth
On 14.02.2013 09:07, Krzysztof wrote: Ok, I changed GlobalPrefix to fpc source path (it is /usr/lib/codetyphon/fpcsrc/) but still same result. So my files looks like: Not the SOURCE path. The path which contains the COMPILED units. So this should be '/usr/lib/codytyphon/fpc' (the correct

[fpc-pascal] Re: Fpc Access Violation if AppConfigDir doesn't exist.

2013-02-14 Thread Lukasz Sokol
On 13/02/2013 16:50, Giuliano Colla wrote: IMHO the try..except..finally construct should provide exactly the same functionality as a nested try try [code] except [code] end; finally [code] end; i.e. it should be executed whatever happened in the sections between try and

Re: [fpc-pascal] Re: Fpc Access Violation if AppConfigDir doesn't exist.

2013-02-14 Thread Giuliano Colla
Lukasz Sokol ha scritto: It is subtle, I agree, but in try try [code] finally [code] end; except [code] end; (my version) I can catch the errors of either normal and finally code; I assume that try...finally...end is the more important; it is try...finally.. end that has to go

Re: [fpc-pascal] Re: Fpc Access Violation if AppConfigDir doesn't exist.

2013-02-14 Thread Giuliano Colla
Sven Barth ha scritto: I don't see the point of a else or nonexcept branch. If I want code to be executed in the case that no exception happened (e.g. a Commit for a database transaction) then I put in the block started by the try... One might argue that an additional branch would increase

Re: [fpc-pascal] Compiling arm-embedded fpc

2013-02-14 Thread Michael Ring
I might have found a hack to solve your linking problem for arm-embedded on linux, unfortunately I am not an expert on gnu ld, but perhaps this here gives a hint to somebody that knows how to properly solve your problem: First, create a script names arm-embedded-ld with the following content:

Re: [fpc-pascal] Compiling arm-embedded fpc

2013-02-14 Thread Florian Klämpfl
Am 14.02.2013 20:08, schrieb Michael Ring: I might have found a hack to solve your linking problem for arm-embedded on linux, unfortunately I am not an expert on gnu ld, but perhaps this here gives a hint to somebody that knows how to properly solve your problem: First, create a script

Re: [fpc-pascal] Compiling arm-embedded fpc

2013-02-14 Thread Jeppe Græsdal Johansen
Den 14-02-2013 20:39, Florian Klämpfl skrev: Am 14.02.2013 20:08, schrieb Michael Ring: I might have found a hack to solve your linking problem for arm-embedded on linux, unfortunately I am not an expert on gnu ld, but perhaps this here gives a hint to somebody that knows how to properly solve

Re: [fpc-pascal] Compiling arm-embedded fpc

2013-02-14 Thread Michael Ring
I did a grep through the fpc sourcecode and found a reference in ./compiler/systems/t_linux.pas in an arm related ifdef section add(' .note.gnu.build-id : { *(.note.gnu.build-id) }'); so perhaps this is really missing in arm-embedded target. The patch for for