On 22/01/11 02:38 , Martin Costabel wrote:
> On 21/01/11 20:42 , Alexander Hansen wrote:
>> On 1/21/11 1:44 PM, Jesse Alama wrote:
>>> On Jan 21, 2011, at 12:41, Alexander Hansen
>>> wrote:
>>>
Ick. If this link has different names in different languages, I guess
you'll need to test f
Hello Jesse,
I totally agree with you. This is a curious case.
As you wrote, if the package outputs a warning message, this is very
useful for users with localized system.
Ryuji Fukaya
2011/1/21 Jesse Alama :
> What a curious bug! Thanks for the investigation, Ryuji. I'm not sure how to
> de
On 21/01/11 20:42 , Alexander Hansen wrote:
> On 1/21/11 1:44 PM, Jesse Alama wrote:
>> On Jan 21, 2011, at 12:41, Alexander Hansen
>> wrote:
>>
>>> Ick. If this link has different names in different languages, I guess
>>> you'll need to test for all of them. Good thing there aren't an
>>> infi
On Jan 21, 2011, at 12:41, Alexander Hansen wrote:
> Ick. If this link has different names in different languages, I guess
> you'll need to test for all of them. Good thing there aren't an
> infinite number.
Yeah. I guess the first task is to find out just what languages are available.
Do I d
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 1/21/11 1:44 PM, Jesse Alama wrote:
> On Jan 21, 2011, at 12:41, Alexander Hansen
> wrote:
>
>> Ick. If this link has different names in different languages, I guess
>> you'll need to test for all of them. Good thing there aren't an
>> infinite
What a curious bug! Thanks for the investigation, Ryuji. I'm not sure how to
deal with this as a packager. One approach could be to look in the root
directory for this document, and warn the user if its not the English version?
Jesse
On Jan 20, 2011, at 20:08, Javier Arantegui wrote:
> Hi!
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ick. If this link has different names in different languages, I guess
you'll need to test for all of them. Good thing there aren't an
infinite number.
On 1/20/11 11:48 PM, Jesse Alama wrote:
> What a curious bug! Thanks for the investigation, Ryuji
Hi!
I just want to add that this solution solves this problem in my case.
I have installed Mac OS X in Spanish. Deleting the link "/Manuales e
información para el usuario" let me build the sbcl package.
Javier
On Thu, Jan 20, 2011 at 12:54 PM, Ryuji Fukaya wrote:
> Hello Mr. Sakai,
>
> The pro
Hello Mr. Sakai,
The problem has been solved. I removed the link that you mentioned and
I could compile "sbcl."
I appreciate your kindness.
Ryuji FUKAYA (Dr. Math. Sci.)
2011/1/20 Sakai, Kazuhiro :
> Hi all,
>
> The problem is the localized "User Guides and Information" directory in the
> root
Hi all,
The problem is the localized "User Guides and Information" directory in the
root (/). I installed Snow Leopard in Japanese, and the directory (actually a
symbolic link) got translated into Japanese.
To solve the issue, remove the directory (symbolic link) or move it to
somewhere else (
2011/1/1 Martin Costabel :
> On 31/12/10 16:30, Alexander Hansen wrote:
> []
>>
>> On 12/30/10 7:45 PM, Ryuji Fukaya wrote:
>
> []
>>
>> Form: (LET ((SB-POSIX-TESTS::DIR (SB-POSIX:OPENDIR "/")))
>
> []
>>
>> Actual value: #.
>
> Could this be a problem with language settings?
>
> --
> Martin
>
I a
On 31/12/10 16:30, Alexander Hansen wrote:
[]
> On 12/30/10 7:45 PM, Ryuji Fukaya wrote:
[]
> Form: (LET ((SB-POSIX-TESTS::DIR (SB-POSIX:OPENDIR "/")))
[]
> Actual value: #.
Could this be a problem with language settings?
--
Martin
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/30/10 7:45 PM, Ryuji Fukaya wrote:
> I compressed 2 log files, an output with (32bit fink, 64bit kernel)
> and an output with (32bit fink, 32 bit kernel), and I have emailed
> these to the maintainer.
> The output was same as my original post whe
I compressed 2 log files, an output with (32bit fink, 64bit kernel)
and an output with (32bit fink, 32 bit kernel), and I have emailed
these to the maintainer.
The output was same as my original post when I tried again with the
combination (32bit fink, 32bit kernel).
The compressed output logs are
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/30/10 5:36 PM, Ryuji Fukaya wrote:
> Hello all,
>
> My combination is (32bit fink, 64bit kernel):
> $ fink -V | head -n 2
> Package manager version: 0.29.17
> Distribution version: selfupdate-rsync Thu Dec 30 21:07:38 2010, 10.6, i386
>
> $ una
Hello all,
My combination is (32bit fink, 64bit kernel):
$ fink -V | head -n 2
Package manager version: 0.29.17
Distribution version: selfupdate-rsync Thu Dec 30 21:07:38 2010, 10.6, i386
$ uname -m; sysctl hw.model; sysctl machdep.cpu.brand_string
x86_64
hw.model: MacBookPro7,1
machdep.cpu.brand
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yeah, that's 64-bit Fink with 32-bit kernel. I tested that
combination--otherwise I wouldn't have updated maxima to use the new
sbcl. :-)
On 12/30/10 2:42 PM, Robert Wyatt wrote:
> Not sure what the question was, but in case it helps, the 64-bit versi
Not sure what the question was, but in case it helps, the 64-bit version
builds and installs for me:
New package:
dists/unstable/main/binary-darwin-x86_64/languages/sbcl_1.0.45-1_darwin-x86_64.deb
* My fink version: fink -V | head -n 2
Package manager version: 0.29.17
Distribution version: selfu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
One thing which stands out here as a possible issue is the combination
of a 32-bit Fink and a 64-kernel. Unfortunately, my machine isn't
capable of booting a 64-bit kernel, so I can't check this.
- --
Alexander Hansen, Ph.D.
Fink User Liaison
On
Hi Ryuji,
Sorry about this. Can you please send a complete build log?
Thanks,
Jesse
2010/12/30 深谷 竜司 :
> Hello,
>
> sbcl-1.0.45-1 fails to build:
>
> ; SYS:CONTRIB;SB-SPROF;SB-SPROF.FASL.NEWEST written
> ; compilation finished in 0:00:00.898
> * true
>
> WARNING! Some of the contrib modules di
Hello,
sbcl-1.0.45-1 fails to build:
; SYS:CONTRIB;SB-SPROF;SB-SPROF.FASL.NEWEST written
; compilation finished in 0:00:00.898
* true
WARNING! Some of the contrib modules did not build successfully or pass
their self-tests. Failed contribs:"
sb-posix
### execution of SBCL_ARCH="x86" failed, ex
21 matches
Mail list logo
