#20136: Various meataxe build issues
--------------------------------------+------------------------
       Reporter:  jdemeyer            |        Owner:
           Type:  defect              |       Status:  new
       Priority:  major               |    Milestone:  sage-7.1
      Component:  packages: optional  |   Resolution:
       Keywords:                      |    Merged in:
        Authors:                      |    Reviewers:
Report Upstream:  N/A                 |  Work issues:
         Branch:                      |       Commit:
   Dependencies:                      |     Stopgaps:
--------------------------------------+------------------------

Comment (by SimonKing):

 Hi Jeroen,

 Thank you for locating a couple of issues and opening the ticket! I am
 about to contact upstream

 Replying to [ticket:20136 jdemeyer]:
 > 3. meataxe assumes that `char` is `signed char` but that is not
 guaranteed by the C standard. This causes breakage on powerpc64le. A work-
 around with GCC is `-fsigned-char` but it's better to fix the sources.

 OK, but that would also require to either fix the sources (namely the
 Makefile), either by using `-fsigned-char` or by passing `CFLAGS`.

 > 4. the test-suite has race conditions: testing with `MAKE="make -j48"`
 fails while `MAKE="make -j1"` works.

 I have seen before that the test suite is flaky. Meataxe's test suite is
 about Meataxe executables that read and write data from files. Could file
 i/o be the reason for race conditions? Hm. Let's see what upstream has to
 say.

--
Ticket URL: <http://trac.sagemath.org/ticket/20136#comment:1>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to