-
-
Notifications
You must be signed in to change notification settings - Fork 570
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
singular 3.1.7 fails to build using GCC 6 #20738
Comments
comment:2
This looks like OS X bits (macho-bundles). Has it also been tested on pre gcc-6.1 compilers? I guess the bots will answer that question soon. |
comment:3
Can you replace |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:5
Replying to @jdemeyer:
Done. |
comment:6
While this (or a similar patch I posted on sage-release) allows building Singular with GCC 6.1 (and without Seems we have to fiddle with optimization flags as well, which doesn't necessarily mean it's GCC's fault. IIRC, with (The previous segfaults happened immediately when initializing libsingular, as also reported by someone else on sage-release, in a thread for Sage 7.3.beta2 related to GCC 6.1 and BRiAl.) |
Changed keywords from GCC6 to GCC6 c++11 |
comment:8
My patch to Singular for C++11 is IMHO more straight-forward... ;-) --- singular-3.1.7p1/kernel/mod_raw.cc 2014-11-19 14:06:05.000000000 +0100
+++ singular-3.1.7p1/kernel/mod_raw.cc 2016-06-19 23:27:19.420554691 +0200
@@ -38,8 +38,8 @@
lib_types type_of_LIB(char *newlib, char *libnamebuf)
{
- const char mach_o[]={0xfe,0xed,0xfa,0xce,0};
- const char mach_o_module[]={0xce,0xfa,0xed,0xfe,0};
+ const char mach_o[]="\xfe\xed\xfa\xce";
+ const char mach_o_module[]="\xce\xfa\xed\xfe";
int i=0;
while(si_bultin_libs[i]!=NULL)
{ (I've put it into |
comment:9
Just for the record: If I compile everything except the Singular 3.1.7p1 package (the latter with GCC 5.4) with GCC 6.1.0, This still refers to Sage 7.2 (plus some work-arounds). So the Singular problem appears to be a singular one. XD |
Reviewer: Volker Braun |
comment:10
Singular works with |
comment:12
Replying to @nexttime:
That's the last test it was waiting for (with Singular 100% busy for a while):
Excluding unrelated failures in
The GAP failure is unrelated (but typical here, passes when rerun), while the forker doctest failure is indeed indirectly caused by Singular (or libsingular), also fails when rerun:
|
comment:13
All of the above Singular-related failures vanish when building Singular with |
Changed branch from u/aapitzsch/gcc6issue to |
Changed commit from |
comment:15
Replying to @nexttime:
With |
Till #17254 is ready. Let's add another patch to singular to fix a build issue with GCC 6.
Component: build
Keywords: GCC6 c++11
Author: André Apitzsch
Branch:
04c0af9
Reviewer: Volker Braun
Issue created by migration from https://trac.sagemath.org/ticket/20738
The text was updated successfully, but these errors were encountered: