On Tue, Mar 30, 2010 at 4:33 PM, Dr. David Kirkby <david.kir...@onetel.net> wrote: > William Stein wrote: >> >> On Sun, Mar 28, 2010 at 3:51 PM, William Stein <wst...@gmail.com> wrote: >>> >>> On Mon, Mar 22, 2010 at 12:31 PM, Jaap Spies <j.sp...@hccnet.nl> wrote: >>>> >>>> Dr. David Kirkby wrote: >>>>> >>>>> William was keen that a new release was made quickly to fix the issues >>>>> which prevent 4.3.4 building on several linux distros. >>>>> >>>>> A patch is here: >>>>> >>>>> http://trac.sagemath.org/sage_trac/ticket/8567 >>>>> >>>>> If that is added, Sage should build ok on these linux distros, which >>>>> otherwise do not like it when there are two copies of iconv (system >>>>> install and $SAGE_LOCAL) >>>>> >>>> +1 >>>> >>>> Jaap >>> >>> I'll make such a release, hopefully tomorrow. I'm also going to >>> include #8612 and #8539, which are blocker bug fixes. >>> >>> William >> >> I just want to record in this thread that just now when preparing the >> Ubuntu-based VirtualBox Sage for Windows, I built sage-4.3.4. I then >> did "sage -upgrade", and the result did not work due to some weird >> iconv issue that appeared when importing the Sage library. I then >> manually forced installation of the iconv spkg (even though it is >> supposed to be disabled on Ubuntu), and then everything worked. >> >> So probably we're still going to have trouble with 4.3.5 and iconv. >> >> -- William >> > > Could it be a forward compatibility issue? > > 1) Sage 4.3.4 contains the latest iconv (1.13.1) > > 2) Code is Sage tests iconv, finds it's a late version, and makes use of the > features in the the latest version. > > 3) After doing a 'sage -upgrade', iconv 1.13.1 is removed. > > 4) After 'sage -upgrade' the system supplied iconv is the only iconv package > available. Any code which relied on new features in the latest iconv library > suddenly breaks, as those features no longer exist. > > Note, the iconv package I created deletes old copies of itself, as > spkg-install contains:
Yes, I'm sure this is the problem. Thus your iconv package in sage-4.3.5 will *break* most sage's version <= 4.3.4 that upgrade... Can you make a version of the spkg that doesn't delete the previous version on operating systems where iconv isn't going to be installed? I.e., make an spkg asap that tests if not on solaris or cygwin, and in that case immediately exits. This test should be first, before anything else. I can then post that spkg online, so "sage -upgrade" isn't broken. -- William > > ------------------- > > echo "Removing old iconv files if they exist" > # If iconv is updated, please double-check these are still necessary > # and that there are no extra files added. > > rm -f $SAGE_LOCAL/bin/iconv $SAGE_LOCAL/lib/charset.alias > rm -f $SAGE_LOCAL/lib/*libiconv* $SAGE_LOCAL/lib/libcharset* > rm -f $SAGE_LOCAL/include/iconv.h $SAGE_LOCAL/include/libcharset.h > rm -f $SAGE_LOCAL/include/localcharset.h > rm -rf $SAGE_LOCAL/share/doc/libiconv > rm -f $SAGE_LOCAL/share/man/man1/iconv* $SAGE_LOCAL/share/man/man3/iconv* > > # Only build iconv on Solaris and Cygwin > if [ "x$UNAME" != xSunOS ] && [ "x$UNAME" != xCYGWIN ] ; then > echo "iconv will not be installed, as it is only installed on" > echo "Solaris and Cygwin - see:" > echo "http://trac.sagemath.org/sage_trac/ticket/8567"; > exit 0 > fi > > echo "Installing iconv as the operating system is Solaris or Cygwin" > ------------------------ > > If iconv becomes a major issue, then perhaps downgrading R, which needed > iconv, might be a sensible solution. The ticket on which R was updated: > > http://trac.sagemath.org/sage_trac/ticket/6532 > > has the title "Make R build with recommended packages". The purpose of the > ticket was never to update R, but the update was an incidental change. The > ticket says: > > "Incidentally, we might as well upgrade now too - see > http://www.r-project.org/, where 2.10.0 has been released, and in a few days > 2.10.1 will be." > > Note there is a comment from Peter Jeremy "At least on FreeBSD, r-2.10.1 is > more broken than r-2.9.2." > > Given all the iconv issues were a result of updating R, which was not done > in response to any need to update R, but rather a "we might as well > upgrade", the n downgrading R would not be such a big loss in my opinion. > > That said, the iconv package will not build on anything except Solaris or > Cygwin, so I suspect the the .spkg removes iconv could be the problem. The > 'sage -upgrade' will actually *downgrade* the version of iconv. That > downgrade might be the cause of the problems. > > dave > > > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org > > To unsubscribe, reply using "remove me" as the subject. > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
