GNAT Community Edition 2018

GNAT Community Edition 2018

[Simon Wright]

.. is available. The macOS arm-elf cross compiler is there too! (phew)

Re: GNAT Community Edition 2018

[eduardsapotski]

пятница, 8 июня 2018 г., 20:58:06 UTC+3 пользователь Simon Wright написал:
> .. is available. The macOS arm-elf cross compiler is there too! (phew)
It's been two days. I probably was the first who downloaded it!)) 
The question remains - how to enable SSL for AWS?!

Re: GNAT Community Edition 2018

[Björn Lundin]

On 2018-06-08 20:15, eduardsapotski@gmail.com wrote:
> The question remains - how to enable SSL for AWS?!

by compiling it yourself. (if it did not change in this dist)
enable it by setting SOCKET = openssl in makefile.conf

-- 
--
Björn

Re: GNAT Community Edition 2018

[Shark8]

On Friday, June 8, 2018 at 11:58:06 AM UTC-6, Simon Wright wrote:
> .. is available. The macOS arm-elf cross compiler is there too! (phew)

Nice -- and it's a 64-bit compiler!
Though it is somewhat disappointing there's no new Dotnet or JVM target.

Re: GNAT Community Edition 2018

[Bill Findlay]

> On Friday, June 8, 2018 at 11:58:06 AM UTC-6, Simon Wright wrote:
> > .. is available. The macOS arm-elf cross compiler is there too! (phew)

On macOS 10.13.5 I get this sort of thing:

> ld: warning: object file (/Users/wf/opt/gnat-2018/lib/gcc/x86_64-apple-darwin16.7.0/7.3.1/adalib/libgnat.a(errno.o)) was built for newer OSX version (10.12) 
than being linked (10.11)

but the object code seems (?) OK.

However, my projects see a ~5% performance regression unless link-time 
optimization is used.

-- 
Bill Findlay

Re: GNAT Community Edition 2018

[Simon Wright]

Bill Findlay <findlaybill@blueyonder.co.uk> writes:

> On macOS 10.13.5 I get this sort of thing:
>
>> ld: warning: object file
>> (/Users/wf/opt/gnat-2018/lib/gcc/x86_64-apple-darwin16.7.0/7.3.1/adalib/libgnat.a(errno.o))
>> was built for newer OSX version (10.12) than being linked (10.11)

Normally that would mean that you're trying to link a binary built on a
later OS than the OS you're currently running; but that doesn't make
sense if you're running 10.13.

You _might_ be able to suppress the warning using

   -largs -Wl,-macosx_version_min,10.11

From 'man ld':

   -macosx_version_min version
      This is set to indicate the oldest Mac OS X version that that the
      output is to be used on.  Specifying a later version enables the
      linker to assumes features of that OS in the out- put file.  The
      format of version is a Mac OS X version number such as 10.4 or
      10.5

Re: GNAT Community Edition 2018

[Bill Findlay]

On 10 Jun 2018, Simon Wright wrote
(in article <lyin6q68a4.fsf@pushface.org>):

> Bill Findlay<findlaybill@blueyonder.co.uk>  writes:
>
> > On macOS 10.13.5 I get this sort of thing:
> >
> > > ld: warning: object file
> > > (/Users/wf/opt/gnat-2018/lib/gcc/x86_64-apple-darwin16.7.0/7.3.1/adalib/lib
> > > gnat.a(errno.o))
> > > was built for newer OSX version (10.12) than being linked (10.11)
>
> Normally that would mean that you're trying to link a binary built on a
> later OS than the OS you're currently running; but that doesn't make
> sense if you're running 10.13.
>
> You _might_ be able to suppress the warning using
>
> -largs -Wl,-macosx_version_min,10.11
>
> From 'man ld':
>
> -macosx_version_min version
> This is set to indicate the oldest Mac OS X version that that the
> output is to be used on. Specifying a later version enables the
> linker to assumes features of that OS in the out- put file. The
> format of version is a Mac OS X version number such as 10.4 or
> 10.5

GNAT GPL 2107 and GNAT 8.1.0 work well for me, so it's not a great problem.
I just don't like to have badly-understood phenomena on my system. 8-)

-- 
Bill Findlay

Re: GNAT Community Edition 2018

[Dmitry A. Kazakov]

On 2018-06-08 19:58, Simon Wright wrote:
> .. is available. The macOS arm-elf cross compiler is there too! (phew)

Great news! 64-bit Windows and 64-bit Gtk.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de

Re: GNAT Community Edition 2018

[eduardsapotski]

> by compiling it yourself. (if it did not change in this dist)
> enable it by setting SOCKET = openssl in makefile.conf

In assemblies AdaCore 2017/2018 not all source files AWS. Makefile empty. 
I try buld AWS of GitHub: https://github.com/AdaCore/aws

