Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] package/gcc: align gcc-final configure-cmds to the generic ones
Date: Sun, 22 Nov 2015 22:02:40 +0100	[thread overview]
Message-ID: <20151122210240.GC3603@free.fr> (raw)
In-Reply-To: <56522CB7.3000807@mind.be>

Arnout, All,

On 2015-11-22 21:59 +0100, Arnout Vandecappelle spake thusly:
> On 22-11-15 15:39, Yann E. MORIN wrote:
> > Since 7d6c79 (Compile static versions of gcc libraries) was applied, the
> > generic configure commands have been updated, but those changes have not
> > been propagated to the gcc-final custom configure commands.
> > 
> > Update the gcc-final custom configure commands to better match the
> > generic ones.
> > 
> > We do not propagate --disable-dependency-tracking because it breaks the
> > build, and --enable-shared (because of 169141a).
> > 
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > ---
> >  package/gcc/gcc-final/gcc-final.mk | 25 ++++++++++++++++++++-----
> >  1 file changed, 20 insertions(+), 5 deletions(-)
> > 
> > diff --git a/package/gcc/gcc-final/gcc-final.mk b/package/gcc/gcc-final/gcc-final.mk
> > index dbdb615..53199c3 100644
> > --- a/package/gcc/gcc-final/gcc-final.mk
> > +++ b/package/gcc/gcc-final/gcc-final.mk
> > @@ -36,16 +36,31 @@ HOST_GCC_FINAL_PRE_CONFIGURE_HOOKS += HOST_GCC_CONFIGURE_SYMLINK
> >  #
> >  # So we must completely override the generic commands and provide our own.
> >  #
> > +# Except for --disable-dependency-tracking which breaks the build, and
> > +# --enable-shared (see 169141a, gcc-final: disable shared build for
> > +# static), we reproduce the exact same command as the autotools infra
> > +# uses.
> > +#
> >  define  HOST_GCC_FINAL_CONFIGURE_CMDS
> >  	(cd $(HOST_GCC_FINAL_SRCDIR) && rm -rf config.cache; \
> > -		$(HOST_CONFIGURE_OPTS) \
> > -		CFLAGS="$(HOST_CFLAGS)" \
> > -		LDFLAGS="$(HOST_LDFLAGS)" \
> > -		$(HOST_GCC_FINAL_CONF_ENV) \
> > -		./configure \
> > +	$(HOST_CONFIGURE_OPTS) \
> > +	CFLAGS="$(HOST_CFLAGS)" \
> > +	LDFLAGS="$(HOST_LDFLAGS)" \
> > +	$(HOST_GCC_FINAL_CONF_ENV) \
> 
>  I do agree with the whitespace change.
> 
> > +	CONFIG_SITE=/dev/null \
> 
>  This makes sense to me as well.
> 
> > +	./configure \
> >  		--prefix="$(HOST_DIR)/usr" \
> >  		--sysconfdir="$(HOST_DIR)/etc" \
> > +		--localstatedir="$(HOST_DIR)/var" \
> 
>  This one is pointless but harmless.
> 
> >  		--enable-static \
> > +		--disable-gtk-doc \
> > +		--disable-gtk-doc-html \
> > +		--disable-doc \
> > +		--disable-docs \
> > +		--disable-documentation \
> > +		--disable-debug \
> > +		--with-xmlto=no \
> > +		--with-fop=no \
> 
>  But all of this gains us nothing IMHO, and is in a way harmful because it will
> produce warnings. We accept those warnings for the generic configure commands
> because it gives us the advantage of avoiding that we forget to add them when
> creating a package, but in this case I really don't see the point.

The point is to diverge as little as possible from the generic command.

Even if some options are useless, or cause the same warning as if we
were using the generic command, they are replicated here. Only those
options we really do not want are omitted.

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2015-11-22 21:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-22 14:39 [Buildroot] [PATCH 0/3] core+gcc: align configure commands (branch yem/quickies-for-master) Yann E. MORIN
2015-11-22 14:39 ` [Buildroot] [PATCH 1/3] core/pkg-autotools: align host configure commands to target one Yann E. MORIN
2015-11-22 20:46   ` Arnout Vandecappelle
2015-11-23 17:38   ` Thomas Petazzoni
2015-11-23 17:51     ` Yann E. MORIN
2015-11-23 17:55       ` Yann E. MORIN
2015-11-23 20:09       ` Thomas Petazzoni
2015-11-23 20:51         ` Yann E. MORIN
2015-11-22 14:39 ` [Buildroot] [PATCH 2/3] package/gcc: comment on why we override the generic configure commands Yann E. MORIN
2015-11-22 15:11   ` Jérôme Pouiller
2015-11-22 20:48   ` Arnout Vandecappelle
2015-11-23 17:38   ` Thomas Petazzoni
2015-11-22 14:39 ` [Buildroot] [PATCH 3/3] package/gcc: align gcc-final configure-cmds to the generic ones Yann E. MORIN
2015-11-22 20:59   ` Arnout Vandecappelle
2015-11-22 21:02     ` Yann E. MORIN [this message]
2015-11-23 20:14   ` Thomas Petazzoni
2015-11-24 18:39     ` Yann E. MORIN
2015-12-29 22:06   ` Yann E. MORIN

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=20151122210240.GC3603@free.fr \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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