[libgcc8] compile failure on i386 on 10.6 Snow

[Ken Cunningham]

> On 27/08/2019 1:31 pm, Ken Cunningham wrote:
> > that is a 32 bit error that is usually suppressed by passing "-read_only_relocs suppress"' to the linker, IIRC.
> > 
> > Why are you seeing it, though, I wonder?
> > 
> > I don't think anyone has likely tried to build libgcc8 32bit on 10.6.8 with clang-8.0...
> 
> My guess is the use of clang 8.0 is something new, and probably related 
> to the recent changes to support libc++ etc. in base 2.6.0...
He's still on 2.5.4 (like my 10.6.8 system).  But (as he should) he's using LibCxxOnOlderSystems. He has chosen to force clang-8.0 (which may well be too new a compiler to force for 10.6.8 for general use).

> 
> > Why don't you try it with clang-3.9....
> 
> Certainly interesting to know if that (still) works, but ultimately this 
> compiler will be removed (it already was, but temporarily put back 
> pending the new base release). So longer term the issues with the new 
> clang needs to be resolved.
> 
> Chris

As is often the case, I have no issues with any of these gcc versions (and also have gcc9 on 10.6.8 for my use, possibly to update on MacPorts when I get time).

$ port -v installed | grep gcc
  gcc5 @5.5.0_5 (active) platform='darwin 10' archs='x86_64' date='2019-08-18T20:25:21-0700'
  gcc6 @6.5.0_4+universal (active) platform='darwin 10' archs='i386 x86_64' date='2019-05-06T02:26:33-0700'
  gcc7 @7.4.0_3 (active) platform='darwin 10' archs='x86_64' date='2019-05-06T04:18:34-0700'
  gcc8 @8.3.0_4 (active) platform='darwin 10' archs='x86_64' date='2019-05-06T06:44:55-0700'
  gcc9 @9.1.0_1+universal platform='darwin 10' archs='i386 x86_64' date='2019-05-14T08:26:36-0700'
  gcc48 @4.8.5_5+universal (active) platform='darwin 10' archs='i386 x86_64' date='2018-10-18T08:19:43-0700'


$ port -v installed | grep libgcc
  libgcc @2.0_2 (active) platform='darwin 10' archs='noarch' date='2019-05-12T16:45:15-0700'
  libgcc6 @6.5.0_4+universal (active) platform='darwin 10' archs='i386 x86_64' date='2019-05-06T00:26:20-0700'
  libgcc7 @7.4.0_3+universal (active) platform='darwin 10' archs='i386 x86_64' date='2019-05-05T22:28:16-0700'
  libgcc8 @8.3.0_5+universal (active) platform='darwin 10' archs='i386 x86_64' date='2019-05-06T23:35:19-0700'
  libgcc9 @9.1.0_1+universal platform='darwin 10' archs='i386 x86_64' date='2019-05-12T19:18:55-0700'


I build everything with clang-5.0 at present, so I know that gcc8/libgcc8 builds with that. At present, clang-5.0 is a very good balance between being not too strict (and therefore causing all sorts of errors with code that used to be considered OK), but also being quite capable. IMHO, it's the best compiler for 10.6.8 general use right now.

But as he had clang-3.9, and not clang-5.0, I suggested he give that a try. 

If clang-8.0 won't build gcc8 on 10.6.8, it might turn out to be hard to fix. Luckily, we'll always have clang-3.7, and I suspect we may well fall back on that in the future, especially if clang-5.0 is obsoleted.


K
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20190827/cfbdcb4d/attachment.html>