Sure, it is not standard, but that's not just capriciousness or
laziness: the whole idea of gnulib is to share files *at the source
level*. If people are not comfortable with cvs checkouts (and autoconf
and ...), they shouldn't be using it.
Indeed, but having gnulib only in the cvs form has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Patrice Dumas [EMAIL PROTECTED] writes:
Simon Josefsson [EMAIL PROTECTED] wrote:
I found it helped to attack the problem one module at a time,
carefully considering the details. Exactly which modules do you need
which are under the GPL in
Hi,
On mingw32, mbrtowc.m4 detects that mbrtowc() exists, leading to
link errors. Actually, mbrtowc() does not exist on this system,
it's only declared in wchar.h but not actually implemented under
this name. config.log shows this:
configure:26506: checking whether mbrtowc and mbstate_t are
Hello Bruno,
On Mon, Jul 04, 2005 at 01:18:25PM +0200, Bruno Haible wrote:
On mingw32, mbrtowc.m4 detects that mbrtowc() exists, leading to
link errors. Actually, mbrtowc() does not exist on this system,
it's only declared in wchar.h but not actually implemented under
this name.
why cannot
[lessergnulib]
I remember this discussion (somewhat), but I was and am a bit puzzled.
Is the only purpose is to make the functionality available under the
LGPL?
Because it does not seem good, or necessary, for the same routines to
exist in two different forms. It does not increase freedom,
Patrice Dumas [EMAIL PROTECTED] writes:
alloca malloc realloc strtod atexit dup2 getcwd getpagesize memmove memset
strerror regex
These are mostly equivalent to existing and widely used LGPLed code,
so I'd say they should be LGPLed.
I would say the one exception is getcwd, where the code to
Patrice Dumas [EMAIL PROTECTED] writes:
Imagine someone doing coding at 6 places (5 labs and a home)
No, let's not imagine that. (You should be simplifying your life! :-)
Seriously, though, I regularly do something like this:
* Check out a the latest Tar CVS.
* Run ./bootstrap.
This
On Mon, Jul 04, 2005 at 05:32:50PM -0400, Karl Berry wrote:
From the point of view of people adopting gnulib (which is what Hello is
all about, basically), I think it is better to show and separate the
pieces than provide one magical humongous script that does everything.
I agree. It's
Stepan Kasal [EMAIL PROTECTED] writes:
A copy of the macro is attached below; does it work for you?
Thanks for suggesting that. Yes, if the current Autoconf macro works
for Bruno, we should simply use a copy of it in gnulib.
___
bug-gnulib mailing
Jim Meyering [EMAIL PROTECTED] writes:
The implementation uses a struct declaration whose name includes the
expansion of __LINE__, so there is a small chance that two uses of
verify_decl from different files will end up colliding
I thought about this problem for a bit and came up
10 matches
Mail list logo
