Singular build failure on OS X 10.4 when directory name is long

[jdemeyer]

When building Sage within a directory with a long name, singular fails to build on OS X 10.4. For example:

$ pwd
/Users/jdemeyer/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-sage-4.8

This problem was discovered by the newly added "moufang" (UGent) buildbot.

This is because of a problem with src/factory/configure and is fixed by generating configure with a more recent autoconf version.

Reported upstream: http://www.singular.uni-kl.de:8002/trac/ticket/399

spkg: http://boxen.math.washington.edu/home/jdemeyer/spkg/singular-3-1-3-3.p4.spkg

Upstream: Fixed upstream, but not in a stable release.

CC: @malb @kcrisman

Component: packages: standard

Author: Jeroen Demeyer

Reviewer: Karl-Dieter Crisman

Merged: sage-5.0.beta0

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

[jdemeyer]

Upstream: Reported upstream. Little or no feedback.

[kcrisman]

comment:3

So do you think this is the problem I had? After all, names with prealpha in them are longer than those with alpha in them...

[jdemeyer]

comment:4

Replying to @kcrisman:

So do you think this is the problem I had?

The new spkg fixes a problem, but I don't know if this caused your build failure. Just try the new spkg here and let me know whether it works...

[jdemeyer]

comment:5

Replying to @kcrisman:

So do you think this is the problem I had?

No, I reproduced your problem. It has nothing to do with Singular, it is caused by #11073. Can you copy the file spkg/bin/testcc.sh to local/bin/testcc.sh and try building again? This file was moved in #11073.

[jdemeyer]

Changed upstream from Reported upstream. Little or no feedback. to Fixed upstream, but not in a stable release.

[kcrisman]

comment:7

So do you think this is the problem I had?

No, I reproduced your problem. It has nothing to do with Singular, it is caused by #11073. Can you copy the file spkg/bin/testcc.sh to local/bin/testcc.sh and try building again? This file was moved in #11073.

I finally was able to get Xcode for one of my old home computers with similar specs, and building 5.0.beta0 went fine (which has the full #11073, including the cp to local/bin). Still checking on my work computer but no problems in Singular thus far.

[kcrisman]

comment:8

I can try to build Sage with a really long directory name if you'd like to test this ticket. How long will it have to be?

[jdemeyer]

comment:9

It doesn't have to be super-long, try the example in the ticket description.

[kcrisman]

comment:10

It doesn't have to be super-long, try the example in the ticket description.

Okay, I'll try this when the load is lower on that computer.

---

The #11073 definitely was fixed, thanks.

[kcrisman]

comment:11

Okay, I have now observed the failure. I've downloaded the new spkg and should know more in about an hour. Actually, more like five minutes since that's where the other one broke, but might as well let it finish :)

[kcrisman]

Reviewer: Karl-Dieter Crisman

[kcrisman]

comment:12

It works! I will not try this on other platforms, trusting it works to the release manager. I'm certainly not going to try to compare that new conf file to the old one, and I don't understand it in any case.

It seems like the changes in the spkg are not checked in, though. Since that's the case, you might as well fix the typo "spgk-changes" in SPKG.txt.

[jdemeyer]

comment:13

Replying to @kcrisman:

It works! I will not try this on other platforms, trusting it works to the release manager.

In any case, the release will be tested on the buildbot.

I'm certainly not going to try to compare that new conf file to the old one, and I don't understand it in any case.

Obviously, you shouldn't. Now that upstream made the same change, you can consider the patch as coming from upstream.

It seems like the changes in the spkg are not checked in, though.

Done.

Since that's the case, you might as well fix the typo "spgk-changes" in SPKG.txt.

Done.

[kcrisman]

comment:14

Looks good.

[jdemeyer]

Merged: sage-5.0.beta0