[fpc-devel] test suite, problem with missing libraries on the target

2011-05-23 Thread Bernd Mueller
Hello, I am running the test suite with remote execution (from a Windows host) on an ARM-Linux target. Some test programs fail at runtime, because they depend on libraries, which were not automatically copied to the target. For example: Failed to run test/tlib1b.pp 2011/01/21 18:06:08 (16

Re: [fpc-devel] test suite, problem with missing libraries on the target

2011-05-23 Thread Jonas Maebe
On 23 May 2011, at 11:49, Bernd Mueller wrote: I am running the test suite with remote execution (from a Windows host) on an ARM-Linux target. Some test programs fail at runtime, because they depend on libraries, which were not automatically copied to the target. For example: Failed to

Re: [fpc-devel] test suite, problem with missing libraries on the target

2011-05-27 Thread Bernd Mueller
Jonas Maebe wrote: On 23 May 2011, at 11:49, Bernd Mueller wrote: I am running the test suite with remote execution (from a Windows host) on an ARM-Linux target. Some test programs fail at runtime, because they depend on libraries, which were not automatically copied to the target. For examp

Re: [fpc-devel] test suite, problem with missing libraries on the target

2011-05-27 Thread Jonas Maebe
On 27 May 2011, at 14:56, Bernd Mueller wrote: I have enough FLASH memory, so I am not using TEST_DELTEMP=1. I had a look into the test suite source and I think, that the test suite is not able to copy the libraries to the target. I attached a small patch, which could be a solution for the

Re: [fpc-devel] test suite, problem with missing libraries on the target

2011-05-27 Thread Bernd Mueller
Jonas Maebe wrote: On 27 May 2011, at 14:56, Bernd Mueller wrote: If you think, this patch could be the right way to copy the libraries, I would submit a second patch which expands all required %needlibrary directives. Isn't it easier to simply copy all compiled libraries to the target when

Re: [fpc-devel] test suite, problem with missing libraries on the target

2011-05-30 Thread Bernd Mueller
Jonas Maebe wrote: Isn't it easier to simply copy all compiled libraries to the target when they are compiled (just like compiled test programs are copied)? this second approach (which works well for me) copies the libraries when the are compiled. No need to expand the %needlibrary directive

Re: [fpc-devel] test suite, problem with missing libraries on the target

2011-05-30 Thread Jonas Maebe
On 30 May 2011, at 11:04, Bernd Mueller wrote: Jonas Maebe wrote: Isn't it easier to simply copy all compiled libraries to the target when they are compiled (just like compiled test programs are copied)? this second approach (which works well for me) copies the libraries when the are com

Re: [fpc-devel] test suite, problem with missing libraries on the target

2011-05-30 Thread Bernd Mueller
Jonas Maebe wrote: On 30 May 2011, at 11:04, Bernd Mueller wrote: Jonas Maebe wrote: Isn't it easier to simply copy all compiled libraries to the target when they are compiled (just like compiled test programs are copied)? this second approach (which works well for me) copies the libraries

Re: [fpc-devel] test suite, problem with missing libraries on the target

2011-05-30 Thread Jonas Maebe
On 30 May 2011, at 11:19, Bernd Mueller wrote: Jonas Maebe wrote: Why do you limit it to Linux targets? I am not sure about the other targets. LibraryFileName:= 'lib' + ForceExtension(SplitFileName(PPFile[current]), 'so'); The above code builds the library name out of the test program n

Re: [fpc-devel] test suite, problem with missing libraries on the target

2011-05-30 Thread Bernd Mueller
Jonas Maebe wrote: On 30 May 2011, at 11:19, Bernd Mueller wrote: Jonas Maebe wrote: Why do you limit it to Linux targets? I am not sure about the other targets. LibraryFileName:= 'lib' + ForceExtension(SplitFileName(PPFile[current]), 'so'); The above code builds the library name out of

Re: [fpc-devel] test suite, problem with missing libraries on the target

2011-05-30 Thread Jonas Maebe
On 30 May 2011, at 11:37, Bernd Mueller wrote: Jonas Maebe wrote: Windows is not supported as a remote target, but it's indeed not correct for all unix targets either. The prefix of a library is always "lib" on all targets, afaik. The suffix is available via dynlibs.SharedSuffix. The down

RE: [fpc-devel] test suite, problem with missing libraries on the target

2011-05-30 Thread Pierre Free Pascal
> -Message d'origine- > De : fpc-devel-boun...@lists.freepascal.org [mailto:fpc-devel- > boun...@lists.freepascal.org] De la part de Bernd Mueller > Envoyé : lundi 30 mai 2011 11:38 > À : FPC developers' list > Objet : Re: [fpc-devel] test suite, problem w

Re: [fpc-devel] test suite, problem with missing libraries on the target

2011-05-30 Thread Bernd Mueller
Pierre Free Pascal wrote: Just add a LibExt constant to dotest.pp source with the same conditionals as for ExeExt, this should be enough. const ObjExt='o'; PPUExt='ppu'; {$ifdef UNIX} ExeExt=''; LibExt='so'; {$else UNIX} {$ifdef MACOS} ExeExt=''; LibExt='so'; {$else MACOS} Ex

Re: [fpc-devel] test suite, problem with missing libraries on the target

2011-05-30 Thread Bernd Mueller
Jonas Maebe wrote: Maybe better would be to hardcode .so for Linux and FreeBSD, and use dynlibs.SharedSuffix for all other targets. maybe I am missing something, but wouldn't dynlibs.SharedSuffix retrieve the library suffix for the host? So, when I am crosscompiling from Windows, I would ge

Re: [fpc-devel] test suite, problem with missing libraries on the target

2011-05-30 Thread Jonas Maebe
On 30 May 2011, at 13:53, Bernd Mueller wrote: Jonas Maebe wrote: Maybe better would be to hardcode .so for Linux and FreeBSD, and use dynlibs.SharedSuffix for all other targets. maybe I am missing something, but wouldn't dynlibs.SharedSuffix retrieve the library suffix for the host? Y