public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug libelf/26708] lcc compiler can't build elfutils because of nested functions
Date: Tue, 06 Oct 2020 12:34:26 +0000	[thread overview]
Message-ID: <bug-26708-10460-JevPyYLINh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26708-10460@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26708

--- Comment #2 from Mark Wielaard <mark at klomp dot org> ---
Note that there should be a configure test to check that your compiler has all
capabilities to build elfutils:

# We use -std=gnu99 but have explicit checks for some language constructs
# and GNU extensions since some compilers claim GNU99 support, but don't
# really support all language extensions. In particular we need
# Mixed Declarations and Code
# https://gcc.gnu.org/onlinedocs/gcc/Mixed-Declarations.html
# Nested Functions
# https://gcc.gnu.org/onlinedocs/gcc/Nested-Functions.html
# Arrays of Variable Length
# https://gcc.gnu.org/onlinedocs/gcc/Variable-Length.html

Normally if your compiler doesn't support those language constructs the
"Checking for for gcc with GNU99 support..." test should fail. If it doesn't in
your case we might have to tighten up the configure check.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-10-06 12:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-06  8:10 [Bug libelf/26708] New: " alexander at mezon dot ru
2020-10-06 10:49 ` [Bug libelf/26708] " mark at klomp dot org
2020-10-06 12:34 ` mark at klomp dot org [this message]
2020-10-06 12:39 ` alexander at mezon dot ru
2020-10-06 18:52 ` mark at klomp dot org

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=bug-26708-10460-JevPyYLINh@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=elfutils-devel@sourceware.org \
    /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).