22.07.2015 00:32, Alexey Sokolov пишет:
>> I've had a busy day and I'm a little tired, so I'm probably about to
>> make a fool of myself on a public mailing list. Never mind :-) Three
>> points on the znc package:
>>
>> - Unless I've missed something, all this talk of DLL naming is a
>> little ac
> I've had a busy day and I'm a little tired, so I'm probably about to
> make a fool of myself on a public mailing list. Never mind :-) Three
> points on the znc package:
>
> - Unless I've missed something, all this talk of DLL naming is a
> little academic at the moment, as there is no 'dll.a'
On 21/07/2015 08:12, Corinna Vinschen wrote:
On Jul 20 19:58, Alexey Sokolov wrote:
Well, in that case 1.6 works fine. When 1.7.0 will be released, the
filename will be changed to cygznc-1.7.dll.
Assuming 1.7 does not break the ABI. The problem here is that modules
built for 1.6 won't run on 1
On 7/21/2015 4:25 PM, Achim Gratz wrote:
Ken Brown writes:
I've rebuilt clisp on both 32-bit and 64-bit, now using libsigsegv on
64-bit, and I don't see any regressions. In particular, it passes the
test suite. I don't know enough about clisp to test it further.
Does maxima still work with t
21.07.2015 08:12, Corinna Vinschen пишет:
> On Jul 20 19:58, Alexey Sokolov wrote:
Well, in that case 1.6 works fine. When 1.7.0 will be released, the
filename will be changed to cygznc-1.7.dll.
>
> Assuming 1.7 does not break the ABI.
Git master which will eventually become 1.7.0 alrea
Ken Brown writes:
> I've rebuilt clisp on both 32-bit and 64-bit, now using libsigsegv on
> 64-bit, and I don't see any regressions. In particular, it passes the
> test suite. I don't know enough about clisp to test it further.
Does maxima still work with the rebuilt clisp or do I need to rebuil
On 7/20/2015 9:03 AM, Ken Brown wrote:
On 7/20/2015 7:20 AM, Corinna Vinschen wrote:
I uploaded snapshots as well as a 2.2.0-0.1 test release. Please
give it a try.
Everything is fine as far as emacs is concerned. I'll rebuild clisp and
test it later today.
I've rebuilt clisp on both 32-bi
Corinna Vinschen writes:
> That's not sufficient, probably. I'm pretty sure you'd have to tweak
> setup as well.
Maybe, but the order setup itself imposes really comes into play only if
the system has a version installed that is not in setup.ini anymore and
that setup would order before all other
On Jul 21 18:59, Achim Gratz wrote:
> Corinna Vinschen writes:
> > How do you tell upset that a package uses a different numbering
> > scheme? You'd have two scenarios which can't be recognized
> > automatically, don't you?
>
> In the case of Perl distributions, I know the ordering scheme and it
Corinna Vinschen writes:
> How do you tell upset that a package uses a different numbering
> scheme? You'd have two scenarios which can't be recognized
> automatically, don't you?
In the case of Perl distributions, I know the ordering scheme and it's
built in to upset already, sort-of, only has
On Jul 20 19:58, Alexey Sokolov wrote:
> >> Well, in that case 1.6 works fine. When 1.7.0 will be released, the
> >> filename will be changed to cygznc-1.7.dll.
Assuming 1.7 does not break the ABI. The problem here is that modules
built for 1.6 won't run on 1.7, even if the ABI hasn't changed, be
11 matches
Mail list logo
