From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Zhenqiang Chen <zhenqiang.chen@linaro.org>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: [PATCH] cc/gcc: Add Fortran support for Baremetal build
Date: Thu, 12 Dec 2013 22:19:00 -0000 [thread overview]
Message-ID: <20131212221902.GC1639@free.fr> (raw)
In-Reply-To: <CACgzC7D5HCVS-qX=ydcQphNFH=VGgJzTdZWQWaLKAv-CdE8crA@mail.gmail.com>
Zhenqiang, All,
On 2013-11-20 17:37 +0800, Zhenqiang Chen spake thusly:
> # HG changeset patch
> # User Zhenqiang Chen <zhenqiang.chen@linaro.org>
> # Date 1384843442 -28800
> # Node ID 3ba918b278a4b1553a49819d5b2feecdea822697
> # Parent 7e569a9cb5fd3ab591bb307328b947a5b7312cba
> cc/gcc: Add Fortran support for Baremetal build
>
> Signed-off-by: Zhenqiang Chen <zhenqiang.chen@linaro.org>
[--SNIP--]
> diff -r 7e569a9cb5fd -r 3ba918b278a4 scripts/build/cc/gcc.sh
> --- a/scripts/build/cc/gcc.sh Sat Nov 16 18:14:45 2013 +0100
> +++ b/scripts/build/cc/gcc.sh Tue Nov 19 14:44:02 2013 +0800
> @@ -164,6 +164,7 @@
> # lang_list : the list of languages to build :
> string : (empty)
> # build_libgcc : build libgcc or not :
> bool : no
> # build_libstdcxx : build libstdc++ or not :
> bool : no
> +# build_libgfortran : build libgfortran or not :
> bool : no
> # build_staticlinked : build statically linked or not :
> bool : no
> # build_manuals : whether to build manuals or not :
> bool : no
> # cflags : cflags to use :
> string : (empty)
Woops... This patch is highly broken. I'll fix locally, no need to resend.
> @@ -173,6 +174,7 @@
> local mode
> local build_libgcc=no
> local build_libstdcxx=no
> + local build_libgfortran=no
> local build_staticlinked=no
> local build_manuals=no
> local host
> @@ -457,6 +459,12 @@
> core_targets+=( target-libstdc++-v3 )
> fi
>
> + if [ "${build_libgfortran}" = "yes" \
> + -a "${CT_CC_LANG_FORTRAN}" = "y" \
> + ]; then
> + core_targets+=( target-libgfortran )
> + fi
> +
> CT_DoLog EXTRA "Building gcc"
> CT_DoExecLog ALL make ${JOBSFLAGS} "${core_targets[@]/#/all-}"
>
> @@ -521,6 +529,7 @@
> build_final_opts+=( "mode=baremetal" )
> build_final_opts+=( "build_libgcc=yes" )
> build_final_opts+=( "build_libstdcxx=yes" )
> + build_final_opts+=( "build_libgfortran=yes" )
> if [ "${CT_STATIC_TOOLCHAIN}" = "y" ]; then
> build_final_opts+=( "build_staticlinked=yes" )
> fi
> @@ -557,6 +566,7 @@
> final_opts+=( "mode=baremetal" )
> final_opts+=( "build_libgcc=yes" )
> final_opts+=( "build_libstdcxx=yes" )
> + final_opts+=( "build_libgfortran=yes" )
> if [ "${CT_STATIC_TOOLCHAIN}" = "y" ]; then
> final_opts+=( "build_staticlinked=yes" )
> fi
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2013-12-12 22:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 9:37 Zhenqiang Chen
2013-12-12 22:19 ` Yann E. MORIN [this message]
2013-12-12 22:32 ` Yann E. MORIN
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=20131212221902.GC1639@free.fr \
--to=yann.morin.1998@free.fr \
--cc=crossgcc@sourceware.org \
--cc=zhenqiang.chen@linaro.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).