root@pc:/home/ds/downloads/aws-master# make setup
gprbuild: "xoscons" up to date
Setup OS specific definitions
Can not generate system tags. The test are disabled
make[1]: *** No rule to make target 'setup'.  Stop.
Makefile:162: recipe for target 'templates_parser_setup' failed
make: *** [templates_parser_setup] Error 2

root@pc:/home/ds/downloads/aws-master# make build
tools.gpr:19:06: unknown project file: "../.build/projects/aws_asis"
zlib.gpr:19:06: unknown project file: "../../.build/projects/aws_config"
zlib.gpr:19:06: imported by "/home/ds/downloads/aws-master/include/zlib/zlib.gpr"
zlib.gpr:19:06: imported by "/home/ds/downloads/aws-master/aws.gpr"
zlib.gpr:19:06: imported by "/home/ds/downloads/aws-master/tools/tools.gpr"
zlib.gpr:41:10: warning: no when others for this case construction
zlib.gpr:41:15: unknown package or project "Aws_Config"
zlib.gpr:41:15: variable "zlib_exists" is not a single string
gprbuild: "tools/tools.gpr" processing failed
Makefile:187: recipe for target 'build-native' failed
make: *** [build-native] Error 4

OS: Ubuntu 18 CentOS 7

Latest version AWS which is installed without problems - 2016.

Re: GNAT Community Edition 2018

[Björn Lundin]

On 2018-06-09 06:29, eduardsapotski@gmail.com wrote:
> In assemblies AdaCore 2017/2018 not all source files AWS. Makefile empty. 
> I try buld AWS of GitHub: https://github.com/AdaCore/aws


open a ticket at
https://github.com/AdaCore/aws/issues/


-- 
--
Björn

Re: GNAT Community Edition 2018

[M. Enzmann]

Am Freitag, 8. Juni 2018 19:58:06 UTC+2 schrieb Simon Wright:
> .. is available. The macOS arm-elf cross compiler is there too! (phew)

Is anybody here experiencing issues while installing the native compiler on High Sierra? 

Re: GNAT Community Edition 2018

[Simon Wright]

"M. Enzmann" <enzmann.m@googlemail.com> writes:

> Am Freitag, 8. Juni 2018 19:58:06 UTC+2 schrieb Simon Wright:
>> .. is available. The macOS arm-elf cross compiler is there too! (phew)
>
> Is anybody here experiencing issues while installing the native
> compiler on High Sierra?

Yes. I reported this to AdaCore:

   I have a Macbook Pro (Retina, 13 inch, early 2015) running 10.13.4,
   with 2.9GHz processor.

   Installing gnat-community-2018-20180523-x86_64-darwin-bin.dmg locked
   up twice while installing RTS files (not at the same place. maybe
   because there are lots of small files? maybe because I have Time
   Machine?)

   Anyway, the workround was to install to an external HDD and copy from
   there to the SSD.

They replied that they hadn't seen this when installing on a Mac with
Time Machine & are puzzled (my interpretation!)

Additional info I should have provided: 512 GB SSD.

Re: GNAT Community Edition 2018

[Bill Findlay]

On 10 Jun 2018, Simon Wright wrote (in article<lyr2le6hoy.fsf@pushface.org>):

> "M. Enzmann"<enzmann.m@googlemail.com>  writes:
>
> > Am Freitag, 8. Juni 2018 19:58:06 UTC+2 schrieb Simon Wright:
> > > .. is available. The macOS arm-elf cross compiler is there too! (phew)
> >
> > Is anybody here experiencing issues while installing the native compiler on High Sierra?
>
> Yes. I reported this to AdaCore:
>
> I have a Macbook Pro (Retina, 13 inch, early 2015) running 10.13.4, with 2.9GHz processor.
>
> Installing gnat-community-2018-20180523-x86_64-darwin-bin.dmg locked
> up twice while installing RTS files (not at the same place. maybe
> because there are lots of small files? maybe because I have Time Machine?)

My installation went smoothly, as far as I could see, but ...

Do you think something similar might have caused the messages I am getting:

> gnatbind -aI../Source/e -aI../Source/shared -aO../MacOSX -aI../MacOSX -static -Sin -x /Users/wf/mekhos/MacOSX/e.ali
>
> gnatlink /Users/wf/mekhos/MacOSX/e.ali -funwind-tables -fdata-sections -ffunction-sections -mtune=native -fno-stack-check -fomit-frame-pointer -O3 
-Wl,-dead_strip -Wl,-dead_strip
>
> ld: warning: object file (/Users/wf/opt/gnat-2018/lib/gcc/x86_64-apple-darwin16.7.0/7.3.1/adalib/libgnat.a(errno.o)) was built for newer OSX version (10.12) 
than being linked (10.11)
>
> ld: warning: object file (/Users/wf/opt/gnat-2018/lib/gcc/x86_64-apple-darwin16.7.0/7.3.1/adalib/libgnat.a(init.o)) was built for newer OSX version (10.12) 
than being linked (10.11)
> ...
> ld: warning: object file (/Users/wf/opt/gnat-2018/lib/gcc/x86_64-apple-darwin16.7.0/7.3.1/adalib/libgnat.a(s-valuns.o)) was built for newer OSX version 
(10.12) than being linked (10.11)

