mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] binutils: disable gprofng to fix build with host java installed
Date: Mon,  5 Dec 2022 13:53:57 +0100	[thread overview]
Message-ID: <20221205125357.2405300-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20221202125811.2834144-1-p.zabel@pengutronix.de>

Thanks, applied as 29c0f4789de7aa470d01c8fd56fa732c14fb76c7.

Michael

[sent from post-receive hook]

On Mon, 05 Dec 2022 13:53:57 +0100, Philipp Zabel <p.zabel@pengutronix.de> wrote:
> Explicitly disable gprofng to avoid a build failure:
> 
>   make[5]: Entering directory '.../build-target/binutils-2.39/gprofng/libcollector'
>     CC       libgp_collector_la-jprofile.lo
>   jprofile.c:32:10: fatal error: jni.h: No such file or directory
> 
> if the binutils build system manages to find a Java host installation.
> Use an environment variable instead of the --disable-gprofng configure
> option for compatibility with older binutils versions.
> 
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> Message-Id: <20221202125811.2834144-1-p.zabel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
> 
> diff --git a/rules/binutils.make b/rules/binutils.make
> index 17b7f7e3e313..bec8436d62fb 100644
> --- a/rules/binutils.make
> +++ b/rules/binutils.make
> @@ -29,6 +29,7 @@ BINUTILS_DIR		:= $(BUILDDIR)/$(BINUTILS)
>  
>  BINUTILS_CONF_ENV := \
>  	$(CROSS_ENV) \
> +	enable_gprofng=no \
>  	host_configargs='$(strip \
>  		--enable-targets=$(PTXCONF_GNU_TARGET) \
>  		--disable-nls \



      reply	other threads:[~2022-12-05 12:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 12:58 [ptxdist] [PATCH] " Philipp Zabel
2022-12-05 12:53 ` Michael Olbrich [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=20221205125357.2405300-1-m.olbrich@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=p.zabel@pengutronix.de \
    --cc=ptxdist@pengutronix.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