#65036 closed defect (fixed)
python310 @3.10.4_0+lto+universal: Undefined symbols
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | jmroot (Joshua Root) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.7.2 |
| Keywords: | mountainlion | Cc: | eborisch (Eric A. Borisch), MarcusCalhoun-Lopez (Marcus Calhoun-Lopez) |
| Port: | python310 |
Description
Saw this problem when installing python310 @3.10.4_0+lto+universal on the mountainlion buildbot worker. python39 @3.9.12_0+universal built fine.
It doesn't seem like things should need to be universal on the buildbot workers. I certainly haven't requested that. But a great many things are getting installed universal on the lion and mountainlion buildbot workers only. It may be happening because libomp defaults to universal and libomp is a dependency of many clang compilers and many clang compilers do get installed as a necessity for building other ports. Presumably I could disable libomp's universal variant to avoid this.
Attachments (1)
Change History (4)
Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
comment:1 Changed 3 years ago by jmroot (Joshua Root)
comment:2 Changed 3 years ago by jmroot (Joshua Root)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
comment:3 Changed 3 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
| Cc: | MarcusCalhoun-Lopez added |
|---|
Note: See
TracTickets for help on using
tickets.
I wonder if the toolchain can't handle universal and LTO at the same time. Any difference if you build with -lto?