> Anyway, the workround was to install to an external HDD and copy from there to the SSD.

I'll try that.
> They replied that they hadn't seen this when installing on a Mac with Time Machine &  are puzzled (my interpretation!)
> Additional info I should have provided: 512 GB SSD.

I have a 256GB SSD with an APFS filesystem on it.
TM runs on a Lacie HD, but I really can't see how that would have a bearing 
on it.
Might it be a Gatekeeper issue, since previous installs were done at the 
command line with sudo?

-- 
Bill Findlay

Re: GNAT Community Edition 2018

[Simon Wright]

Bill Findlay <findlaybill@blueyonder.co.uk> writes:

> On 10 Jun 2018, Simon Wright wrote (in article<lyr2le6hoy.fsf@pushface.org>):
>
>> "M. Enzmann"<enzmann.m@googlemail.com>  writes:
>>
>> > Am Freitag, 8. Juni 2018 19:58:06 UTC+2 schrieb Simon Wright:
>> > > .. is available. The macOS arm-elf cross compiler is there too!
>> > > (phew)
>> >
>> > Is anybody here experiencing issues while installing the native
>> > compiler on High Sierra?
>>
>> Yes. I reported this to AdaCore:
>>
>> I have a Macbook Pro (Retina, 13 inch, early 2015) running 10.13.4,
>> with 2.9GHz processor.
>>
>> Installing gnat-community-2018-20180523-x86_64-darwin-bin.dmg locked
>> up twice while installing RTS files (not at the same place. maybe
>> because there are lots of small files? maybe because I have Time
>> Machine?)
>
> My installation went smoothly, as far as I could see, but ...

For me, it hung while copying RTS files over.

> Do you think something similar might have caused the messages I am
> getting:

Would be surprised .. sorry

Re: GNAT Community Edition 2018

[Bill Findlay]

On 10 Jun 2018, Simon Wright wrote
(in article <lyefhe685u.fsf@pushface.org>):

> Bill Findlay<findlaybill@blueyonder.co.uk>  writes:
>
> > On 10 Jun 2018, Simon Wright wrote (in
> > article<lyr2le6hoy.fsf@pushface.org>):
> >
> > > "M. Enzmann"<enzmann.m@googlemail.com>  writes:
> > >
> > > > Am Freitag, 8. Juni 2018 19:58:06 UTC+2 schrieb Simon Wright:
> > > > > .. is available. The macOS arm-elf cross compiler is there too!
> > > > > (phew)
> > > >
> > > > Is anybody here experiencing issues while installing the native
> > > > compiler on High Sierra?
> > >
> > > Yes. I reported this to AdaCore:
> > >
> > > I have a Macbook Pro (Retina, 13 inch, early 2015) running 10.13.4,
> > > with 2.9GHz processor.
> > >
> > > Installing gnat-community-2018-20180523-x86_64-darwin-bin.dmg locked
> > > up twice while installing RTS files (not at the same place. maybe
> > > because there are lots of small files? maybe because I have Time
> > > Machine?)
> >
> > My installation went smoothly, as far as I could see, but ...
>
> For me, it hung while copying RTS files over.
>
> > Do you think something similar might have caused the messages I am
> > getting:
>
> Would be surprised .. sorry

I have now tried on an external APFS SSD, and on a HD I also use for TM;
neither solves the problem.

-- 
Bill Findlay

Re: GNAT Community Edition 2018

[Simon Wright]

Bill Findlay <findlaybill@blueyonder.co.uk> writes:

> I have now tried on an external APFS SSD, and on a HD I also use for TM;
> neither solves the problem.

We're now wondering whether the hang is caused by installing with the
'detailed view' option selected.

I've now found a way of provoking the behaviour you see:

$ gnatmake -f raiser -largs -Wl,-macosx_version_min,10.11
gcc -c raiser.adb
gnatbind -x raiser.ali
gnatlink raiser.ali -Wl,-macosx_version_min,10.11
ld: warning: object file (b~raiser.o) was built for newer OSX version (10.13) than being linked (10.11)
ld: warning: object file (./raiser.o) was built for newer OSX version (10.13) than being linked (10.11)
ld: warning: object file (/opt/gnat-gpl-2018/lib/gcc/x86_64-apple-darwin16.7.0/7.3.1/adalib/libgnat.a(init.o)) was built for newer OSX version (10.12) than being linked (10.11)
[...]

