On Sun, 2019-09-01 at 18:57 -0400, Dmitry Goncharov via Bug reports and
discussion for GNU make wrote:
> This patch fixes a compilation error when time.h does not get
> indirectly included.
>
> regards, Dmitry
>
> diff --git a/src/file.c b/src/file.c
> index c20fcf8..f58e855 100644
> ---
Good morning.
sum_up_to_nul reads 4 bytes starting from the passed string 'p'.
'p' can have fewer than 4 bytes. Usually there more allocated space
after 'p', which prevents this reading from manifesting itself. This
reading manifests itself visibly when 'p' points to the end of the
allocated
On Wed, 2019-08-28 at 14:01 +, Mike Gran wrote:
> The '--enable-load' configure option will cause warnings since
> --export-dynamic is not supported for PE+ targets.
I'm not sure what a PE+ target is, but as long as running configure
with no special flags correctly detects the situation and
On Fri, 2019-08-30 at 00:38 +0900, Kiyoshi KANAZAWA wrote:
> But, there are also N/A:
> functions/guile . N/A
> misc/close_stdout ... N/A
> vms/library . N/A
>
> I do not know
On Mon, 2019-09-02 at 15:35 -0700, Paul Eggert wrote:
> We need to be portable to C99 and later. C89 and later if the
> programmer wants to and if it's not too much work. K C is almost
> surely not worth the effort.
I generally attempt to keep GNU make more portable than most GNU
projects as I
Dennis Clarke wrote:
I am wondering what is
the actual dialect to adher to.
We need to be portable to C99 and later. C89 and later if the programmer wants
to and if it's not too much work. K C is almost surely not worth the effort.
OpenSSL is a different project from OpenSSL and uses
On 9/2/19 4:12 PM, Paul Eggert wrote:
Dennis Clarke wrote:
On 9/2/19 12:28 PM, Paul Smith wrote:
On Mon, 2019-09-02 at 18:20 +0200, Robert Pluim wrote:
is this intended to build on macOS using clang, or using gcc only?
It should work with any C compiler that supports the C89 standard.
I
Dennis Clarke wrote:
On 9/2/19 12:28 PM, Paul Smith wrote:
On Mon, 2019-09-02 at 18:20 +0200, Robert Pluim wrote:
is this intended to build on macOS using clang, or using gcc only?
It should work with any C compiler that supports the C89 standard.
I was looking for this sort of answer
On 9/2/19 12:28 PM, Paul Smith wrote:
On Mon, 2019-09-02 at 18:20 +0200, Robert Pluim wrote:
is this intended to build on macOS using clang, or using gcc only?
It should work with any C compiler that supports the C89 standard.
I was looking for this sort of answer before. I have been
On Mon, 2019-09-02 at 18:20 +0200, Robert Pluim wrote:
> is this intended to build on macOS using clang, or using gcc only?
It should work with any C compiler that supports the C89 standard.
> $ gcc --version
> Configured with: --prefix=/Library/Developer/CommandLineTools/usr
>
> On Mon, 26 Aug 2019 09:00:13 -0400, Paul Smith said:
Paul>
Paul> GNU make is a tool which controls the generation of executables
and
Paul> other non-source files of a program from the program's
On Sun, 2019-09-01 at 16:01 -0400, Dmitry Goncharov via Bug reports and
discussion for GNU make wrote:
> $ echo 'all: ; @echo $(wildcard hello*/)' > /tmp/1.mk
> $ ./make -f /tmp/1.mk
> Segmentation Fault
>
> A patch was provided here
>
On Sun, 2019-09-01 at 15:33 -0400, Dmitry Goncharov via Bug reports and
discussion for GNU make wrote:
> This patch executes posix_spawnp at configuration time and then
> disables posix_spawn if posix_spawn returns 0 on an attempt to exec a
> missing file.
> This solution won't work for cross
13 matches
Mail list logo
