- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 601
Singular does not state return type of main() functions #12442
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
Comments
Attachment: singular-main-returns.patch.gz for review purposes |
Work Issues: Rebase the spkg on the p6 from #12680. |
Reviewer: Leif Leonhardy |
comment:2
FWIW, otherwise patch looks good... ;-) |
Changed keywords from none to spkg |
Author: R. Andrew Ohana |
comment:3
Has this been reported upstream (http://www.singular.uni-kl.de:8002/trac/newticket)? |
comment:6
Looks like there were meanwhile more instances (in Singular 3-1-5), although at least some of them are in test code which does not necessarily get built. |
Changed work issues from Rebase the spkg on the one from #14429. to Rebase the spkg on the latest one (presumably 3-1-5.p8). |
comment:7
Just to make you aware of #14737 (new spkg presumably coming up soon). |
comment:10
Might be fixed by #14333, try sage-6.2.beta0 when its out and report back... |
To be put into |
comment:14
Attachment: singular-3.1.6-no_return_type.patch.gz Replying to @nexttime:
New patch for Singular 3.1.6 attached. (No branch [yet], also because of #13331.) |
comment:15
Anyway... |
Changed work issues from Rebase the spkg on the latest one (presumably 3-1-5.p8). to none |
Changed author from R. Andrew Ohana to R. Andrew Ohana, Leif Leonhardy |
comment:17
Anyone feels like reviewing this if I create a branch? |
comment:18
This is fixed in Singular-4.0 |
comment:19
Great, but is it officially released (I'm aware there is tarball available) and is there anyone working on porting Sage to the new Singular interface? |
comment:20
Well the webpage still points to 3-1-6. If you want to patch 3-1-6 in the interim then go ahead, all I'm saying is that this will fix itself sooner or later. How much of a priority is building Sage with clang? |
comment:21
Actually I don't care, but I'd like to get #13331 in and this one was mentioned there. |
Changed reviewer from Leif Leonhardy to Leif Leonhardy, Jean-Pierre Flori |
comment:22
Still builds fine with the trivial patch, and it makes sense to me. I assume this was actually tested with clang, so positive review. |
Branch: u/jpflori/ticket/12442 |
New commits:
|
Commit: |
Changed reviewer from Leif Leonhardy, Jean-Pierre Flori to Leif Leonhardy, Jean-Pierre Flori, Volker Braun |
Changed branch from u/jpflori/ticket/12442 to |
This breaks building with clang.
I've posted an spkg fixes this (and #12441) at http://wstein.org/home/ohanar/clang-port/sage-5.0.beta1-src/spkg/standard/singular-3-1-3-3.p5.spkg. (This is a review spkg in case there are more issues with clang down the road.)
Component: packages: standard
Keywords: spkg
Author: R. Andrew Ohana, Leif Leonhardy
Branch/Commit:
d45f16b
Reviewer: Leif Leonhardy, Jean-Pierre Flori, Volker Braun
Issue created by migration from https://trac.sagemath.org/ticket/12442
The text was updated successfully, but these errors were encountered: