From: Olaf Hering <olaf@aepfle.de>
To: Wei Liu <wei.liu2@citrix.com>
Cc: Minios-devel <minios-devel@lists.xenproject.org>,
"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
xen-devel@lists.xen.org, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH] mini-os: link to libgcc.a to fix build with gcc7
Date: Fri, 30 Jun 2017 19:01:36 +0200 [thread overview]
Message-ID: <20170630170136.GA18914@aepfle.de> (raw)
In-Reply-To: <20170630165819.GA18537@aepfle.de>
[-- Attachment #1.1: Type: text/plain, Size: 583 bytes --]
On Fri, Jun 30, Olaf Hering wrote:
> On Fri, Jun 30, Wei Liu wrote:
>
> > On second thought I don't think we want to make this worse. So the
> > change in this patch should be conditional on gcc.
>
> How whould I check for gcc in the Makefile?
> In xen.git I see a conditional for clang. I dont have a clang at hand,
> perhaps it knows about "-print-libgcc-file-name"?
Mine works fine:
$ gcc -print-libgcc-file-name
/usr/lib64/gcc/x86_64-suse-linux/7/libgcc.a
$ clang-3.8 -print-libgcc-file-name
/usr/bin/../lib64/gcc/x86_64-suse-linux/7/libgcc.a
Olaf
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2017-06-30 17:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 13:28 [PATCH] mini-os: link to libgcc.a to fix build with gcc7 Olaf Hering
2017-06-30 14:41 ` Wei Liu
2017-06-30 14:48 ` Roger Pau Monné
2017-06-30 14:50 ` Wei Liu
2017-06-30 14:56 ` Roger Pau Monné
2017-06-30 15:13 ` Wei Liu
2017-06-30 16:58 ` Olaf Hering
2017-06-30 17:01 ` Olaf Hering [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=20170630170136.GA18914@aepfle.de \
--to=olaf@aepfle.de \
--cc=minios-devel@lists.xenproject.org \
--cc=roger.pau@citrix.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.