emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MS-Windows build using Posix configury


From: Paul Eggert
Subject: Re: MS-Windows build using Posix configury
Date: Thu, 16 May 2013 00:16:29 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6

On 05/15/2013 11:56 PM, Eli Zaretskii wrote:

> Do you also feel that some minor change
> in qset-acl.c, to cause the compilation fall back on chmod_or_fchmod,
> is not justified?  That would allow to compile that file.

If I understand you correctly, there's no need to compile the file,
as its function is never called.  So I'd just omit it from
nt/gnulib.mk; that's simpler.

> And another question: what is the difference between the files
> mentioned in libgnu_a_SOURCES and those in EXTRA_libgnu_a_SOURCES?
> Like here:
> 
>   ## begin gnulib module qacl
> 
>   libgnu_a_SOURCES += acl-errno-valid.c file-has-acl.c qcopy-acl.c
> 
>   EXTRA_DIST += acl-internal.h acl.h acl_entries.c
> 
>   EXTRA_libgnu_a_SOURCES += acl_entries.c

There's a call AC_REPLACE_FUNCS([acl_entries]) in gl_FUNC_ACL,
which means the autoconf machinery decides whether to compile
acl_entries.c based on whether the system already has an acl_entries.
The functions acl_errno_valid, file_has_acl, and qcopy_acl are
not like that: they're meant to be compiled no matter what,
so one can simply tell Automake about them directly, using
libgnu_a_SOURCES.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]