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

Update MacOS instructions to reflect changes in Catalina #380

Closed
wants to merge 1 commit into from

Conversation

mull
Copy link
Contributor

@mull mull commented Jun 8, 2020

No description provided.


First install Xcode via ```xcode-select --install``` and accept the license. ```xcodebuild -license```

Once you have installed XCode and the command line tools as well as agreed to the end user license you can install the prerequisite software either by using MacPorts or by using Homebrew.

With the release of MacOS Catalina, Apple no longer provides an installation of gcc. The command ```gcc``` is an alias for clang. When building Haiku you need to provide it with instructions to use gcc, which can be installed by both Homebrew and MacPorts. This process likely looks something like ```CC=/usr/local/bin/gcc-9 jam -q -j2 @nightly-anyboot```.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should not be necessary, the host tools can be built with Clang, and all other tools use the crosstools built using configure.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(If using Clang triggered errors, these should be fixed.)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If i remember correctly from discussing this on IRC, our Jamfiles end up passing -I- to clang instead of using -iquote. Something is probably wrong with us trying to detect gcc version from clang output, and we think it's a gcc2.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah that's correct. Should I open an issue on trac with the build output I get when clang is used?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please do. I'll close this then.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Redoing all steps from pre-reqs to building now. Homebrew does prevent force linking bison, so maybe the instructions should be updated in regards to that?

mull$Haiku brew link bison --force
Warning: Refusing to link macOS provided/shadowed software: bison
If you need to have bison first in your PATH run:
  echo 'export PATH="/usr/local/opt/bison/bin:$PATH"' >> /Users/mull/.bash_profile

For compilers to find bison you may need to set:
  export LDFLAGS="-L/usr/local/opt/bison/lib"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, indeed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants