public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/64635] darwin produces libgomp-plugin-host_nonshm.1.dylib but tries to load libgomp-plugin-host_nonshm.so.1
Date: Mon, 19 Jan 2015 15:47:00 -0000	[thread overview]
Message-ID: <bug-64635-4-3QcLcA1B4k@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64635-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64635

--- Comment #16 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> > With the attached patch at https://gcc.gnu.org/bugzilla/attachment.cgi?id=34469
> > and the patch at https://gcc.gnu.org/ml/gcc-patches/2015-01/msg01479.html,
> > I get ...
>
> I have found the origin of the problem: I am testing gfortran with
> the additional options '-g -flto', apparently this propagates
> to libgomp.oacc-fortran (I did not check why). Could someone test
> libgomp.oacc-fortran with these options on a linux platform?

I have opened pr64672 for that.


  parent reply	other threads:[~2015-01-19 15:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-16 19:13 [Bug libgomp/64635] New: " howarth at bromo dot med.uc.edu
2015-01-17  1:37 ` [Bug libgomp/64635] " howarth at bromo dot med.uc.edu
2015-01-17  2:05 ` howarth at bromo dot med.uc.edu
2015-01-17 18:17 ` howarth at bromo dot med.uc.edu
2015-01-17 20:00 ` jakub at gcc dot gnu.org
2015-01-18  1:18 ` howarth at bromo dot med.uc.edu
2015-01-18  9:35 ` iains at gcc dot gnu.org
2015-01-18  9:39 ` iains at gcc dot gnu.org
2015-01-18 18:18 ` dominiq at lps dot ens.fr
2015-01-18 21:30 ` howarth at bromo dot med.uc.edu
2015-01-18 21:38 ` howarth at bromo dot med.uc.edu
2015-01-18 22:02 ` dominiq at lps dot ens.fr
2015-01-19 14:36 ` dominiq at lps dot ens.fr
2015-01-19 15:39 ` howarth at bromo dot med.uc.edu
2015-01-19 15:47 ` dominiq at lps dot ens.fr [this message]
2015-01-21 20:50 ` howarth at bromo dot med.uc.edu
2015-01-28 16:20 ` howarth at bromo dot med.uc.edu
2015-01-28 16:23 ` jakub at gcc dot gnu.org
2015-01-28 16:51 ` howarth at bromo dot med.uc.edu
2015-01-28 16:53 ` howarth at bromo dot med.uc.edu
2015-01-28 17:06 ` jakub at gcc dot gnu.org
2015-01-28 20:53 ` howarth at bromo dot med.uc.edu
2015-01-28 21:24 ` mrs at gcc dot gnu.org
2015-01-28 21:26 ` mrs at gcc dot gnu.org
2015-01-28 21:27 ` mrs at gcc dot gnu.org
2015-02-02  3:32 ` dje at gcc dot gnu.org

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=bug-64635-4-3QcLcA1B4k@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).