So, I wonder whether you've got some linker option hidden in a project
file or something?

Re: GNAT Community Edition 2018

[Bill Findlay]

On 10 Jun 2018, Simon Wright wrote (in article<lya7s2616h.fsf@pushface.org>):

> Bill Findlay<findlaybill@blueyonder.co.uk>  writes:
>
> > I have now tried on an external APFS SSD, and on a HD I also use for TM;
> > neither solves the problem.
>
> We're now wondering whether the hang is caused by installing with the
> 'detailed view' option selected.
>
> I've now found a way of provoking the behaviour you see:
>
> $ gnatmake -f raiser -largs -Wl,-macosx_version_min,10.11
> gcc -c raiser.adb
> gnatbind -x raiser.ali
> gnatlink raiser.ali -Wl,-macosx_version_min,10.11
> ld: warning: object file (b~raiser.o) was built for newer OSX version (10.13)
> than being linked (10.11)
> ld: warning: object file (./raiser.o) was built for newer OSX version (10.13)
> than being linked (10.11)
> ld: warning: object file
> (/opt/gnat-gpl-2018/lib/gcc/x86_64-apple-darwin16.7.0/7.3.1/adalib/libgnat.a(i
> nit.o)) was built for newer OSX version (10.12) than being linked (10.11)
> [...]
>
> So, I wonder whether you've got some linker option hidden in a project
> file or something?

Thanks, Simon.
I am old-school: I use only makefiles and gnatmake.
I have re-confirmed that GNAT GPL 2017 and FSF GNAT 8.0.1 both work without 
complaint.

I have this setting: "LINK_OPTIONS = -bargs -static -Sin -largs 
-Wl,-dead_strip -Wl,-dead_strip".

I have tried removing each component of those flags separately; makes no 
difference.

I have tried adding each of -Wl,-macosx_version_min,10.1[123]; makes no 
difference.

Also I do not get messages analogous to your "object file (b~raiser.o) was 
built for newer OSX version (10.13)
than being linked (10.11)" about my own .o files.

What is baffling to me is that it seems to think it is running on macOS 10.11 
even thoughI am running 13.5,
and my XCode and Command Line Tools are all up to date. At least, that is how 
I interpret:
"ld: warning: object file 
(/Users/wf/opt/gnat-2018/lib/gcc/x86_64-apple-
darwin16.7.0/7.3.1/adalib/libgnat.a(s-valuns.o))
was built for newer OSX version (10.12) than being linked (10.11))".

I am also surprised that AdaCoreapparently built a new GNAT on 10.12, when 
10.13 is about to be superseded.

All in all, rather a disappointing performance from AdaCore this time.

-- 
Bill Findlay

Re: GNAT Community Edition 2018

[Simon Wright]

Bill Findlay <findlaybill@blueyonder.co.uk> writes:

Baffling, I agree.

> I have this setting: "LINK_OPTIONS = -bargs -static -Sin -largs 
> -Wl,-dead_strip -Wl,-dead_strip".

You might get some insight from adding "-Wl,-v" to -largs, to see what
options ld actually got.

Re: GNAT Community Edition 2018

[Bill Findlay]

On 11 Jun 2018, Simon Wright wrote
(in article <lywov54der.fsf@pushface.org>):

> Bill Findlay<findlaybill@blueyonder.co.uk>  writes:
>
> Baffling, I agree.
>
> > I have this setting: "LINK_OPTIONS = -bargs -static -Sin -largs
> > -Wl,-dead_strip -Wl,-dead_strip".
>
> You might get some insight from adding "-Wl,-v" to -largs, to see what options ld actually got.

With GPL 2017 the linker output:

