Simon Josefsson <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
>> Any objection to this?
>
> The patch is not needed now that intprops is now LGPLv2+. The comment
> would need to be adjusted, though, if you still want to push the patch.
Thanks. I noticed.
I'm glad my cha
Jim Meyering <[EMAIL PROTECTED]> writes:
> Any objection to this?
The patch is not needed now that intprops is now LGPLv2+. The comment
would need to be adjusted, though, if you still want to push the patch.
/Simon
> From 2fea9d6efde41eea3af51b45d27b31ed9f376b52 Mon Sep 17 00:00:00 2001
> From
Paolo Bonzini <[EMAIL PROTECTED]> wrote:
>> strerror.c appears to need intprops only for its
>> definition of the INT_STRLEN_BOUND macro, used here:
>>
>> {
>> char *result = strerror (n);
>>
>> if (result == NULL || result[0] == '\0')
>> {
>> static char const fmt[] = "Unkn
> strerror.c appears to need intprops only for its
> definition of the INT_STRLEN_BOUND macro, used here:
>
> {
> char *result = strerror (n);
>
> if (result == NULL || result[0] == '\0')
> {
> static char const fmt[] = "Unknown error (%d)";
> static char mesg[siz
Simon Josefsson <[EMAIL PROTECTED]> wrote:
> Using the perror module results in warnings:
>
> warning: module perror depends on a module with an incompatible license:
> intprops
> warning: module perror depends on a module with an incompatible license:
> strerror
>
> The reason appears to be beca
Simon Josefsson wrote:
> Does anyone see any problem with the patch below?
You can't change the copyright of code owned by the FSF if you are not
the copyright holder (FSF) and not the author (who has some rights by virtue
of the copyright assignment signed with the FSF).
In other words: For the
Using the perror module results in warnings:
warning: module perror depends on a module with an incompatible license:
intprops
warning: module perror depends on a module with an incompatible license:
strerror
The reason appears to be because perror is 'LGPLv2+' while intprops and
strerror is 'L
