From: Cyrus H. <ch...@bo...> - 2010-01-25 07:58:00
|
Just out of curiosity, did you try rebuilding 1.0.34.9 with itself and see if that fixed the problem? I'm wondering if there isn't some cross-compile problem with 1.0.34.9 built with a pre-1.0.34.9 build. thanks, Cyrus On Jan 24, 2010, at 1:33 PM, Harald Hanche-Olsen wrote: > + Harald Hanche-Olsen <ha...@ma...>: > >> Well, at least, rolling back just one commit to 1.0.34.8 (git commit >> 09e08ad0ba4eb09cd1a08ef5b7da527757ca78e5) cured it. I'll see if I can >> narrow it down further. (Real life keeps intruding ...) > > I poked around in the source a bit, and so it occured to me to try out > sb-unix:unix-stat in a good sbcl and a bad one. The results of > (sb-unix:unix-stat "/local/src/lisp/sbcl/sbcl-git/clean.sh") > which the bad sbcl thinks is a directory are as follows: > > 1.0.33.30 1.0.34.9 > T T > 234881026 234881026 > 936912 0 <--- inode number > 33261 19408 <--- mode > 1 14 > 13799 0 > 80 98797 > 0 13799 > 4147 80 > 1255394773 16 > 1237026090 1255394773 > 1245258805 1237026090 > 4096 4147 > 16 4096 > > The discrepancies are legion, most notably the mode, here translated > into octal: > > 100755 45720 > > The one on the left makes sense, the one on the right does not. > > It seems to me that the changes in 1.0.34.9 are too iffy to be part of > 1.0.34, unless someone can come up with a good explanation and fix. > Rollback time? > > - Harald > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for Conference > attendees to learn about information security's most important issues through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Sbcl-devel mailing list > Sbc...@li... > https://lists.sourceforge.net/lists/listinfo/sbcl-devel |