From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Christopher Li <sparse@chrisli.org>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH 07/10] Add support for multiarch system header files
Date: Mon, 06 Oct 2014 11:31:39 +0100 [thread overview]
Message-ID: <54326F8B.1050201@ramsay1.demon.co.uk> (raw)
In-Reply-To: <CANeU7QnuZucjgq2b972ZxBi0e1TZpz=mMjo6SCRvk5mngXaETg@mail.gmail.com>
On 06/10/14 00:33, Christopher Li wrote:
> On Tue, Aug 5, 2014 at 2:39 AM, Ramsay Jones <ramsay@ramsay1.demon.co.uk> wrote:
>>
>> Signed-off-by: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
>
> May I have a more descriptive change log why is multiarch option useful?
>
>> @@ -36,6 +36,9 @@ HAVE_LLVM:=$(shell $(LLVM_CONFIG) --version >/dev/null 2>&1 && echo 'yes')
>> GCC_BASE = $(shell $(CC) --print-file-name=)
>> BASIC_CFLAGS = -DGCC_BASE=\"$(GCC_BASE)\"
>>
>> +MULTIARCH_TRIPLET = $(shell $(CC) -print-multiarch 2>/dev/null)
>> +BASIC_CFLAGS += -DMULTIARCH_TRIPLET=\"$(MULTIARCH_TRIPLET)\"
>
> My gcc(4.8, FC20) does not support "-print-multiarch".
Yep, same is true for cygwin.
> So the patch need to handle that case.
> As far as I can tell, this patch is not ready for empty MULTIARCH_TRIPLET.
Hmm, works for me! Could you describe the failure you are seeing.
>
>> + if (multiarch_dir && *multiarch_dir) {
>> + add_pre_buffer("#add_system \"/usr/include/%s\"\n", multiarch_dir);
>> + add_pre_buffer("#add_system \"/usr/local/include/%s\"\n", multiarch_dir);
>> + }
>
> Not sure empty multiarch_dir works here.
Again, it works for me. :-D
ATB,
Ramsay Jones
next prev parent reply other threads:[~2014-10-06 10:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 18:39 [PATCH 07/10] Add support for multiarch system header files Ramsay Jones
2014-10-05 23:33 ` Christopher Li
2014-10-06 10:31 ` Ramsay Jones [this message]
2014-10-07 3:55 ` Christopher Li
2014-10-07 10:20 ` Ramsay Jones
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=54326F8B.1050201@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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