On Wed, May 6, 2020 at 8:03 AM Sven Barth via fpc-pascal
wrote:
> Not in the makefile.fpc,
That is unfortunate.
> but fpcmake allows you to pass a list of supported targets (usually -Tall is
> used to allow all targets), but you'd need to pick each one. This does mean
> however that everyone
Bart via fpc-pascal schrieb am Mi., 6.
Mai 2020, 02:33:
> Hi,
>
> Here's the first line of the Lazarus Makefile:
> -
> #
> # Don't edit, this file is generated by FPCMake Version 2.0.0
> #
> default: all
> MAKEFILETARGETS=i386-linux i386-go32v2 i386-win32
Hi Ched,
I run nightly testsuite on a raspberry PiB,
and I did not see anything like that.
Would it be possible for you to send here a simple source file that
shows this behavior together with an explicit command line
for the compilation, to be sure of the precise options you are using:
> 5 maj 2020 kl. 07:19 skrev Sven Barth via fpc-pascal
> :
>
> Am 05.05.2020 um 04:16 schrieb Ryan Joseph via fpc-pascal:
>>
>>
>>> On May 4, 2020, at 10:44 PM, Michael Van Canneyt
>>> wrote:
>>>
>>> That is how enums work by default in Pascal.
>>>
>>> If you don't force scoped
Hello All,
With the 3.2.0-RC1 on a Raspberry PiB running raspbian, most of my software which ran very well when
compiled with fpc 3.0.4 do stop with the error in title when or near a seek() is done in a structured
binary file. I tryed first -O3 then -O2 then -O1 then no optimisation option
On 3/05/20 10:28 pm, Michael Van Canneyt wrote:
On Sun, 3 May 2020, Noel Duffy via fpc-pascal wrote:
On Sun, 3 May 2020 09:57:46 +0200 (CEST) Michael Van Canneyt
wrote:
Yes, please open a bug report. If you attach a small console test
program that
demonstrates the bug (and subsequently
On Wed, May 6, 2020 at 12:19 PM Noel Duffy via fpc-pascal <
fpc-pascal@lists.freepascal.org> wrote:
> So I guess the question is, is it worth the effort to make
> StrToHostAddr6 RFC4291 compliant? Is that something the FPC team would
> want, or do they just not use the sockets unit?
>
There have
Hi,
On Wed, 6 May 2020, Noel Duffy via fpc-pascal wrote:
> Testing would also have to be fairly rigorous to make sure all the
> different formats are handled correctly. I've already done some work to
> make it easy to compare StrToHostAddr6's output to that of inet_pton in
> the C library, so
