From: Siegmar Gross <siegmar.gross@informatik.hs-fulda.de>
To: gcc-dev <gcc@gcc.gnu.org>
Subject: Re: gcc-8-20180225: "go" breaks building OpenMP
Date: Fri, 09 Mar 2018 21:04:00 -0000 [thread overview]
Message-ID: <2acd7641-1ce2-a8b1-fa59-9418ba05d9c8@informatik.hs-fulda.de> (raw)
In-Reply-To: <877eql18xn.fsf@euler.schwinge.homeip.net>
Hi Thomas,
thank you very much for your help. That's exactly what I wanted.
I tried again and was successful.
Kind regards
Siegmar
Am 09.03.2018 um 17:59 schrieb Thomas Schwinge:
> Hi!
>
> On Fri, 9 Mar 2018 17:15:16 +0100, Siegmar Gross <siegmar.gross@informatik.hs-fulda.de> wrote:
>> [...]
>> configure: error: "libffi has not been ported to nvptx-unknown-none."
>> [...]
>
> Right, such things are not supported for a "--target=nvptx" compiler.
>
> But, if your desire is to just enable additional languages, without
> offloading support for them (which doesn't exist, as discussed in my
> other email), then the solution is to just specify them in
> "--enable-languages" for your "gcc-8.0.0_host_build" (host compiler) but
> not for your "gcc-8.0.0_build" (nvptx offloading compiler), keeping the
> latter at "--enable-languages=c,c++,fortran,lto".
>
> Specifically:
>
>>>> I used the following commands to build everything.
>>>>
>>>> setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/usr/local/cuda/lib64
>>>> setenv CUDA_INC_PATH /usr/local/cuda/include
>>>> setenv CUDA_LIB_PATH /usr/local/cuda/lib64
>>>> set path = ( ${path} /usr/local/cuda/bin )
>>>>
>>>> mkdir make_nvptx-tools
>>>> cd make_nvptx-tools
>>>> ../nvptx-tools/configure --prefix=/usr/local/gcc-8.0.0 \
>>>> |& tee log.configure
>>>> make |& tee log.make
>>>> make install |& tee log.make-install
>>>> cd ..
>>>>
>>>> mkdir gcc-8.0.0_build
>>>> cd gcc-8.0.0_build
>>>> ../gcc-8.0.0/configure --prefix=/usr/local/gcc-8.0.0 \
>>>> --target=nvptx-none \
>>>> --enable-as-accelerator-for=x86_64-pc-linux-gnu \
>>>> --with-build-time-tools=/usr/local/gcc-8.0.0/nvptx-none/bin \
>>>> --disable-sjlj-exceptions \
>>>> --with-newlib \
>>>> --enable-newlib-io-long-long \
>>>> --enable-languages=c,c++,objc,obj-c++,fortran,go,lto \
>
> Continue to use "--enable-languages=c,c++,fortran,lto" here.
>
>>>> |& tee log.configure
>>>> make -j 6 |& tee log.make
>>>> make -j 6 install |& tee log.make-install
>>>>
>>>> mkdir ../gcc-8.0.0_host_build
>>>> cd ../gcc-8.0.0_host_build
>>>> ../gcc-8.0.0/configure --prefix=/usr/local/gcc-8.0.0 \
>>>> --build=x86_64-pc-linux-gnu \
>>>> --host=x86_64-pc-linux-gnu \
>>>> --target=x86_64-pc-linux-gnu \
>>>> --enable-offload-targets=nvptx-none=/usr/local/gcc-8.0.0/bin \
>>>> --with-cuda-driver=/usr/local/cuda/ \
>>>> --enable-languages=c,c++,objc,obj-c++,fortran,go,lto \
>
> That should work fine.
>
>>>> --enable-nls \
>>>> --enable-threads=posix \
>>>> --with-gmp-lib=/usr/local/lib64 \
>>>> --with-gmp-include=/usr/local/include \
>>>> --with-mpfr-lib=/usr/local/lib64 \
>>>> --with-mpfr-include=/usr/local/include \
>>>> --with-mpc-lib=/usr/local/lib64 \
>>>> --with-mpc-include=/usr/local/include \
>>>> --with-isl-lib=/usr/local/lib64 \
>>>> --with-isl-include=/usr/local/include \
>>>> |& tee log.configure
>>>> make -j 6 |& tee log.make
>>>> make -j 6 install |& tee log.make-install
>
>
> GrüÃe
> Thomas
next prev parent reply other threads:[~2018-03-09 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 6:56 Siegmar Gross
2018-03-09 9:35 ` Jakub Jelinek
2018-03-09 8:32 ` Siegmar Gross
2018-03-09 16:15 ` Thomas Schwinge
2018-03-09 16:28 ` Siegmar Gross
2018-03-09 13:38 ` Ian Lance Taylor
2018-03-09 16:15 ` Siegmar Gross
2018-03-09 16:59 ` Thomas Schwinge
2018-03-09 21:04 ` Siegmar Gross [this message]
2018-03-09 18:35 ` Jakub Jelinek
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=2acd7641-1ce2-a8b1-fa59-9418ba05d9c8@informatik.hs-fulda.de \
--to=siegmar.gross@informatik.hs-fulda.de \
--cc=gcc@gcc.gnu.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).