emacs-bug-tracker
[Top][All Lists]
Advanced

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

[debbugs-tracker] bug#26123: closed (guile-2.2.0: AI_ADDRCONFIG)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#26123: closed (guile-2.2.0: AI_ADDRCONFIG)
Date: Wed, 19 Apr 2017 14:51:02 +0000

Your message dated Wed, 19 Apr 2017 16:50:18 +0200
with message-id <address@hidden>
and subject line Re: bug#26123: guile-2.2.0: AI_ADDRCONFIG
has caused the debbugs.gnu.org bug report #26123,
regarding guile-2.2.0: AI_ADDRCONFIG
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
26123: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=26123
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: guile-2.2.0: AI_ADDRCONFIG Date: Thu, 16 Mar 2017 10:29:18 +0100
Hi!

When compiling guile-2.2.0 on NetBSD_7.99.65/amd64, I see:


  SNARF  net_db.doc
net_db.c:468:***Missing or erroneous `#define FUNC_NAME s_AI_ADDRCONFIG);'
net_db.c:488:***Missing or erroneous #undef for AI_ADDRCONFIG);:

Compilation continues even though this looks like an error.
 Thomas



--- End Message ---
--- Begin Message --- Subject: Re: bug#26123: guile-2.2.0: AI_ADDRCONFIG Date: Wed, 19 Apr 2017 16:50:18 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
On Fri 17 Mar 2017 14:11, <address@hidden> writes:

> ---- Thomas Klausner <address@hidden> wrote: 
>> 
>>   SNARF  net_db.doc
>> net_db.c:468:***Missing or erroneous `#define FUNC_NAME s_AI_ADDRCONFIG);'
>> net_db.c:488:***Missing or erroneous #undef for AI_ADDRCONFIG);:
>> 
>> Compilation continues even though this looks like an error.
>
> Yeah,  while annoying, this is harmless.
>
> The proper fix in my opinion is to limit the regular expression on line
> 28 in libguile/guile-func-name-check to only match function definition
> macros.  Currently, it matches other macros that define things other
> than functions, and so erroneously looks for a function body.
>
> For example, adding a space like /^SCM_DEFINE / would probably be 
> appropriate.  However, that would prevent it from matching any other function 
> defining macros, if they exist.

Good idea, done.  Thanks :)

ANdy


--- End Message ---

reply via email to

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