[sage-support] Re: Mercurial problems in 3.1.2
On Sep 22, 2008, at 22:24 , mabshoff wrote: Nope, none of those fixes is in alpha0, but I hope that at least some of them will make it into alpha1, due out late tomorrow. I still don't see how parallel make impacts numpy, so if you could send me the portion of the blown up numpy build with parallel make I could attempt to figure out what is wrong. See sage.math.washington.edu:~justin/logs/sage-numpy.log (the whole shebang; maybe something early on triggered it :-}). Justin -- Justin C. Walker, Curmudgeon-At-Large Institute for the Enhancement of the Director's Income When LuteFisk is outlawed, Only outlaws will have LuteFisk --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Mercurial problems in 3.1.2
On Sep 22, 11:39 pm, Justin C. Walker [EMAIL PROTECTED] wrote: On Sep 22, 2008, at 22:24 , mabshoff wrote: Nope, none of those fixes is in alpha0, but I hope that at least some of them will make it into alpha1, due out late tomorrow. I still don't see how parallel make impacts numpy, so if you could send me the portion of the blown up numpy build with parallel make I could attempt to figure out what is wrong. See sage.math.washington.edu:~justin/logs/sage-numpy.log (the whole shebang; maybe something early on triggered it :-}). Thanks. Numpy is complaining about a missing math module, but I think that is more likely caused by the libpng.dylib disaster than anything else. I just checked the python.spkg and we are running make install with parallel make, which I would guess is not a good idea :) The ticket for that issue is #4174 and there should be an spkg shortly. Justin Cheers, Michael -- Justin C. Walker, Curmudgeon-At-Large Institute for the Enhancement of the Director's Income When LuteFisk is outlawed, Only outlaws will have LuteFisk --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Mercurial problems in 3.1.2
On Sep 21, 11:27 pm, Justin C. Walker [EMAIL PROTECTED] wrote: Hi, all, I'm on Mac OS X, 10.5.4 (dual quad xeon), and when I run sage -hg commit, I get this SNIP Anyone seen this? This is the same crap issue you hit when building 3.1.2.rc-something, i.e. emacs is linked against Apple's libnpng while launching it from hg causes it to pick up out linpng. Results in *boom*. You can work around this by writing an emacs script in SAGE_LOCAL/bin that sets DYLD_LIBRARY_PATH to the old DYLD_LIBRARY_PATH and then launches emacs. Is someone can find out where Apple has its modifications to libpng this issue can be resolved. Justin Cheers, Michael -- Justin C. Walker, Curmudgeon-At-Large, Director Institute for the Enhancement of the Director's Income The path of least resistance: it's not just for electricity any more. --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Mercurial problems in 3.1.2
On Sep 21, 2008, at 23:35 , mabshoff wrote: On Sep 21, 11:27 pm, Justin C. Walker [EMAIL PROTECTED] wrote: [snip] Anyone seen this? This is the same crap issue you hit when building 3.1.2.rc-something, i.e. emacs is linked against Apple's libnpng while launching it from hg causes it to pick up out linpng. Results in *boom*. You can work around this by writing an emacs script in SAGE_LOCAL/bin that sets DYLD_LIBRARY_PATH to the old DYLD_LIBRARY_PATH and then launches emacs. Is someone can find out where Apple has its modifications to libpng this issue can be resolved. Hard to say where they keep it, but they (Apple) appear to be using 1.2.24, while we (Sage) appear to be using 1.2.22 (assuming these are version numbers). Might that be the cause? I'll see if I can find out where the source is; if Apple made changes, they should be available (ether directly from Apple, or from upstream - assuming the license requires this, of course. Does it?). It's bedtime for me; early class field theory tomorrow. Thanks for the response. Justin -- Justin C. Walker, Curmudgeon-at-Large () The ASCII Ribbon Campaign /\ Help Cure HTML Email --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Mercurial problems in 3.1.2
On Sep 21, 2008, at 23:35 , mabshoff wrote:
On Sep 21, 11:27 pm, Justin C. Walker [EMAIL PROTECTED] wrote:
This is the same crap issue you hit when building 3.1.2.rc-something,
i.e. emacs is linked against Apple's libnpng while launching it from
hg causes it to pick up out linpng. Results in *boom*. You can work
around this by writing an emacs script in SAGE_LOCAL/bin that sets
DYLD_LIBRARY_PATH to the old DYLD_LIBRARY_PATH and then launches
emacs.
Well, that worked. I actually used SAGE_ORIG_{LD,DYLD}_LIBRARY_PATH
to get it to work in all the cases I tried (and had to check the
$XXX_SET variables as well). Thanks for the work-around.
Is someone can find out where Apple has its modifications to libpng
this issue can be resolved.
I'll guess that it's a difference between versions (1.2.22 vs.
1.2.24), but I can't find old source on the libpng site, and it
doesn't show up on the Darwin site (which I infer means that they did
not change anything). I'll poke further, but if anyone has a better
idea, speak up!
Justin
--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
---
My wife 'n kids 'n dogs are gone,
I can't get Jesus on the phone,
But Ol' Milwaukee's Best is my best friend.
---
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-support] Re: Mercurial problems in 3.1.2
On Sep 22, 8:41 pm, Justin C. Walker [EMAIL PROTECTED] wrote:
On Sep 21, 2008, at 23:35 , mabshoff wrote:
Hi Justin,
On Sep 21, 11:27 pm, Justin C. Walker [EMAIL PROTECTED] wrote:
This is the same crap issue you hit when building 3.1.2.rc-something,
i.e. emacs is linked against Apple's libnpng while launching it from
hg causes it to pick up out linpng. Results in *boom*. You can work
around this by writing an emacs script in SAGE_LOCAL/bin that sets
DYLD_LIBRARY_PATH to the old DYLD_LIBRARY_PATH and then launches
emacs.
Well, that worked. I actually used SAGE_ORIG_{LD,DYLD}_LIBRARY_PATH
to get it to work in all the cases I tried (and had to check the
$XXX_SET variables as well). Thanks for the work-around.
No problem, good that it works for you.
Is someone can find out where Apple has its modifications to libpng
this issue can be resolved.
I'll guess that it's a difference between versions (1.2.22 vs.
1.2.24), but I can't find old source on the libpng site, and it
doesn't show up on the Darwin site (which I infer means that they did
not change anything). I'll poke further, but if anyone has a better
idea, speak up!
I am playing with libpng-1.2.32 since that is the latest release and
also has a boatload of security updates since the lowly 1.2.22 that we
ship. Hopefully this will resolve the symbol missing issues. I am
testing 3.1.3.alpha0 on OSX 10.5 to see if I can hit any of those
problems.
Justin
Cheers,
Michael
--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
---
My wife 'n kids 'n dogs are gone,
I can't get Jesus on the phone,
But Ol' Milwaukee's Best is my best friend.
---
--~--~-~--~~~---~--~~
To post to this group, send email to sage-support@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/sage-support
URLs: http://www.sagemath.org
-~--~~~~--~~--~--~---
[sage-support] Re: Mercurial problems in 3.1.2
On Sep 22, 2008, at 21:33 , mabshoff wrote: On Sep 22, 8:41 pm, Justin C. Walker [EMAIL PROTECTED] wrote: On Sep 21, 2008, at 23:35 , mabshoff wrote: [snip] I'll guess that it's a difference between versions (1.2.22 vs. 1.2.24), but I can't find old source on the libpng site, and it doesn't show up on the Darwin site (which I infer means that they did not change anything). I'll poke further, but if anyone has a better idea, speak up! I am playing with libpng-1.2.32 since that is the latest release and also has a boatload of security updates since the lowly 1.2.22 that we ship. Hopefully this will resolve the symbol missing issues. I am testing 3.1.3.alpha0 on OSX 10.5 to see if I can hit any of those problems. Is 1.2.32 in alpha0? As well as the md5 and numpy fixes (for parallel building)? Justin -- Justin C. Walker, Curmudgeon-At-Large Institute for the Absorption of Federal Funds Men are from Earth. Women are from Earth. Deal with it. --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
[sage-support] Re: Mercurial problems in 3.1.2
On Sep 22, 10:16 pm, Justin C. Walker [EMAIL PROTECTED] wrote: On Sep 22, 2008, at 21:33 , mabshoff wrote: [snip] Hi Justin, I am playing with libpng-1.2.32 since that is the latest release and also has a boatload of security updates since the lowly 1.2.22 that we ship. Hopefully this will resolve the symbol missing issues. I am testing 3.1.3.alpha0 on OSX 10.5 to see if I can hit any of those problems. Is 1.2.32 in alpha0? As well as the md5 and numpy fixes (for parallel building)? Nope, none of those fixes is in alpha0, but I hope that at least some of them will make it into alpha1, due out late tomorrow. I still don't see how parallel make impacts numpy, so if you could send me the portion of the blown up numpy build with parallel make I could attempt to figure out what is wrong. Justin Cheers, Michael -- Justin C. Walker, Curmudgeon-At-Large Institute for the Absorption of Federal Funds Men are from Earth. Women are from Earth. Deal with it. --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~--~~~~--~~--~--~---
