Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OS X Universal Binary Support #2024

Closed
ashgti opened this issue Mar 18, 2012 · 12 comments
Closed

OS X Universal Binary Support #2024

ashgti opened this issue Mar 18, 2012 · 12 comments
Labels
A-driver Area: rustc_driver that ties everything together into the `rustc` compiler C-enhancement Category: An issue proposing an enhancement or a PR with one. O-macos Operating system: macOS

Comments

@ashgti
Copy link

ashgti commented Mar 18, 2012

On OS X a number of libraries are built universally. At the very least, it would be nice to tell rustc if your planning on targeting 32 or 64 bit in case your building against a library that is currently only available as one or the other. Currently, I think the only way of doing this is to specify a host triple at compile time and build the entire system as one or the other. It would be nice to be able to build universally on OS X and support targeting a specific architecture. The gcc and clang both support -m32 or -m64 as a simple solution to specifying the architecture, as well as -arch flags.

With clang and gcc -arch can be used to specify which architectures you want to build for, for example clang foo.c -o foo.o -arch i386 -arch x86_64 -arch ppc will tell the compiler to build a binary that supports 3 different architectures.

@catamorphism
Copy link
Contributor

Looks like #2084 blocks this.

@cooljeanius
Copy link

Is this still non-universal? The MacPorts port for Rust includes a +universal variant, and I'm just wondering if it does anything, or if I should remove it.

@cooljeanius
Copy link

(and by "or if I should remove it", I actually mean "or if I should have @g5pw remove it".)

@bstrie
Copy link
Contributor

bstrie commented Apr 29, 2013

It's been a year, and I don't own a mac. Is 32-bit support still relevant? What range of OS X does Rust support?

@cooljeanius
Copy link

What range of OS X does Rust support?

10.6+

@larryv
Copy link
Contributor

larryv commented Apr 29, 2013

Can’t you target 32-bit by specifying --target-triples=i686-apple-darwin when building Rust and --target=i686-apple-darwin when using rustc?

@catamorphism
Copy link
Contributor

By the way, it seems that the highest version of Mac OS X that a PPC Mac can run is 10.5.8, and since we don't support anything < 10.6 anyway, we don't need to worry about PPC. IA32, however, can run 10.6.8. Not sure how important it is.

@catamorphism
Copy link
Contributor

Nominating for milestone 3, feature-complete

@graydon
Copy link
Contributor

graydon commented Jul 11, 2013

just a bug, removing milestone/nomination.

@thestinger
Copy link
Contributor

Still an issue, but it feels like we're not going to implement this by the time Apple drops support for Snow Leopard anyway

@emberian
Copy link
Member

emberian commented Jan 6, 2014

Still an issue. I feel like it's pretty unimportant ATM.

@athei
Copy link
Contributor

athei commented Jun 25, 2020

With the upcoming transition to Apple Silicon it might become important to support Univeral Binaries.

celinval added a commit to celinval/rust-dev that referenced this issue Jun 4, 2024
Kobzol pushed a commit to Kobzol/rust that referenced this issue Dec 30, 2024
* linkcheck: fix reported broken links (part 2)

* Apply suggestions from code review

Co-authored-by: León Orell Valerian Liehr <[email protected]>

* Fix mir::Constant link target

* Fix borked links

* Fix one more link name

* Exclude 2 links from checking

* Fix exclude patterns in book.toml

* Fix comment

* Fix rmake-tests URL

* Apply suggestions from code review

Co-authored-by: León Orell Valerian Liehr <[email protected]>

---------

Co-authored-by: León Orell Valerian Liehr <[email protected]>
bors pushed a commit to rust-lang-ci/rust that referenced this issue Jan 2, 2025
* linkcheck: fix reported broken links (part 2)

* Apply suggestions from code review

Co-authored-by: León Orell Valerian Liehr <[email protected]>

* Fix mir::Constant link target

* Fix borked links

* Fix one more link name

* Exclude 2 links from checking

* Fix exclude patterns in book.toml

* Fix comment

* Fix rmake-tests URL

* Apply suggestions from code review

Co-authored-by: León Orell Valerian Liehr <[email protected]>

---------

Co-authored-by: León Orell Valerian Liehr <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-driver Area: rustc_driver that ties everything together into the `rustc` compiler C-enhancement Category: An issue proposing an enhancement or a PR with one. O-macos Operating system: macOS
Projects
None yet
Development

No branches or pull requests

9 participants