public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Navin P <navinp0304@gmail.com>, elfutils-devel@sourceware.org
Subject: Re: Indent and formatting of elfutils
Date: Mon, 09 Nov 2020 18:21:12 +0100	[thread overview]
Message-ID: <7f28f67458fd28068914bb9cc18bae1cb34ab8a7.camel@klomp.org> (raw)
In-Reply-To: <CALO2Tq+XfakhssOC9yf=V8Krow5Lc1JBDhT=tRg+bhx5XU7HcA@mail.gmail.com>

Hi Navin,

On Mon, 2020-11-09 at 22:03 +0530, Navin P via Elfutils-devel wrote:
>    I'm trying to compile elfutils with clang.
>    I haven't written new code but moved code around. In this process source
> code formatting is lost when I moved couple of functions.
> 
> Do you have any indent settings or clang-format or any auto settings ?

Unfortunately (last time we checked) clang didn't support enough of the
gnu99 standard to build elfutils. See the following comment for our
configure check:

# 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

You might want to poke the clang developers to make sure they support
those extended GNU C language features. As soon as they do, the
configure check should succeed and you should be able to use the clang
tools to build stuff.

Cheers,

Mark

      reply	other threads:[~2020-11-09 17:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 16:33 Navin P
2020-11-09 17:21 ` Mark Wielaard [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=7f28f67458fd28068914bb9cc18bae1cb34ab8a7.camel@klomp.org \
    --to=mark@klomp.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=navinp0304@gmail.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).