public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Janis Johnson <janis187@us.ibm.com>
Cc: Gerald Pfeifer <gerald@pfeifer.com>,
	fortran@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Fortran-related libgomp failures in case of -fno-openmp
Date: Mon, 01 Jun 2009 20:21:00 -0000	[thread overview]
Message-ID: <20090601202100.GA23172@troutmask.apl.washington.edu> (raw)
In-Reply-To: <1243885782.6140.19.camel@janis-laptop>

On Mon, Jun 01, 2009 at 12:49:42PM -0700, Janis Johnson wrote:
> On Mon, 2009-06-01 at 11:14 -0700, Steve Kargl wrote:
> > 
> > If someone uses -fno-openmp and still tries to link to libgomp,
> > then the -pthread option is missing and hence the test fail
> > because -lpthread is not included.  On FreeBSD, libgomp.so.1
> > does not show a dependency on libpthread, so the dynamic linker
> > can't automagically work.
> 
> Why doesn't libgomp.so.1 show a depedency on libpthread, isn't
> that the bug?
> 

I've never looked at how the authors of libgomp wrote the
build glue nor have I tried to decipher why one would specifically
suppress OpenMP with the -fno-openmp option yet still try to
link to its runtime library.  It does appear that libgomp/configure
looks to see if -pthread (or -lpthread) is required, but then it
may not use that result in actually building libgomp.so.1

-- 
Steve

      reply	other threads:[~2009-06-01 20:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-01 17:59 Gerald Pfeifer
2009-06-01 18:14 ` Steve Kargl
2009-06-01 19:49   ` Janis Johnson
2009-06-01 20:21     ` Steve Kargl [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=20090601202100.GA23172@troutmask.apl.washington.edu \
    --to=sgk@troutmask.apl.washington.edu \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gerald@pfeifer.com \
    --cc=janis187@us.ibm.com \
    /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).