Skip to content
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

Gap 4.6.3 upgrade #14039

Closed
vbraun opened this issue Jan 30, 2013 · 30 comments
Closed

Gap 4.6.3 upgrade #14039

vbraun opened this issue Jan 30, 2013 · 30 comments

Comments

@vbraun
Copy link
Member

vbraun commented Jan 30, 2013

And now MPIR defines __GNU_MP_RELEASE so the __GMP_MP_RELEASE hack is not needed anymore here or in gap spkg.

Depends on #14014

Component: packages: standard

Reviewer: Travis Scrimshaw

Issue created by migration from https://trac.sagemath.org/ticket/14039

@vbraun vbraun added this to the sage-5.8 milestone Jan 30, 2013
@jdemeyer

This comment has been minimized.

@jdemeyer jdemeyer modified the milestones: sage-5.8, sage-5.9 Mar 8, 2013
@jdemeyer jdemeyer changed the title Gap 4.6.0 upgrade Gap 4.6.2 upgrade Mar 8, 2013
@jdemeyer
Copy link

jdemeyer commented Mar 8, 2013

comment:2

Would this require also an upgrade of gap_packages?

@jdemeyer
Copy link

jdemeyer commented Mar 8, 2013

Author: Jeroen Demeyer

@jdemeyer

This comment has been minimized.

@jdemeyer
Copy link

jdemeyer commented Mar 8, 2013

comment:5

Volker, any idea what to do about this:

sage -t  "devel/sage/sage/groups/libgap_wrapper.pyx"
An error occurred, but libGAP has no handler set.
Error message:
An error occurred, but libGAP has no handler set.
Error message:
**********************************************************************
File "/release/merger/sage-5.8.beta4/devel/sage/sage/groups/libgap_wrapper.pyx", line 12:
    sage: from sage.groups.libgap_wrapper import ElementLibGAP, ParentLibGAP
Exception raised:
    Traceback (most recent call last):
      File "/release/merger/sage-5.8.beta4/local/bin/ncadoctest.py", line 1231, in run_one_test
        self.run_one_example(test, example, filename, compileflags)
      File "/release/merger/sage-5.8.beta4/local/bin/sagedoctest.py", line 38, in run_one_example
        OrigDocTestRunner.run_one_example(self, test, example, filename, compileflags)
      File "/release/merger/sage-5.8.beta4/local/bin/ncadoctest.py", line 1172, in run_one_example
        compileflags, 1) in test.globs
      File "<doctest __main__.example_0[2]>", line 1, in <module>
        from sage.groups.libgap_wrapper import ElementLibGAP, ParentLibGAP###line 12:
    sage: from sage.groups.libgap_wrapper import ElementLibGAP, ParentLibGAP
      File "libgap_wrapper.pyx", line 62, in init sage.groups.libgap_wrapper (sage/groups/libgap_wrapper.c:5712)
      File "libgap.pyx", line 574, in init sage.libs.gap.libgap (sage/libs/gap/libgap.c:4203)
      File "libgap.pyx", line 395, in sage.libs.gap.libgap.Gap.__init__ (sage/libs/gap/libgap.c:2747)
      File "util.pyx", line 215, in sage.libs.gap.util.initialize (sage/libs/gap/util.c:3538)
    RuntimeError: libGAP initialization failed


    You are running a GAP kernel which does not fit with the library.
    Probably you forgot to apply the kernel part or the library part
    of a bugfix?

    If you are using Windows, make sure you installed the file
    wbin4r6n2.zoo (or .zip),
    Macintosh users make sure the file
    bin4r6n2-PPC.sit (or -68k.sit) is installed,
    Unix users please recompile.

    Error before error-handling is initialized: Update to correct kernel version!


    #W Static module lib/oper1.g has CRC mismatch, ignoring
    Error before error-handling is initialized:

**********************************************************************

Running ./sage -b doesn't really do much, could there be some dependencies missing?

@vbraun
Copy link
Member Author

vbraun commented Mar 9, 2013

comment:6

LibGAP needs to be kept in sync since it uses the GAP library from the stand-alone GAP install. I can update libgap...

@jdemeyer
Copy link

jdemeyer commented Mar 9, 2013

comment:7

Replying to @vbraun:

LibGAP needs to be kept in sync since it uses the GAP library from the stand-alone GAP install. I can update libgap...

OK, sounds good.

@vbraun
Copy link
Member Author

vbraun commented Mar 10, 2013

comment:8
  • The gap_packages and database_gap spkgs might need to be updated.
  • Changes are not checked in

@vbraun
Copy link
Member Author

vbraun commented Mar 10, 2013

comment:9

I've added the corresponding libgap spkg. I didn't make any real changes, only applied the GAP 4.5.7->4.6.2 diffs.

@vbraun
Copy link
Member Author

vbraun commented Mar 10, 2013

Changed author from Jeroen Demeyer to Jeroen Demeyer, Volker Braun

@vbraun

This comment has been minimized.

@vbraun

This comment has been minimized.

@vbraun
Copy link
Member Author

vbraun commented Mar 10, 2013

comment:11

For the record: I based the libgap spkg on the libgap version that awaits review at #14014.

There are a few doctests that fail because of changed GAP notation for some group elements.

@vbraun
Copy link
Member Author

vbraun commented Mar 10, 2013

Dependencies: #14014

@vbraun

This comment has been minimized.

@jdemeyer
Copy link

comment:14

Does this really depend on #14014? If not, could you upgrade the libGAP spkg to 4.6.3?

@jdemeyer jdemeyer changed the title Gap 4.6.2 upgrade Gap 4.6.3 upgrade Apr 25, 2013
@jdemeyer

This comment has been minimized.

@vbraun
Copy link
Member Author

vbraun commented Apr 25, 2013

comment:16

gap, libgap, database_gap, and gap_packages must be kept in sync.

@jdemeyer

This comment has been minimized.

@jdemeyer
Copy link

comment:18

Replying to @vbraun:

gap, libgap, database_gap, and gap_packages must be kept in sync.

Sure. I can do all packages except for libGAP.

@vbraun
Copy link
Member Author

vbraun commented Apr 25, 2013

comment:19

The patch depends on #14014

@vbraun

This comment has been minimized.

@vbraun
Copy link
Member Author

vbraun commented Apr 25, 2013

comment:21

The siginterrupt.patch has been upstreamed

@vbraun

This comment has been minimized.

@vbraun
Copy link
Member Author

vbraun commented Apr 25, 2013

Attachment: trac_14039_doctest_fixes.patch.gz

Updated patch

@vbraun
Copy link
Member Author

vbraun commented Apr 25, 2013

comment:22

All doctests pass for me...

@SnarkBoojum
Copy link
Mannequin

SnarkBoojum mannequin commented May 14, 2013

comment:23

I combined those packages and patches with those of ticket #14014, and things compile and doctest (except the quadratic forms ones which fail on this box anyway).

I'm not sure I can give a positive review though: the patches change the result of many tests, and I have no idea if they really replace a correct value by another correct value...

@vbraun
Copy link
Member Author

vbraun commented Jun 3, 2013

comment:24

Superseded by #14682

@vbraun vbraun removed this from the sage-5.10 milestone Jun 3, 2013
@tscrim
Copy link
Collaborator

tscrim commented Jun 4, 2013

Changed author from Jeroen Demeyer, Volker Braun to none

@tscrim
Copy link
Collaborator

tscrim commented Jun 4, 2013

Reviewer: Travis Scrimshaw

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants