public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@ubuntu.com>
To: Andreas Schwab <schwab@suse.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Andrew Pinski <pinskia@gmail.com>,
	       Nicola Pero <nicola.pero@meta-innovation.com>,
	       Jeff Law <law@redhat.com>
Subject: Re: [patch] boehm-gc removal and libobjc changes to build with an external bdw-gc
Date: Wed, 30 Nov 2016 10:06:00 -0000	[thread overview]
Message-ID: <98216026-e0e2-f253-0346-94071d7dc5c7@ubuntu.com> (raw)
In-Reply-To: <mvm7f7ls73x.fsf@hawking.suse.de>

On 30.11.2016 09:29, Andreas Schwab wrote:
> configure: error: no --with-target-bdw-gc options and no bdw-gc pkg-config module found
> make[1]: *** [Makefile:19775: configure-target-libobjc] Error 1
> 
> Andreas.

that's a bit terse. Could you send the complete output for the configuration of
the libobjc subdir and the config.log?

I assume that is a configuration with --enable-objc-gc and then the pkg-config
module cannot be found.  Are gc/gc.h and libgc.so in standard paths without
having the bdw-gc pkg-config module available? Which libgc version is installed?

Thanks, Matthias

  reply	other threads:[~2016-11-30 10:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-22 20:44 Matthias Klose
2016-11-30  8:30 ` Andreas Schwab
2016-11-30 10:06   ` Matthias Klose [this message]
2016-11-30 10:11     ` Andreas Schwab
2016-11-30 10:17     ` Richard Biener
2016-11-30 10:53       ` Jakub Jelinek
2016-11-30 11:13         ` Matthias Klose
2016-11-30 11:30         ` Matthias Klose
2016-11-30 11:38           ` Richard Biener
2016-11-30 12:08             ` Matthias Klose
2016-11-30 16:54             ` Matthias Klose
2016-11-30 17:27               ` Jeff Law
2016-12-01 12:32                 ` Matthias Klose
2016-11-30 11:37         ` Richard Biener

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=98216026-e0e2-f253-0346-94071d7dc5c7@ubuntu.com \
    --to=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=law@redhat.com \
    --cc=nicola.pero@meta-innovation.com \
    --cc=pinskia@gmail.com \
    --cc=schwab@suse.de \
    /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).