lysp fails to build on Ubuntu 14.04 about linuxbrew-core

[rwhogg]

From @sjackman on March 14, 2016 22:30

Does brew install gcc --with-glibc && brew install lysp work around this issue?

[rwhogg]

From @sjackman on March 14, 2016 22:31

I pushed faf5144 which may resolve this issue. Try it out.

[rwhogg]

I pushed faf5144 which may resolve this issue. Try it out.

No luck, unfortunately. Same problem. That said, it did fix the failing libxmp test!

[rwhogg]

brew install gcc --with-glibc && brew install lysp

No luck here either, but that's just because glibc fails to build (it says gcc-4.9 is not installed and the gcc I have is too old).

I was able to work around that with brew install glibc --with-cc=gcc, but that fails in the postinstall stage with "Inconsistency detected by ld.so: get-dynamic-info.h: 134: elf_get_dynamic_info: Assertion `info[15] == ((void *)0)' failed!"

I promptly removed glibc after seeing that, since I'm nervous about programs incorrectly linking to a broken libc. This issue is low priority, so no big deal.

[rwhogg]

From @sjackman on March 15, 2016 4:51

I've seen that error message before over here: Linuxbrew/legacy-linuxbrew#126

GCC 4.8.4 is plenty new enough. It shouldn't complain about an old GCC. If you have been using this Linuxbrew installation for a while, and don't have glibc installed, I'd recommend starting over with a clean installation of Linuxbrew and start with brew install gcc, which will install glibc and gcc. Everything should be easier after that.

[rwhogg]

From @sjackman on March 15, 2016 4:51

Do you have binutils installed? If not, you can try brew install binutils.

[rwhogg]

binutils was installed as a dependency right before I started to build glibc.

The funny thing is, I've been using Homebrew's GCC 5.3 for a couple of months now, precisely because of that "your gcc is ancient" error message.

[rwhogg]

From @sjackman on March 15, 2016 5:27

"your gcc is ancient" error message.

Does glibc give that error message? Can you quote it?

[rwhogg]

Does glibc give that error message?
It originally came up a few months ago; I don't remember what formula was causing the problem.

The exact text is "*** These critical programs are missing or too old: gcc". Which sounds to me like utter nonsense since the gcc in my PATH is Homebrew's 5.3 and the one in /usr/bin is 4.8.4.

I think you're right and I should probably reinstall from scratch. However, considering the massive number of packages I have installed at this point, I think I'm probably better off waiting until my next distro upgrade (I'm planning one in May).

Also, question: I need to keep track of which formulae fail for me, so I can eventually fix them. For a while, I had settled on only filing issues which I had effectively given up on and just tracking the rest on a wiki page, but then decided I shouldn't hide the issues from you. For issues which don't have an immediate, obvious fix (for which I obviously just provide the PR straight away, per your earlier advice), what would you rather I do?

[rwhogg]

From @sjackman on March 15, 2016 22:38

The exact text is "*** These critical programs are missing or too old: gcc". Which sounds to me like utter nonsense since the gcc in my PATH is Homebrew's 5.3 and the one in /usr/bin is 4.8.4.

That is nonsense. I think the glibc compiler check is failing somehow.

I changed the default behaviour of bottles today to install both glibc and gcc when the system's glibc is too old. Installing glibc without installing gcc was fraught with peril. gcc is often necessary since it provides the shared libraries libgcc_s.so and libstdc++.so.6.

Please do open an issue with a gist whenever you encounter a failed build. If someone else encounters that failed build as well, it's nice to have a history of the build failure corroborated by someone else.

[rwhogg]

From @sjackman on March 15, 2016 22:38

I want to add a new DSL construct fails_with_os :linux, "GitHub issue number" to mark formula that are known to fail.

[iMichka]

Trying to build it with our latest gcc and ubuntu version: #4795

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.