Bug 427250 - maxima --enable-gcl busted (x86_64)
Summary: maxima --enable-gcl busted (x86_64)
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: maxima
Version: 9
Hardware: x86_64
OS: Linux
low
low
Target Milestone: ---
Assignee: Rex Dieter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 428539
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-02 13:41 UTC by Rex Dieter
Modified: 2009-01-20 14:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-20 14:37:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Rex Dieter 2008-01-02 13:41:20 UTC
Atm, maxima --enable-gcl builds are busted.  ./configure fails with
configure: error: unable to run gcl executable "gcl".

Oddly, my own local mock builds are fine.  ??

See also
failed build: http://koji.fedoraproject.org/koji/buildinfo?buildID=29572
fedora-devel post:
https://www.redhat.com/archives/fedora-devel-list/2008-January/msg00012.html

Any ideas?

Comment 1 Rex Dieter 2008-01-02 13:42:24 UTC
fwiw, only x86_64 is failing, i386, ppc seem fine.

Comment 2 Rex Dieter 2008-01-02 13:44:14 UTC
nevermind about the ppc comment (no gcl there yet, per bug #167952) :)

Comment 3 Gérard Milmeister 2008-01-02 13:54:08 UTC
I cannot test myself on x86_64. The last build seemed to be ok, but
the build.log is no longer available, so I cannot check it.
gcl is really a pain on anything other than i386. I do not know
what other distros do. The Debian diff is a full 13MB!

Comment 4 Rex Dieter 2008-01-02 14:20:05 UTC
ok, I'll just disable x86_64/gcl for now (and reassign to maxima), until a
better solution presents itself.

Comment 5 Kevin Kofler 2008-01-02 14:45:31 UTC
gcl-pers.patch is trying to set the personality on /proc/self/exe. Looking at 
the equivalent patch for sbcl, there, Rex Dieter added this:
http://cvs.fedora.redhat.com/viewcvs/rpms/sbcl/devel/sbcl-0.9.5-personality.patch?rev=1.1&view=markup
The relevant lines:
+                    /* if /proc isn't available (like in chroot builds, like 
mock), 
+                     * try using execvp with argv[0] instead */
+                    execvp(argv[0], argv);

Could this be the origin of the breakage (maybe also the one on ppc)?

Comment 6 Kevin Kofler 2008-01-02 14:47:16 UTC
Especially as the comments below the use of /proc/self/exe in gcl-pers.patch 
say:
+         /* Either changing the personality or execve() failed. Either
+          * way we might as well continue, and hope that the random
+          * memory maps are ok this time around.
+          */
This looks very much like an explanation for non-reproducible errors to me.

Comment 7 Kevin Kofler 2008-01-04 05:39:28 UTC
This build failure of gcl itself also looks very much like this is the issue:
https://koji.fedoraproject.org/koji/getfile?taskID=323688&name=build.log

Comment 8 Bug Zapper 2008-05-14 04:16:39 UTC
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Rex Dieter 2009-01-20 14:37:45 UTC
* Sun Jan 18 2009 Rex Dieter <rdieter> - 5.17.1-3
- reenable gcl on i386 (#451801), x86_64 (#427250), ppc (#167952)


Note You need to log in before you can comment on or make changes to this bug.