> gnatlink /Users/wf/mekhos/MacOSX/e.ali -funwind-tables -fdata-sections
> -ffunction-sections -fstack-check -fstack-usage -Wl,-dead_strip
> -Wl,-dead_strip -Wl,-v
> collect2 version 6.3.1 20170510 (for GNAT GPL 2017 20170515)
> /usr/bin/ld -dynamic -arch x86_64 -macosx_version_min 10.11 -weak_reference_mismatches non-weak -o e
> -L/Users/wf/mekhos/MacOSX/
> -L../MacOSX/ -L/opt/gnat-2017/lib/gcc/x86_64-apple-darwin14.5.0/6.3.1/adalib/
> -L/opt/gnat-2017/bin/../lib/gcc/x86_64-apple-darwin14.5.0/6.3.1
> -L/opt/gnat-2017/bin/../lib/gcc
> -L/opt/gnat-2017/bin/../lib/gcc/x86_64-apple-darwin14.5.0/6.3.1/../../..
> b~e.o /Users/wf/mekhos/MacOSX/m.o /Users/wf/mekhos/MacOSX/m-opcodes.o
> ...
> /Users/wf/mekhos/MacOSX/execute.o /Users/wf/mekhos/MacOSX/e.o -dead_strip -dead_strip -v
> /opt/gnat-2017/lib/gcc/x86_64-apple-darwin14.5.0/6.3.1/adalib/libgnat.a -no_compact_unwind -lSystem -lSystem
> @(#)PROGRAM:ld PROJECT:ld64-408.1.1
> BUILD 05:18:43 May 25 2018
> configured to support archs: armv6 armv7 armv7s arm64 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em

And with GNAT CE gave:

> gnatlink /Users/wf/mekhos/MacOSX/e.ali -funwind-tables -fdata-sections
> -ffunction-sections -fstack-check -fstack-usage -Wl,-dead_strip
> -Wl,-dead_strip -Wl,-v
> collect2 version 7.3.1 20180524 (for GNAT Community 2018 20180523)
> /usr/bin/ld -dynamic -arch x86_64 -macosx_version_min 10.11 -weak_reference_mismatches non-weak -o e
> -L/Users/wf/mekhos/MacOSX/
> -L../MacOSX/ -L/opt/gnat-2018/lib/gcc/x86_64-apple-darwin16.7.0/7.3.1/adalib/
> -L/opt/gnat-2018/bin/../lib/gcc/x86_64-apple-darwin16.7.0/7.3.1
> -L/opt/gnat-2018/bin/../lib/gcc
> -L/opt/gnat-2018/bin/../lib/gcc/x86_64-apple-darwin16.7.0/7.3.1/../../..
> b~e.o /Users/wf/mekhos/MacOSX/m.o /Users/wf/mekhos/MacOSX/m-opcodes.o
> ...
> /Users/wf/mekhos/MacOSX/execute.o /Users/wf/mekhos/MacOSX/e.o -dead_strip -dead_strip -v
> /opt/gnat-2018/lib/gcc/x86_64-apple-darwin16.7.0/7.3.1/adalib/libgnat.a -no_compact_unwind -lSystem -lSystem
> @(#)PROGRAM:ld PROJECT:ld64-408.1.1
> BUILD 05:18:43 May 25 2018
> configured to support archs: armv6 armv7 armv7s arm64 i386 x86_64 x86_64h armv6m armv7k armv7m armv7em

I see that both are using:

> -macosx_version_min 10.11

without my asking.

Apart from that I don't see anything surprising.

-- 
Bill Findlay

Re: GNAT Community Edition 2018

[Simon Wright]

Bill Findlay <findlaybill@blueyonder.co.uk> writes:

> I see that both are using:
>
>> -macosx_version_min 10.11
>
> without my asking.

Do you by any chance have the env var MACOSX_DEPLOYMENT_TARGET set?

Re: GNAT Community Edition 2018

[Bill Findlay]

On 11 Jun 2018, Simon Wright wrote
(in article <lysh5tl0l5.fsf@pushface.org>):

> Bill Findlay<findlaybill@blueyonder.co.uk>  writes:
>
> > I see that both are using:
> >
> > > -macosx_version_min 10.11
> >
> > without my asking.
>
> Do you by any chance have the env var MACOSX_DEPLOYMENT_TARGET set?

Bingo!

Who ordered that? 8-)

Thanks very much Simon, and for FSF GNAT as well.

Do you happen to know if there is an up-to-date compiler for Ada 2012 that
generates code for RPi Linux?

-- 
Bill Findlay

Re: GNAT Community Edition 2018

[Simon Wright]

Bill Findlay <findlaybill@blueyonder.co.uk> writes:

> On 11 Jun 2018, Simon Wright wrote
> (in article <lysh5tl0l5.fsf@pushface.org>):
>
>> Bill Findlay<findlaybill@blueyonder.co.uk>  writes:
>>
>> > I see that both are using:
>> >
>> > > -macosx_version_min 10.11
>> >
>> > without my asking.
>>
>> Do you by any chance have the env var MACOSX_DEPLOYMENT_TARGET set?
>
> Bingo!

Glad that ws it!

> Thanks very much Simon, and for FSF GNAT as well.

Glad to help.

> Do you happen to know if there is an up-to-date compiler for Ada 2012
> that generates code for RPi Linux?

Debian Stretch has GCC 6.3, same (roughly) as CE 2017.

Re: GNAT Community Edition 2018

[Simon Wright]

Simon Wright <simon@pushface.org> writes:

> Bill Findlay <findlaybill@blueyonder.co.uk> writes:
>
>> On 11 Jun 2018, Simon Wright wrote
>> (in article <lysh5tl0l5.fsf@pushface.org>):
>>
>>> Bill Findlay<findlaybill@blueyonder.co.uk>  writes:
>>>
>>> > I see that both are using:
>>> >
>>> > > -macosx_version_min 10.11
>>> >
>>> > without my asking.
>>>
>>> Do you by any chance have the env var MACOSX_DEPLOYMENT_TARGET set?
>>
>> Bingo!
>
> Glad that ws it!
>
>> Thanks very much Simon, and for FSF GNAT as well.
>
> Glad to help.
>
>> Do you happen to know if there is an up-to-date compiler for Ada 2012
>> that generates code for RPi Linux?
>
> Debian Stretch has GCC 6.3, same (roughly) as CE 2017.

I meant to add, current Raspbian is Stretch

Re: GNAT Community Edition 2018

[Bill Findlay]

On 11 Jun 2018, Simon Wright wrote
(in article <lyin6pksec.fsf@pushface.org>):

> Simon Wright <simon@pushface.org> writes:
>
> > Bill Findlay<findlaybill@blueyonder.co.uk>  writes:
> >
> > > On 11 Jun 2018, Simon Wright wrote
> > > (in article <lysh5tl0l5.fsf@pushface.org>):
> > >
> > > > Bill Findlay<findlaybill@blueyonder.co.uk>  writes:
> > > >
> > > > > I see that both are using:
> > > > >
> > > > > > -macosx_version_min 10.11
> > > > >
> > > > > without my asking.
> > > >
> > > > Do you by any chance have the env var MACOSX_DEPLOYMENT_TARGET set?
> > >
> > > Bingo!
> >
> > Glad that ws it!
> >
> > > Thanks very much Simon, and for FSF GNAT as well.
> >
> > Glad to help.
> >
> > > Do you happen to know if there is an up-to-date compiler for Ada 2012
> > > that generates code for RPi Linux?
> >
> > Debian Stretch has GCC 6.3, same (roughly) as CE 2017.
>
> I meant to add, current Raspbian is Stretch

You anticipated my next question. 8-)

