Ben Pfaff wrote:
> Eric Blake writes:
>
>> Jim Meyering meyering.net> writes:
>>> -mbstate_t _gl_mbsrtowcs_state = 0;
>>> +mbstate_t _gl_mbsrtowcs_state = { 0, };
>> Is this correct for all platforms? If I read Posix correctly, mbstate_t can
>> be
>> a numeric type rather than a struct.
>
>
Karl Berry wrote:
> Please excuse my (mostly-ignorant) intrusion, but are you sure Red Hat
> does not already have an assignment on file? (I'm sure I heard somewhere
> that they do at least for certain GNU projects...)
>
> Indeed, Red Hat does, as an employer. I have been told that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Haible wrote:
> If gnulib-tool was to be rewritten in another programming language than
> shell + sed, what would be the good choices?
>
> The foremost criteria IMO should be the maintainability, i.e. the ability for
> us and for new contributor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Paul Eggert wrote:
> Eric Blake <[EMAIL PROTECTED]> writes:
>
>> Would anyone object to modifying GNUmakefile to also cause
>> recompilation for new version info prior to any 'make install' of a VCS
>> snapshot development build, when .tarball-versi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Josefsson wrote:
> Another problem that I discovered is that gnulib's getpass.c inhibits
> signals, so the user cannot press ^C/^Z. This is even more of a problem
> when the user needs to type the same password twice: the process may be
> stuck
Simon Josefsson wrote:
> I'm not sure it is a good idea to recommend use of getpass, possibly
> gnulib could offer a better interface. It could have a parameter to ask
> for confirmation of the password internally. However, I will use
> getpass for now since I don't want to introduce a lot of cha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Josefsson wrote:
>>> http://www.opengroup.org/onlinepubs/009695399/functions/strftime.html
>>>
>>> that specifier was not part of SUS.
>> Um, I see it on that page, don't you?
>
> Yes, so that makes it part of POSIX. Further down on that page,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Josefsson wrote:
> In this report:
>
> http://thread.gmane.org/gmane.network.gnutls.general/1145/focus=1170
>
> It seems that strftime on Windows doesn't support %e.
>
> According to:
>
> http://www.opengroup.org/onlinepubs/009695399/function
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Haible wrote:
> Simon Josefsson wrote:
>> # define __func__ ""
>
> Some packages use
>#define __func__ __FILE__
> in this case. Not perfect, but still more informative than "".
But, wouldn't one normally include __FILE__ in diagno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric Blake wrote:
> Meanwhile, whether or not the decision is made to go with \ vs. % quoting,
> I think it shouldn't be too hard to make the quotearg module support both
> styles, so I'll tackle an implementation of % quoting next.
What will it do wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Haible wrote:
> When a user is getting an error message from 'msgfmt', and the user is a
> translator who has never written any code in any programming language,
> why should the error message she shall see be influenced by the syntax
> of progra
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karl Berry wrote:
> | "C escapes" means to use the backslash character as escape character.
> | This is a particularly bad choice, because - as you know - on some
> systems,
> | backslahes are used as directory separator.
>
> That hardly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Karl Berry wrote:
> I don't think it's exactly "recommended"; it's mentioned as an
> alternative, but in a rather ambiguous way (at least if we're talking
> about the same thing, in the Change Log Concepts node of standards.texi):
>
>Another a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Haible wrote:
> Jim Meyering wrote yesterday:
>> With the proliferation of "topic branches" in my work-flow, it is not
>> effective for me to version-control ChangeLog files (too many pointless
>> conflicts). So, for projects that I control, I a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Micah Cowan wrote:
> This would
> end up doing the right thing if the locale is UTF-8 but the input string
> is in ISO-8859-1.
Er, if the locale is UTF-8 or similar and wide characters are using
native-order Unicode to represent their
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Haible wrote:
> Any volunteer wants to write a 'mbsfnmatch' function that works like fnmatch
> but supports invalid byte sequences?
(I've removed bug-tar from the Cc list but left everyone else; I hope
that's as it should be.)
Wget is in need o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Haible wrote:
> Colin Watson wrote:
>> Do you happen to know whether I was overdoing it by adding in #ifdefs
>> for SIGHUP, SIGINT, etc.? I decided better safe than sorry, but didn't
>> know whether there was some basic set of signals that Gnulib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
While attempting to compile sed from current CVS, I ran across the
following output from bootstrap.sh:
+ cc -DHAVE_CONFIG_H -I.. -I. -c getline.c
getline.c:26: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’
before ‘getline’
Line 26 is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Guy Rutenberg wrote:
> Since what version of GCC is the restricted keyword available? I've
> tried compiling the code with gcc ( 4.1.2) and it doesn't recognized
> this keyword. Compiling using gcc instead of g++ solved all compilation
> errors excep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Guy Rutenberg wrote:
> When trying to compile base64.c using g++ I got the following
> compilation problems:
Note that base64.c, .h are written in C, not C++. Trying to compile with
g++ makes almost as little sense as trying to compile it as Fortran
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Guy Rutenberg wrote:
> I'm using gcc 4.1.2 on Gentoo. It may well be
Missing the rest of that sentence. :)
> N.B. I'm not subscribed to this list, so please cc back to my email your
> reply.
>Where can I find an email archive of this list?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bruno Haible wrote:
> Micah Cowan wrote:
>> How best do I determine in my code whether I'm using gnulib's
>> getopt_long, or the system library (potentially glibc)'s? That is, I
>> want to know whether I ought to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
How best do I determine in my code whether I'm using gnulib's
getopt_long, or the system library (potentially glibc)'s? That is, I
want to know whether I ought to be passing in a char ** or a
char*const*, whilst avoiding warnings and the like.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
> According to Micah Cowan on 10/25/2007 10:13 AM:
>> +/* TRANSLATORS: Servname and ai_socktype are formal parameter names,
>> + and should not be translated. */
>> { EAI_SERVICE, N_("
---
ChangeLog |6 ++
lib/gai_strerror.c |2 ++
2 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 3ed561c..1fdf097 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2007-10-25 Micah Cowan <[EMAIL PROTECTED]>
+
+
>
> >
> > Most likely, yes. But where's the source to the boilerplate that
> > includes this magic? I used http://www.gnu.org/boilerplate.html,
> > which has the magic already expanded. I couldn't find the actual
> > source for that.
>
> Here's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bruno Haible wrote:
> Micah Cowan wrote:
>> --- a/users.txt
>> +++ b/users.txt
>> @@ -43,6 +43,7 @@ The following packages appear to be using gnulib and
>> gnulib-tool:
>>shishi http://git.sv.gnu.o
---
users.txt |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/users.txt b/users.txt
index c46edbc..69c44b5 100644
--- a/users.txt
+++ b/users.txt
@@ -43,6 +43,7 @@ The following packages appear to be using gnulib and
gnulib-tool:
shishi http://git.sv.gnu.org/g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Simon Josefsson wrote:
> Micah Cowan <[EMAIL PROTECTED]> writes:
>
>>> The second set of patches is against gnulib to remove most of the rules
>>> in coreutils, to avoid duplication. This removes some features from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Simon Josefsson wrote:
>> Sadly, old versions of gzip send the help/usage report to stderr, not
>> stdout, so ">/dev/null" alone does not discard it. (And grep wouldn't
>> see an "rsyncable", even if it were there.) Folding stderr into stdout
>> lo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Simon Josefsson wrote:
> Simon Josefsson <[EMAIL PROTECTED]> writes:
>
>> If we make maint.mk minimal, it would be excellent to make coreutils'
>> Makefile.maint do 'include maint.mk'. This was the idea all along.
>> I'll suggest patches for gnulib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I could've sworn the gnulib project page on Savannah had git cloning
information just a couple days ago
(https://savannah.gnu.org/projects/gnulib). At the moment, though, it
appears not to. Or maybe I was just thinking of the "Use git" page.
Interes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
H.Merijn Brand wrote:
> On Thu, 18 Oct 2007 05:50:42 -0600, Eric Blake <[EMAIL PROTECTED]> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> According to H.Merijn Brand on 10/18/2007 1:43 AM:
>>> Please convince the GNU world to add
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Paul Eggert wrote:
> Bruno Haible <[EMAIL PROTECTED]> writes:
>
>> Compilers such as Sun C++ really define NULL to 0
>> (in both C and C++ mode!), and misinterpret NULL in varargs and sizeof.
>
> The problem with varargs is one that has bitten me p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bruno Haible wrote:
> Hi,
>
> Micah Cowan asked:
>> If I've --import'ed md5, is there a means for me to specify in
>> configure.ac that it should not be included in certain circumstances?
>
> Depending on what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
If I've --import'ed md5, is there a means for me to specify in
configure.ac that it should not be included in certain circumstances?
I'm in the process of converting portions of Wget to gnulib. We had
GNU's MD5 code in there, but only used it when w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Bruno Haible wrote:
> Ben Pfaff wrote:
>> ISO C says that NULL can be defined as 0, without a cast to void
>> *, and it is always defined that way in C++.
>
> The latter statement is not true. ISO C++ 18.1.(3) says:
>
> "The macro NULL is an impl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
> I'm not sure how that works. Yes, my understanding is that libssl is a
> gnulib client, but then it seems like you should have been asking on the
> libssl list. I don't see wget listed in gnulib/users.txt; do we need to
> add an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
> According to Micah Cowan on 8/7/2007 12:07 PM:
>> Hello,
>
>> I have recently become the maintainer for GNU Wget, which uses autoconf
>> and havelib, but currently not automake.
>
>> The use of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Eric Blake wrote:
> We will probably start seeing reports like this more frequently as gcc 4.3 is
> adopted, especially since gnulib projects tend to prefer std=gnu99 when a gcc
> compiler is detected. Can anyone think of a way to detect broken sy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ralf Wildenhues wrote:
> The AS_IF of Autoconf 2.61 will cause all m4_require'd/AC_REQUIRE'd
> macros to be expanded outside of the conditional.
>
> Hope that helps.
It certainly does, thanks!
- --
Micah J. Cowan
Programmer, musician, typesetting
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
I have recently become the maintainer for GNU Wget, which uses autoconf
and havelib, but currently not automake.
The use of ./configure --with-libssl-prefix= has stopped
working; I did some investigating, and it appears that the following
co
42 matches
Mail list logo
