Opened 13 months ago

Last modified 12 months ago

#68544 assigned defect

gcc10-bootstrap forces unversal builds on Leopard, not respecting even explicit -universal

Reported by: barracuda156 Owned by: catap (Kirill A. Korinsky)
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: leopard, powerpc Cc:
Port: gcc10-bootstrap

Description

Something is wrong with gcc10-bootstrap: on 10.5.8 I cannot force a non-universal build of libgcc13 now. I disabled universal everywhere, yet it forces itself somehow. To be clear, gcc10-bootstrap itself is built as +universal, and I do not want to rebuild it for a single arch. I believe, this should still allow non-universal builds.

Attachments (1)

gcc13_why_universal.txt (203.0 KB) - added by barracuda156 13 months ago.
So I set universal_archs to nothing, build_arch to ppc64 and called sudo port -v install libgcc13 libgcc gcc13 -universal, and still got universal forced

Download all attachments as: .zip

Change History (6)

Changed 13 months ago by barracuda156

Attachment: gcc13_why_universal.txt added

So I set universal_archs to nothing, build_arch to ppc64 and called sudo port -v install libgcc13 libgcc gcc13 -universal, and still got universal forced

comment:1 Changed 13 months ago by barracuda156

Initially I tried without extra steps, just unsetting universal variant from defaults, then added extra measures sequentially, in any case I got the same outcome of forced universal build.

comment:2 Changed 13 months ago by ryandesign (Ryan Carsten Schmidt)

The fact that the port defaults to +universal is clearly deliberate. It's in the Portfile code and it has been ever since the port was added last year. I don't know why, though.

That you can't disable it with -universal is more surprising since I don't see the lines in the Portfile that I have used when I wanted to do that.

comment:3 in reply to:  2 Changed 13 months ago by barracuda156

Replying to ryandesign:

The fact that the port defaults to +universal is clearly deliberate. It's in the Portfile code and it has been ever since the port was added last year. I don't know why, though.

That you can't disable it with -universal is more surprising since I don't see the lines in the Portfile that I have used when I wanted to do that.

I believe gcc10-bootstrap itself builds with -universal, at least it surely did on 10.6 (both native and in Rosetta). The issue I faced on 10.5 was that when gcc10-bootstrap has been built as universal, it seems to force universal builds on libgcc13, which a) is likely broken or at least never tested by anyone, AFAIK, and b) may not be needed/wanted by a user.

It was unexpected issue, and I got no explanation at the moment for it.

comment:4 Changed 13 months ago by barracuda156

As Kirill suggested, this fixes the issue: configure.compiler.add_deps no. I have rebased the PR. It is ready now: https://github.com/macports/macports-ports/pull/16843

comment:5 Changed 12 months ago by catap (Kirill A. Korinsky)

barracuda156, shall it be closed when?

Note: See TracTickets for help on using tickets.