Kenneth Westerback writes:
> On 5 October 2015 at 11:51, Josh Elsasser wrote:
[...]
>> I thought I'd jumped in here but it looks like not.
>>
>> This builds and appears to pass tests on macppc, and builds an sbcl
>> which also passes its tests.
>>
>> The fact that the configure script appears
On 5 October 2015 at 11:51, Josh Elsasser wrote:
> On Mon, Oct 05, 2015 at 08:59:45AM -0400, Kenneth Westerback wrote:
>> On 2 October 2015 at 08:27, Kenneth Westerback wrote:
>> > On 2 October 2015 at 08:18, Jérémie Courrèges-Anglas
>> > wrote:
>> >> Kenneth Westerback writes:
>> >>
>> >>> On
On 2 October 2015 at 08:27, Kenneth Westerback wrote:
> On 2 October 2015 at 08:18, Jérémie Courrèges-Anglas wrote:
>> Kenneth Westerback writes:
>>
>>> On 30 September 2015 at 04:11, Jérémie Courrèges-Anglas
>>> wrote:
Last night I ran ''make; make clean'' in a loop on i386 and amd6
On 2 October 2015 at 08:18, Jérémie Courrèges-Anglas wrote:
> Kenneth Westerback writes:
>
>> On 30 September 2015 at 04:11, Jérémie Courrèges-Anglas
>> wrote:
>>>
>>> Last night I ran ''make; make clean'' in a loop on i386 and amd64.
>>>
>>> amd64: 142 builds / 0 failures
>>> i386: 58 builds
Kenneth Westerback writes:
> On 30 September 2015 at 04:11, Jérémie Courrèges-Anglas
> wrote:
>>
>> Last night I ran ''make; make clean'' in a loop on i386 and amd64.
>>
>> amd64: 142 builds / 0 failures
>> i386: 58 builds / 2 failures
>>
>> (same failure as yours)
>>
>> Maybe this has someth
On 30 September 2015 at 04:11, Jérémie Courrèges-Anglas wrote:
>
> Last night I ran ''make; make clean'' in a loop on i386 and amd64.
>
> amd64: 142 builds / 0 failures
> i386: 58 builds / 2 failures
>
> (same failure as yours)
>
> Maybe this has something to do with this...
>
> [...]
> checking
Last night I ran ''make; make clean'' in a loop on i386 and amd64.
amd64: 142 builds / 0 failures
i386: 58 builds / 2 failures
(same failure as yours)
Maybe this has something to do with this...
[...]
checking for the code address range... 0x1600
checking for the malloc address range...
On 29 September 2015 at 19:43, Jérémie Courrèges-Anglas wrote:
> Kenneth Westerback writes:
>
> [...]
>
>> That didn't take long.
>>
>> cc -I/usr/local/include
>> -I/home/packages/wrkobj/clisp-2.49/build-i386/gllib -O2 -pipe -W
>> -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type
>> -Wm
Kenneth Westerback writes:
[...]
> That didn't take long.
>
> cc -I/usr/local/include
> -I/home/packages/wrkobj/clisp-2.49/build-i386/gllib -O2 -pipe -W
> -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type
> -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2
> -fexpensi
On 29 September 2015 at 07:54, Kenneth Westerback wrote:
> On 29 September 2015 at 04:24, Jérémie Courrèges-Anglas
> wrote:
>> Kenneth Westerback writes:
>>
>>> I can probably set up build tests on i386 and sparc64 and eventually
>>> macppc if that would help.
>>
>> That would be great. :)
>>
>
On 29 September 2015 at 04:24, Jérémie Courrèges-Anglas wrote:
> Kenneth Westerback writes:
>
>> I can probably set up build tests on i386 and sparc64 and eventually
>> macppc if that would help.
>
> That would be great. :)
>
> --
> jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74A
Kenneth Westerback writes:
> I can probably set up build tests on i386 and sparc64 and eventually
> macppc if that would help.
That would be great. :)
--
jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
I can probably set up build tests on i386 and sparc64 and eventually
macppc if that would help.
Ken
On 28 September 2015 at 19:39, Jérémie Courrèges-Anglas wrote:
>
> I've had several tentative diffs to update clisp, but every time
> I delete them because of frustrations with the build sys
I've had several tentative diffs to update clisp, but every time
I delete them because of frustrations with the build system.
This has to stop!
Here's a tentative diff, probably not perfect. I did not enable the use
of shared modules, cause I don't know how to use them. There are a few
missing
14 matches
Mail list logo
