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

gcc: patch and revision for Xcode bug #39041

Closed
wants to merge 1 commit into from

Conversation

zbeekman
Copy link
Contributor

@zbeekman zbeekman commented Apr 18, 2019


I'm still building and testing locally, please do not merge yet.

This is a work around for an Xcode bug, introduced in the latest Xcode release.

See:

@zbeekman zbeekman added do not merge maintainer feedback Additional maintainers' opinions may be needed and removed do not merge labels Apr 18, 2019
@zbeekman
Copy link
Contributor Author

Local build finished, and tests pass locally.

I think this is ready to 🚢 unless other maintainers want changes.

@fxcoudert
Copy link
Member

  • Sad that Apple, once again, does not care about compilers other than clang
  • OK on principle, but please put the patch on formula-patches and include it in a patch do block
  • Thanks for taking care of this!

@zbeekman zbeekman self-assigned this Apr 18, 2019
@zbeekman zbeekman removed the maintainer feedback Additional maintainers' opinions may be needed label Apr 18, 2019
@zbeekman
Copy link
Contributor Author

hmmm.... the patch recommended by the GCC devs didn't apply cleanly. I'll use the old patch instead...

@zbeekman
Copy link
Contributor Author

reverted the patch at formula-patches to the user contributed one from the forums: https://discourse.brew.sh/t/atomic-does-not-name-a-type-gcc8-should-be-updated-patched/4516/10

@zbeekman zbeekman added the ready to merge PR can be merged once CI is green label Apr 18, 2019
@zbeekman
Copy link
Contributor Author

@BrewTestBot test this please

@rjurney
Copy link

rjurney commented Apr 19, 2019

Seeing this problem on the latest (as of 4/18/19) version of Mac OS X Mojave (10.14.4) and XCode (10.2.1 (10E1001)). brew install gccproduced an error and pointed me here. I'm unable to build python-geohash as a result.

@EdmundMai
Copy link

Same, brew install postgis brought me here

@zbeekman
Copy link
Contributor Author

@rjurney and @EdmundMai when you guys are running brew install <formula> is it building from source? By default you should be getting bottled gcc and postgis. If you build gcc from source it will fail until this is merged, and other C++ projects built with gcc may also fail until this is merged.

As soon as CI is green (we don't have binary bottles to merge until then) this will get merged and should resolve your issue, assuming it's the error related to _Atomic...

@EdmundMai
Copy link

@zbeekman correct, it says it's building from source:

brew install postgis
==> Installing dependencies for postgis: gcc, szip, hdf5, jasper, json-c, libxml2, libdap, proj, libgeotiff, libpng, libpq, libspatialite, netcdf, openblas, python@2, numpy, freetype, fontconfig, gettext, libffi, glib, pixman, cairo, little-cms2, nspr, nss, openjpeg, qt, poppler, libtool, unixodbc, webp, xerces-c, zstd, gdal, protobuf, protobuf-c, boost, eigen, cgal and sfcgal
==> Installing postgis dependency: gcc
Warning: Building gcc from source:
  The bottle needs the Xcode CLT to be installed.
==> Downloading https://ftp.gnu.org/gnu/gcc/gcc-8.3.0/gcc-8.3.0.tar.xz
Already downloaded: /Users/edmundmai/Library/Caches/Homebrew/downloads/790ecda70af93e36763edcb183a8d4e91e433bee9bad9a60360addae9d8e82be--gcc-8.3.0.tar.xz
==> ../configure --build=x86_64-apple-darwin18.2.0 --prefix=/usr/local/Cellar/gcc/8.3.0 --libdir=/usr/local/Cellar/gcc/8.3.0/lib/gcc/8 --disabl
==> make BOOT_LDFLAGS=-Wl,-headerpad_max_install_names

@SMillerDev
Copy link
Member

With that log, installing the commandline tools should be enough to have it use bottles.

@fxcoudert fxcoudert closed this in a4c2a99 Apr 19, 2019
@fxcoudert
Copy link
Member

fxcoudert commented Apr 19, 2019

Two test failures to address: libmatio and nwchem

@zbeekman zbeekman deleted the gcc8-atomic-fix branch April 19, 2019 13:59
@scpeters scpeters mentioned this pull request Apr 19, 2019
@fxcoudert
Copy link
Member

@zbeekman can you look at applying the same fix to gcc@6 and gcc@7 please? see #38553

@zbeekman
Copy link
Contributor Author

sure!

@zbeekman zbeekman mentioned this pull request Apr 21, 2019
5 tasks
@petitout
Copy link

petitout commented Apr 21, 2019

Hi @zbeekman,
seems like it is still not merged.
meanwhile I tried :

brew remove gcc
brew tap androidports/patch
brew install -s androidports/patch/gcc

without success. I still have _atomic issue...
Any idea ?

@zbeekman
Copy link
Contributor Author

@petitout: Why are you tapping androidports/patch? This is now in homebrew-core.

If you need additional support please ask in discourse.brew.sh and include relavent logs and output of brew doctor.

For now try:

xcode-select --install # ensure you have xcode CLT
brew untap androidports/patch
brew update-reset
brew upgrade gcc

If that doesn't work, please post over on discourse.brew.sh

@Homebrew Homebrew locked as off-topic and limited conversation to collaborators Apr 22, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ready to merge PR can be merged once CI is green
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants