From: Yann Diorcet <diorcet.yann@gmail.com>
To: Cody P Schafer <dev@codyps.com>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
crossgcc <crossgcc@sourceware.org>
Subject: Re: [PATCH 1 of 1] cc/gcc: Split gcc configurations and functions from cc ones
Date: Tue, 10 Dec 2013 09:26:00 -0000 [thread overview]
Message-ID: <CACPcEYn_1JeamKsScEBnv2xvfXKh_MDpqEMh4MtwotP6Mv3qiw@mail.gmail.com> (raw)
In-Reply-To: <52A63E9C.40909@codyps.com>
Hi,
2013/12/9 Cody P Schafer <dev@codyps.com>:
>
>> --- a/scripts/showSamples.sh Sat Nov 16 18:14:45 2013 +0100
>> +++ b/scripts/showSamples.sh Mon Dec 02 21:51:09 2013 +0100
>> @@ -76,7 +76,7 @@
>> [ -z "${CT_LIBELF}" -a -z "${CT_LIBELF_TARGET}" ] || printf
>> " libelf-%s" "${CT_LIBELF_VERSION}"
>> [ -z "${complibs}" ] || printf "\n"
>> printf " %-*s : %s\n" ${width} "binutils"
>> "binutils-${CT_BINUTILS_VERSION}"
>> - printf " %-*s : %s" ${width} "C compiler"
>> "${CT_CC}-${CT_CC_VERSION} (C"
>> + printf " %-*s : %s" ${width} "C compiler"
>> "${CT_CC}-${CT_CC_GCC_VERSION} (C"
>> [ "${CT_CC_LANG_CXX}" = "y" ] && printf ",C++"
>> [ "${CT_CC_LANG_FORTRAN}" = "y" ] && printf ",Fortran"
>> [ "${CT_CC_LANG_JAVA}" = "y" ] && printf ",Java"
>> @@ -121,7 +121,7 @@
>> fi
>> printf "| ${CT_BINUTILS_VERSION} "
>> printf "| ''${CT_CC}'' "
>> - printf "| ${CT_CC_VERSION} "
>> + printf "| ${CT_CC_GCC_VERSION} "
>> printf "| ''${CT_LIBC}'' |"
>> if [ "${CT_LIBC}" != "none" ]; then
>> printf " ${CT_LIBC_VERSION} "
>>
>> --
>
>
> From this it looks like
> - there isn't a way to get the NAME-VERSION of the configured C compiler
There is maybe more that C compiler selected btw.
> - You'll be using the GCC version number even if CT_CC isn't gcc.
>
Indeed not clean. How we can improve that?
--
Diorcet Yann
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2013-12-10 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 20:52 [PATCH 0 of 1] Split gcc from cc Yann Diorcet
2013-12-02 20:54 ` [PATCH 1 of 1] cc/gcc: Split gcc configurations and functions from cc ones Yann Diorcet
2013-12-09 19:05 ` Ray Donnelly
2013-12-09 22:06 ` Cody P Schafer
2013-12-10 9:26 ` Yann Diorcet [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-12-11 20:42 [PATCH 0 of 1] Split gcc from cc Yann Diorcet
2013-12-11 20:42 ` [PATCH 1 of 1] cc/gcc: Split gcc configurations and functions from cc ones Yann Diorcet
2013-12-12 22:07 ` Yann E. MORIN
2013-07-09 22:58 [PATCH 0 of 1] Split gcc from cc Yann Diorcet
2013-07-09 22:58 ` [PATCH 1 of 1] cc/gcc: Split gcc configurations and functions from cc ones Yann Diorcet
2013-07-10 6:16 ` Daniel Price
2013-07-10 7:43 ` Diorcet Yann
2013-07-10 8:50 ` Martin Guy
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=CACPcEYn_1JeamKsScEBnv2xvfXKh_MDpqEMh4MtwotP6Mv3qiw@mail.gmail.com \
--to=diorcet.yann@gmail.com \
--cc=crossgcc@sourceware.org \
--cc=dev@codyps.com \
--cc=yann.morin.1998@free.fr \
/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).