Building RTEMS 6 toolchain on a Mac

[Karel Gardas]

On 4/27/22 08:48, Sebastian Huber wrote:
> On 27.04.22 08:45, Karel Gardas wrote:
>> On 4/27/22 06:46, Sebastian Huber wrote:
>>> On 26.04.22 22:57, Karel Gardas wrote:
>>>> On 4/25/22 10:10, Sebastian Huber wrote:
>>>>> Hello Heinz,
>>>>>
>>>>> you are probably one of the first persons building GCC 12 on this 
>>>>> platform. I checked in a change which could fix the problem.
>>>>>
>>>>
>>>> Not sure if this is related, but after this hacking I'm no longer 
>>>> able to build neither 6/rtems-arm not 6/rtems-x86_64.
>>>
>>> I changed the mpfr version from 3.1.4 to 4.1.0. This is the latest 
>>> mpfr release and used by the GCC contrib/download_prerequisites 
>>> script currently. If this version doesn't build on macOS, then it 
>>> would be good to submit a bug report to mpfr.
>>
>> The problem is that I'm perfectly able to build 4.1.0 including 
>> testsuite including its run on catalina. So the problem is somewhere 
>> else and rsb logging was just misleading...
> 
> The RTEMS 7 RSB configuration still uses mpfr-4.1.0 (and GCC 12), maybe 
> you can check it here.

I'm a little bit confused since HEAD works fine with 7/rtems-arm and 
7/rtems-x86_64 on catalina. So I reverted patches up to:

me at mes-MacBook-Pro rtems % git log -1
commit 70f302e08c9053637f5eff7dfb52d3442aaf76cb (HEAD)
Author: Chris Johns <chrisj at rtems.org>
Date:   Tue Apr 26 10:13:41 2022 +1000

     gdb: Split python's version into major/minor and check for embed option

     Closes #4631


and now, 6/rtems-x86_64 correctly fails as I reported, but 
7/rtems-x86_64 builds fine again.

Diffing shows quite major differences between rtems-default.bset files 
for 6/ and 7/ so I guess that's the reason...

Karel