public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] znc 1.6.0
Date: Thu, 23 Jul 2015 13:24:00 -0000	[thread overview]
Message-ID: <55B0EB09.50402@cornell.edu> (raw)
In-Reply-To: <55B03C16.1060009@asokolov.org>

On 7/22/2015 8:57 PM, Alexey Sokolov wrote:
> 23.07.2015 00:03, David Stacey :
>>      cygport ./znc.cygport prep compile
>>
>> Nothing out of the ordinary there. This gives the following error:
>>
>>      configure.ac:255: Something is trying to use the C compiler. Since
>> this is a C++ project, this should not happen!
>>      autom4te-2.69: /usr/bin/m4 failed with exit status: 1
>>
> Hm, I'm not sure why autoreconf would do this (works for me though)

I can confirm Dave's experience.  It's strange that you don't get the 
same failure.  The error message is generated by AC_PROG_CC, which is 
redefined at the beginning of configure.ac.

Ken

  parent reply	other threads:[~2015-07-23 13:24 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-18 15:48 Alexey Sokolov
     [not found] ` <55AABF89.7030306@asokolov.org>
     [not found]   ` <55AADC2C.1070802@asokolov.org>
2015-07-19  8:24     ` Alexey Sokolov
2015-07-19 10:03       ` Corinna Vinschen
2015-07-19 13:24         ` Alexey Sokolov
2015-07-19 16:42           ` Achim Gratz
     [not found]             ` <55ABEC90.3040106@asokolov.org>
2015-07-19 18:30               ` Alexey Sokolov
2015-07-19 19:11                 ` Achim Gratz
2015-07-19 19:30                   ` Marco Atzeri
2015-07-19 19:36                     ` Achim Gratz
2015-07-19 19:54                   ` Alexey Sokolov
2015-07-20  7:44                     ` Corinna Vinschen
2015-07-20 18:58                       ` Alexey Sokolov
2015-07-20 20:46                         ` Alexey Sokolov
2015-07-21  7:12                         ` Corinna Vinschen
2015-07-21 20:37                           ` Alexey Sokolov
2015-07-21 23:25                           ` David Stacey
2015-07-21 23:32                             ` Alexey Sokolov
2015-07-21 23:53                               ` Alexey Sokolov
2015-07-22 23:03                                 ` David Stacey
2015-07-22 23:29                                   ` David Stacey
2015-07-23  0:58                                   ` Alexey Sokolov
2015-07-23  5:23                                     ` Achim Gratz
2015-07-23 20:50                                       ` Alexey Sokolov
2015-07-23 13:24                                     ` Ken Brown [this message]
2015-07-23 20:50                                       ` Alexey Sokolov
2015-07-23 21:04                                         ` Alexey Sokolov
2015-07-23 21:28                                           ` Ken Brown
2015-07-24  6:42                                             ` Alexey Sokolov
2015-07-22  8:07                               ` Corinna Vinschen
2015-07-22 21:40                                 ` Alexey Sokolov
2015-07-30 22:34                                   ` Alexey Sokolov
2015-08-03  7:59                                     ` Corinna Vinschen
2015-08-03  9:02                                       ` Alexey Sokolov
2015-08-03  9:20                                         ` Corinna Vinschen
2015-07-24 19:14                                 ` Alexey Sokolov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55B0EB09.50402@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).