-
Notifications
You must be signed in to change notification settings - Fork 136
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 doesn't cope with newly built openssl on r151014 #85
Comments
Thanks a lot GCC... I wonder if this affects r151016 as well? |
On Tue, Apr 12 2016 06:47:19 -0700, Dan McDonald wrote:
Yep, and bloody too. Lauri Tirkkonen | lotheac @ IRCnet |
On Tue, Apr 12 2016 17:07:08 +0300, Lauri Tirkkonen wrote:
I'll rephrase: the header exists in include-fixed on r151016 and Lauri Tirkkonen | lotheac @ IRCnet |
Fixed.
|
Per the original filer, I'm keeping this open --> like the illumos-building gcc44, gcc51 (or any of its replacements) shouldn't included extra header files like this. |
dbus: update to 1.11.14
OPENSSL_NO_MD2 is defined in openssl/opensslconf.h, but gcc "fixes" that
header at build time by copying it to its 'include-fixed' directory (shown in
cpp output above).
So effectively this means that gcc needs to be rebuilt if openssl configuration
changes. Although you could probably patch opensslconf.h instead to make gcc's
fixincludes not fix it.
In any case, this means that a fully updated 151014 box cannot build eg. perl
Net::SSLeay. A republished gcc package is required to fix that (either to
update the include-fixed header or to make it not end up there in the first
place).
Also interesting to note that there are 18 header files in that include-fixed
path on my 151014 box, whereas gcc-4.4.4's path only contains two...
The text was updated successfully, but these errors were encountered: