public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Missing `alloca` symbol - help?
Date: Tue, 16 Oct 2018 02:26:00 -0000	[thread overview]
Message-ID: <771d665d-b7bd-18b8-44b3-59441d3fbc21@cornell.edu> (raw)
In-Reply-To: <CAGnQBS2mTCZvMuALwY0PVkZaOo3AvjCpJkHXSfzfih9vEvfo7Q@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1252 bytes --]

On 10/15/2018 9:20 PM, Murray Christopherson wrote:
> I'm not certain this is a problem with Cygwin, but I am unable to find any
> issue by looking over the project in question, so I thought I'd ask. Is
> this an obvious bug, either in Cygwin or the project itself?
> [...]
> # Observed result
> Fails to install. Particularly, the error output makes multiple mentions of
> `undefined reference to `alloca'` during linking (full error log at
> https://github.com/theacodes/cmarkgfm/issues/13).
> 
> # Notes
> As far as I can tell, `alloca` is a standard Unix function (though
> deprecated). Also, in Cygwin, `/usr/includes/alloca/h` exists, suggesting
> the function _should_ exist to be linked without further packages?

alloca is defined in /usr/include/alloca.h as a macro expanding to 
__builtin_alloca.  The linking error you report suggests that there's a missing 
"#include <alloca.h>" in the source code that's being compiled.  This is also 
confirmed by the gcc warnings in your full log.

Ken
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

      reply	other threads:[~2018-10-16  2:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16  1:20 Murray Christopherson
2018-10-16  2:26 ` Ken Brown [this message]

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=771d665d-b7bd-18b8-44b3-59441d3fbc21@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@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).