[EMAIL PROTECTED] (Bob Proulx) wrote:
> Paul Eggert wrote:
>> Matthew Woehlke <[EMAIL PROTECTED]> writes:
>>
>> > I could probably do it on
>> > this box, but since it's Linux, it would still be with gcc.
>>
>> Even that would be helpful, since our current buildbot doesn't do the
>> particular comb
Jim Meyering wrote:
> Here's what Paul just added to Makefile.maint.
> That should do it, as long as you do that build
> on a relatively modern Linux system:
>
> $ grep -C2 ansi Makefile.maint
> && (cd src && patch -V never --fuzz=0&& ./configure --disable-largefi
Ben Pfaff <[EMAIL PROTECTED]> writes:
> The following actually makes an unconditional wrapper around
> , in the same way as the fcntl module does.
Is that needed? I'd think that the normal modern case wouldn't need
the wrapper. It'd be nice to avoid the wrapper in that case, since
the wrapper i
[EMAIL PROTECTED] (Bob Proulx) wrote:
> Jim Meyering wrote:
>> Here's what Paul just added to Makefile.maint.
>> That should do it, as long as you do that build
>> on a relatively modern Linux system:
>>
>> $ grep -C2 ansi Makefile.maint
>> && (cd src && patch -V never --fuzz=0 >
Sylvain Beucler <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 27, 2006 at 10:41:49PM +0100, Jim Meyering wrote:
>> Hi Sylvain,
>>
>> Do you know of a good way to sync a git repository to cvs?
>> Ideally, it'd happen upon each commit or push, via a hook.
>>
>> Currently I'm manually invoking a tiny scrip
[EMAIL PROTECTED] (Bob Proulx) wrote:
> Jim Meyering wrote:
>> Yes, but the code that decides whether to skip the test should know
>> whether there is a version of linux-2.4.x for which the bug is fixed.
>>
>> I guess you don't have access to an ia64 system with 2.4.X, 20 <= X ?
>
> I have one Debi
Jim Meyering <[EMAIL PROTECTED]> writes:
> If anyone in the audience has access to an ia64 system running a kernel
> newer than linux-2.4.19, would you please let me know?
SLES8 is using 2.4.21.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5,
Andreas Schwab <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
>> If anyone in the audience has access to an ia64 system running a kernel
>> newer than linux-2.4.19, would you please let me know?
>
> SLES8 is using 2.4.21.
Thanks.
I found a better way to handle this:
Paul Eggert wrote:
> Thanks, I like this change. I tested it for m4/stdint.m4, and
> installed that part of the change.
OK, so I installed the rest.
> Would you mind if we removed m4/ptrdiff_max.m4? Nobody has used it
> since 2003-11-12, as far as I know. stdint obsoletes it now, anyway.
Done
On 11/27/06, Bruno Haible <[EMAIL PROTECTED]> wrote:
There is no long-term stable interface between *.m4 and Makefile.in.in.
This means, you need to take both from the same version. And gnulib here
counts as the newest released gettext version.
OK. Is po/Makefile.in.in in gettext? If not,
Andreas Schwab wrote:
Matthew Woehlke writes:
(* You would need to (a) somehow force gcc to reject all non-c89
constructs
"-std=c89 -pedantic-errors" is supposed to do that.
Agreed, but as I recall, emphasis is needed on "is supposed to". But
maybe I recall incorrectly, or had incorrect exp
Matthew Woehlke <[EMAIL PROTECTED]> writes:
> (* You would need to (a) somehow force gcc to reject all non-c89
> constructs
"-std=c89 -pedantic-errors" is supposed to do that.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Ge
Jim Meyering wrote:
[EMAIL PROTECTED] (Bob Proulx) wrote:
Jim Meyering wrote:
Yes, but the code that decides whether to skip the test should know
whether there is a version of linux-2.4.x for which the bug is fixed.
I guess you don't have access to an ia64 system with 2.4.X, 20 <= X ?
I have
Ben Pfaff <[EMAIL PROTECTED]> writes:
> tests/test-base64.c in the gnulib repository checks out marked
> executable for me. Seems odd.
Here too. Is this possible to fix without direct access to the CVS
repository?
/Simon
eponymous alias <[EMAIL PROTECTED]> writes:
> The getaddrinfo.c file contains these lines within getaddrinfo():
>
>151if (hints && (hints->ai_flags & ~(AI_CANONNAME|AI_PASSIVE)))
>152 /* FIXME: Support more flags. */
>153 return EAI_BADFLAGS;
>
> followed later by:
>
>
Simon Josefsson <[EMAIL PROTECTED]> wrote:
>> tests/test-base64.c in the gnulib repository checks out marked
>> executable for me. Seems odd.
>
> Here too. Is this possible to fix without direct access to the CVS
> repository?
Yep, but it's a kludge.
Remove it and re-add without the execute bit
Jim Meyering writes:
>
> Simon Josefsson <[EMAIL PROTECTED]> wrote:
> >
> > Here too. Is this possible to fix without direct access to the CVS
> > repository?
>
> Yep, but it's a kludge.
> Remove it and re-add without the execute bit set.
I don't think that works -- CVS only sets the execute pe
The patch below causes this error when running configure for me:
checking absolute name of ... ///usr/include/stdint.h
checking whether stdint.h conforms to C99... no
./configure: line 31250: syntax error near unexpected token `('
./configure: line 31250: `if { as_var=sizeof ($gltype) * CHAR_BIT;
[EMAIL PROTECTED] (Larry Jones) wrote:
> Jim Meyering writes:
>> Simon Josefsson <[EMAIL PROTECTED]> wrote:
>> > Here too. Is this possible to fix without direct access to the CVS
>> > repository?
>>
>> Yep, but it's a kludge.
>> Remove it and re-add without the execute bit set.
>
> I don't think
James Youngman wrote:
> OK. Is po/Makefile.in.in in gettext? If not, do I need to obtain
> gettext from CVS as well?
po/Makefile.in.in is installed when you run gettextize. You shouldn't use
the gettext CVS regularly, except if you're specially keen on new gettext
features.
> > It's known, an
Simon Josefsson wrote:
> The patch below causes this error when running configure for me:
>
> checking absolute name of ... ///usr/include/stdint.h
> checking whether stdint.h conforms to C99... no
> ./configure: line 31250: syntax error near unexpected token `('
> ./configure: line 31250: `if { a
Bruno Haible <[EMAIL PROTECTED]> writes:
> You need to upgrade to autoconf 2.61. The signature of AC_COMPUTE_INT has
> changed between 2.60a and 2.61. (Such a change is normal. There is no
> promise of an API compatibility for a snapshot version of autoconf.)
For what it's worth, I hadn't realize
On 11/28/06, James Youngman <[EMAIL PROTECTED]> wrote:
OK. Is po/Makefile.in.in in gettext? If not, do I need to obtain
gettext from CVS as well?
Sorrym I meant, is it in gnulib? If not, where do I get the version
that works with current gnulib?
James.
Ben Pfaff <[EMAIL PROTECTED]> writes:
> Bruno Haible <[EMAIL PROTECTED]> writes:
>
>> You need to upgrade to autoconf 2.61. The signature of AC_COMPUTE_INT has
>> changed between 2.60a and 2.61. (Such a change is normal. There is no
>> promise of an API compatibility for a snapshot version of auto
On 11/28/06, Bruno Haible <[EMAIL PROTECTED]> wrote:
We have an autotools-announce (obviously at gnu.org) mailing list for this
purpose. Sorry the gettext-0.16 announcement didn't make it there.
Thanks for the tip. I didn't know about the list. This patch to
gnulib's README file lets other
"James Youngman" <[EMAIL PROTECTED]> writes:
>* README: Advise users that they might find the [EMAIL PROTECTED]
>and autotools-announce@gnu.org mailing lists useful.
Thanks, I applied that, along with a suggestion to use "cvs update -dP"
to synchronize.
I had a bit of trouble app
On Tue, Nov 28, 2006 at 11:32:55AM +0100, Jim Meyering wrote:
> Sylvain Beucler <[EMAIL PROTECTED]> wrote:
> > On Mon, Nov 27, 2006 at 10:41:49PM +0100, Jim Meyering wrote:
> >> Hi Sylvain,
> >>
> >> Do you know of a good way to sync a git repository to cvs?
> >> Ideally, it'd happen upon each comm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Meyering <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] (Larry Jones) wrote:
> > Jim Meyering writes:
> >> Simon Josefsson <[EMAIL PROTECTED]> wrote:
> >> > Here too. Is this possible to fix without direct access to the CVS
> >> > repository?
>
Ping!
I could also just go ahead and commit the tests/ part of this,
that would be sufficient to fix the test failure, and avoid glibc
synchronization issues.
* Ralf Wildenhues wrote on Wed, Nov 08, 2006 at 11:49:48PM CET:
>
> 2006-11-08 Ralf Wildenhues <[EMAIL PROTECTED]>
>
> * lib/argp
Sylvain Beucler wrote:
> I haven't setup an auto-packing commit hook so may need to have me do
> that. I'm planning to add something like in post-update:
>
> export GIT_DIR=coreutils.git
> git-count-objects
> # If > 5120k
> git repack
> git prune
A useful reference for update scripts is
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> I could also just go ahead and commit the tests/ part of this,
> that would be sufficient to fix the test failure, and avoid glibc
> synchronization issues.
That sounds good to me. Please give Sergey a couple of days first,
but if he's too busy, then
31 matches
Mail list logo