-- 
Bill Findlay

Re: GNAT Community Edition 2018

[Simon Wright]

Simon Wright <simon@pushface.org> writes:

> Debian Stretch has GCC 6.3, same (roughly) as CE 2017.

Umm.

CE2017 is bsed on GCC 6.3, but actually in terms of features GCC 7 would
be closer. But 6.3's not that bad!

Re: GNAT Community Edition 2018

[M. Enzmann]

Yes, that‘s similar to what I got. The install process locked, whenever I tried to install into /usr/local or /opt. It wenn smoothly however, when I installed into my home directory.

No issues when compiling native or for ARM now.

Re: GNAT Community Edition 2018

[Alejandro R. Mosteo]

On 08/06/2018 19:58, Simon Wright wrote:
> .. is available. The macOS arm-elf cross compiler is there too! (phew)
> 

I'm seeing several projects fail because the new release no longer 
recognizes -gnat05/-gnat2005 switches.

Curiously, gnatmake -h says to accept -gnat2012 and says it's the default 
mode, but lists no way to select another mode.

Not sure what to think about it.

Re: GNAT Community Edition 2018

[Dan'l Miller]

> I'm seeing several projects fail because the
> new release no longer recognizes
> -gnat05/gnat2005 switches. 
>
> Curiously, gnatmake -h says to accept
> -gnat2012 and says it's the default
> mode, but lists no way to select another mode.

I thought as a general policy AdaCore demanded that all prior eras of Ada are a paid-support topic for GNAT Pro.  Along with 83 and 95, 2005 would now be a prior pre-2012 era.  Convert to the Ada2012 era or pay Pro’s $$$$$ (or £££££ or €€€€£ or ¥¥¥¥¥ as the case may be).

Re: GNAT Community Edition 2018

[Alejandro R. Mosteo]

On 10/06/2018 22:11, Dan'l Miller wrote:
>> I'm seeing several projects fail because the
>> new release no longer recognizes
>> -gnat05/gnat2005 switches.
>>
>> Curiously, gnatmake -h says to accept
>> -gnat2012 and says it's the default
>> mode, but lists no way to select another mode.
> 
> I thought as a general policy AdaCore demanded that all prior eras of Ada are a paid-support topic for GNAT Pro.  Along with 83 and 95, 2005 would now be a prior pre-2012 era.  Convert to the Ada2012 era or pay Pro’s $$$$$ (or £££££ or €€€€£ or ¥¥¥¥¥ as the case may be).
> 

No, in my experience you could always select the compiler mode.

I'm seeing the error raised by some gnat1 compiler component; gnatmake 
does not complain directly, and the old switches are in the documentation 
that comes in the package.

Re: GNAT Community Edition 2018

[Dan'l Miller]

> On 10/06/2018 22:11, Dan'l Miller wrote: 
> >> I'm seeing several projects fail because the 
> >> new release no longer recognizes 
> >> -gnat05/gnat2005 switches. 
> >> 
> >> Curiously, gnatmake -h says to accept 
> >> -gnat2012 and says it's the default 
> >> mode, but lists no way to select another mode. 
> > 
> > I thought as a general policy AdaCore demanded that all prior eras of Ada are a paid-support topic for GNAT Pro.  Along with 83 and 95, 2005 would now be a prior pre-2012 era.  
> > 
> No, in my experience you could always select
> the compiler mode. 

I reiterate:
The AdaCore version comparison is quite explicitly clear on this.  GNAT GPL Community Edition (a.k.a. “public) lists Ada2005 for paying customers only under the Languages section at:

https://www.adacore.com/gnatpro/comparison

Re: GNAT Community Edition 2018

[Alejandro R. Mosteo]

On 11/06/2018 00:39, Dan'l Miller wrote:
>> On 10/06/2018 22:11, Dan'l Miller wrote:
>>>> I'm seeing several projects fail because the
>>>> new release no longer recognizes
>>>> -gnat05/gnat2005 switches.
>>>>
>>>> Curiously, gnatmake -h says to accept
>>>> -gnat2012 and says it's the default
>>>> mode, but lists no way to select another mode.
>>>
>>> I thought as a general policy AdaCore demanded that all prior eras of Ada are a paid-support topic for GNAT Pro.  Along with 83 and 95, 2005 would now be a prior pre-2012 era.
>>>
>> No, in my experience you could always select
>> the compiler mode.
> 
> I reiterate:
> The AdaCore version comparison is quite explicitly clear on this.  GNAT GPL Community Edition (a.k.a. “public) lists Ada2005 for paying customers only under the Languages section at:
> 
> https://www.adacore.com/gnatpro/comparison

You're right. Then this is part of the GPL -> Community rebranding.

Re: GNAT Community Edition 2018

[Simon Wright]

"Alejandro R. Mosteo" <alejandro@mosteo.com> writes:

> On 11/06/2018 00:39, Dan'l Miller wrote:
>>> On 10/06/2018 22:11, Dan'l Miller wrote:
>>>>> I'm seeing several projects fail because the
>>>>> new release no longer recognizes
>>>>> -gnat05/gnat2005 switches.
>>>>>
>>>>> Curiously, gnatmake -h says to accept
>>>>> -gnat2012 and says it's the default
>>>>> mode, but lists no way to select another mode.
>>>>
>>>> I thought as a general policy AdaCore demanded that all prior eras
>>>> of Ada are a paid-support topic for GNAT Pro.  Along with 83 and
>>>> 95, 2005 would now be a prior pre-2012 era.
>>>>
>>> No, in my experience you could always select
>>> the compiler mode.
>>
>> I reiterate:
>> The AdaCore version comparison is quite explicitly clear on this.
>> GNAT GPL Community Edition (a.k.a. “public) lists Ada2005 for paying
>> customers only under the Languages section at:
>>
>> https://www.adacore.com/gnatpro/comparison
>
> You're right. Then this is part of the GPL -> Community rebranding.

-gnat83, -gnat95, -gnat2005 still OK with FSF GCC 8.

Re: GNAT Community Edition 2018

[Alejandro R. Mosteo]

On 11/06/2018 10:28, Simon Wright wrote:
> "Alejandro R. Mosteo" <alejandro@mosteo.com> writes:
> 
>> On 11/06/2018 00:39, Dan'l Miller wrote:
>>>> On 10/06/2018 22:11, Dan'l Miller wrote:
>>>>>> I'm seeing several projects fail because the
>>>>>> new release no longer recognizes
>>>>>> -gnat05/gnat2005 switches.
>>>>>>
>>>>>> Curiously, gnatmake -h says to accept
>>>>>> -gnat2012 and says it's the default
>>>>>> mode, but lists no way to select another mode.
>>>>>
>>>>> I thought as a general policy AdaCore demanded that all prior eras
>>>>> of Ada are a paid-support topic for GNAT Pro.  Along with 83 and
>>>>> 95, 2005 would now be a prior pre-2012 era.
>>>>>
>>>> No, in my experience you could always select
>>>> the compiler mode.
>>>
>>> I reiterate:
>>> The AdaCore version comparison is quite explicitly clear on this.
>>> GNAT GPL Community Edition (a.k.a. “public) lists Ada2005 for paying
>>> customers only under the Languages section at:
>>>
>>> https://www.adacore.com/gnatpro/comparison
>>
>> You're right. Then this is part of the GPL -> Community rebranding.
> 
> -gnat83, -gnat95, -gnat2005 still OK with FSF GCC 8.

Where is GCC 8 already available? Debian testing?

Re: GNAT Community Edition 2018

[Simon Wright]

"Alejandro R. Mosteo" <alejandro@mosteo.com> writes:

> On 11/06/2018 10:28, Simon Wright wrote:

>> -gnat83, -gnat95, -gnat2005 still OK with FSF GCC 8.
>
> Where is GCC 8 already available? Debian testing?

On Mac definitely[1]. Is in buster & sid[2].

[1]https://sourceforge.net/projects/gnuada/files/GNAT_GCC%20Mac%20OS%20X/8.1.0/native-2017/
[2] https://packages.debian.org/search?keywords=gnat-8

Re: GNAT Community Edition 2018

[Alejandro R. Mosteo]

On 11/06/2018 12:38, Simon Wright wrote:
> "Alejandro R. Mosteo" <alejandro@mosteo.com> writes:
> 
>> On 11/06/2018 10:28, Simon Wright wrote:
> 
>>> -gnat83, -gnat95, -gnat2005 still OK with FSF GCC 8.
>>
>> Where is GCC 8 already available? Debian testing?
> 
> On Mac definitely[1]. Is in buster & sid[2].
> 
> [1]https://sourceforge.net/projects/gnuada/files/GNAT_GCC%20Mac%20OS%20X/8.1.0/native-2017/
> [2] https://packages.debian.org/search?keywords=gnat-8

OK, thanks.

Re: GNAT Community Edition 2018

[Dmitry A. Kazakov]

On 2018-06-11 11:32, Alejandro R. Mosteo wrote:

> Where is GCC 8 already available? Debian testing?

Yes. Debian (buster), Ubuntu, Fedora, all have GNAT 8, works just fine.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de

Re: GNAT Community Edition 2018

[fabien.chouteau]

On Monday, June 11, 2018 at 12:39:30 AM UTC+2, Dan'l Miller wrote:
> > On 10/06/2018 22:11, Dan'l Miller wrote: 
> > >> I'm seeing several projects fail because the 
> > >> new release no longer recognizes 
> > >> -gnat05/gnat2005 switches. 
> > >> 
> > >> Curiously, gnatmake -h says to accept 
> > >> -gnat2012 and says it's the default 
> > >> mode, but lists no way to select another mode. 
> > > 
> > > I thought as a general policy AdaCore demanded that all prior eras of Ada are a paid-support topic for GNAT Pro.  Along with 83 and 95, 2005 would now be a prior pre-2012 era.  
> > > 
> > No, in my experience you could always select
> > the compiler mode. 
> 
> I reiterate:
> The AdaCore version comparison is quite explicitly clear on this.  GNAT GPL Community Edition (a.k.a. “public) lists Ada2005 for paying customers only under the Languages section at:
> 
> https://www.adacore.com/gnatpro/comparison

It is indeed a choice on our part to remove pure Ada05/95/83 support from the community release of the compiler.

That being said, 99% of Ada2005 project will work just fine in Ada2012 modes. So you can either don't specify any language version switches and the compiler will be in Ada2012 mode by default, or you can explicitly use the Ada2012 switch.

Re: GNAT Community Edition 2018

[Vincent]

Le vendredi 8 juin 2018 19:58:06 UTC+2, Simon Wright a écrit :
> .. is available. The macOS arm-elf cross compiler is there too! (phew)

Hello Simon,

Is it possible to have the POSIX library, Florist running for this version ?
Where can I download it ? I tried to compile Florist for GPL 2017 but it's not working with FSF Gnat..

Regards,

Vincent

Re: GNAT Community Edition 2018

[Simon Wright]

Vincent <vincent.diemunsch@gmail.com> writes:

> Le vendredi 8 juin 2018 19:58:06 UTC+2, Simon Wright a écrit :
>> .. is available. The macOS arm-elf cross compiler is there too! (phew)
>
> Is it possible to have the POSIX library, Florist running for this
> version ?  Where can I download it ? I tried to compile Florist for
> GPL 2017 but it's not working with FSF Gnat..

You seem to have got an answer on the GNAT-OSX list!

Re: GNAT Community Edition 2018

[Vincent]

Le samedi 14 juillet 2018 21:34:06 UTC+2, Simon Wright a écrit :
> Vincent <vincent..> writes:
> 
> > Le vendredi 8 juin 2018 19:58:06 UTC+2, Simon Wright a écrit :
> >> .. is available. The macOS arm-elf cross compiler is there too! (phew)
> >
> > Is it possible to have the POSIX library, Florist running for this
> > version ?  Where can I download it ? I tried to compile Florist for
> > GPL 2017 but it's not working with FSF Gnat..
> 
> You seem to have got an answer on the GNAT-OSX list!

Yes. Thank you Simon.