Jim Meyering <[EMAIL PROTECTED]> writes:
> That looks fine to me.
OK, I installed it into gnulib.
Paul Eggert <[EMAIL PROTECTED]> wrote:
> How about the following patch instead? It seems a bit more
> straightforward. However, I don't fully understand the problem so I
> may well have gotten it wrong.
>
> 2006-12-11 Paul Eggert <[EMAIL PROTECTED]>
>
> * m4/openat.m4 (gl_FUNC_OPENAT): Do
Arkadiusz Miskiewicz <[EMAIL PROTECTED]> writes:
> Please take a look at thread:
> http://lists.pld-linux.org/mailman/pipermail/pld-devel-en/2006-December/018341.html
>
> The problem is that coreutils uses own internal copies
> of openat() and fchmodat() even if glibc already provides
> these func
Bruno Haible wrote:
> Lorenzo Bettini wrote:
>> I've just started using gnulib, and I have a doubt.
>> I've imported strdup and I'm using it in a C++ program.
>>
>> Now should I import strdup.h in the C++ program simply like this
>>
>> #include "strdup.h"
>>
>> Or should I wrap it as follows?
>>
>>
Paul Eggert wrote:
> for it to be useful won't we
> also need to sprinkle $(NO_CXX) throughout the descriptions of all
> modules that are not compilable with g++?
Yes. This is easy to do. I imagine Simon's buildbot will give us the list
of modules for which it is necessary.
So far, I put each suc
Ralf Wildenhues wrote:
> > ! for module in `join "$tmp"/modules1 "$tmp"/modules2`; do
>
> I'm pretty sure you want `LC_ALL=C join' instead here.
Yes. Good catch. Thanks.
--- gnulib-tool 11 Dec 2006 12:41:09 - 1.200
+++ gnulib-tool 11 Dec 2006 18:19:59 - 1.201
@@ -2189,7 +2189
Lorenzo Bettini wrote:
> I've just started using gnulib, and I have a doubt.
> I've imported strdup and I'm using it in a C++ program.
>
> Now should I import strdup.h in the C++ program simply like this
>
> #include "strdup.h"
>
> Or should I wrap it as follows?
>
> extern "C" {
> #include "st
Bruno Haible <[EMAIL PROTECTED]> writes:
> Objections?
I have no objections to this module, but for it to be useful won't we
also need to sprinkle $(NO_CXX) throughout the descriptions of all
modules that are not compilable with g++? How would that work?
Hi,
We've seen that it can be useful, for typechecking purposes, to be able
to compile a whole package with a C++ compiler. But some parts, such as
the regex module, are written in C, and too many code changes would be needed
to make them compile in C++ mode.
This module allows to group such modu
Hello Bruno,
* Bruno Haible wrote on Mon, Dec 11, 2006 at 04:20:02PM CET:
> ! for module in `join "$tmp"/modules1 "$tmp"/modules2`; do
I'm pretty sure you want `LC_ALL=C join' instead here.
Cheers,
Ralf
Karl Berry wrote on 2006-11-15:
> Would it be reasonable/possible to have gnulib-tool output only the
> top-level #includes?
Implemented. Thanks for bringing this up.
2006-12-10 Bruno Haible <[EMAIL PROTECTED]>
* gnulib-tool (func_import): Show the include files only for those
11 matches
Mail list logo
