Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/x11r7/xlib_libXft: remove autoreconf
Date: Mon, 01 Oct 2018 23:29:32 +0200	[thread overview]
Message-ID: <87efd91hkz.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180915121806.5264-2-bernd.kuhls@t-online.de> (Bernd Kuhls's message of "Sat, 15 Sep 2018 14:18:06 +0200")

>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:

 > Nine years ago we added autoreconf to fix libtool-related problems
 > with the matchbox package:

 > https://git.buildroot.net/buildroot/commit/?id=51ef5b81224c243aa7f937c4690b1a120c81ccbc

 > After building this defconfig with autoreconf removed from this package

 > BR2_x86_64=y
 > BR2_x86_core_avx2=y
 > BR2_TOOLCHAIN_BUILDROOT_LOCALE=y
 > BR2_TOOLCHAIN_BUILDROOT_CXX=y
 > BR2_PACKAGE_XORG7=y
 > BR2_PACKAGE_XLIB_LIBXFONT=y
 > BR2_PACKAGE_MATCHBOX=y
 > BR2_PACKAGE_MATCHBOX_SM=y
 > BR2_PACKAGE_MATCHBOX_COMMON=y
 > BR2_PACKAGE_MATCHBOX_COMMON_PDA=y
 > BR2_PACKAGE_MATCHBOX_DESKTOP=y
 > BR2_PACKAGE_MATCHBOX_KEYBOARD=y
 > BR2_PACKAGE_MATCHBOX_PANEL=y
 > BR2_PACKAGE_MATCHBOX_STARTUP_MONITOR=y

 > it is obvious that the problem which existed nine years ago seems to be
 > gone, therefore we remove autoreconf from this package because there is
 > no need for it anymore.

 > Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>

Committed to 2018.02.x, 2018.05.x and 2018.08.x, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-10-01 21:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-15 12:18 [Buildroot] [PATCH 1/2] package/x11r7/xlib_libXfont: remove autoreconf Bernd Kuhls
2018-09-15 12:18 ` [Buildroot] [PATCH 2/2] package/x11r7/xlib_libXft: " Bernd Kuhls
2018-10-01 21:29   ` Peter Korsgaard [this message]
2018-09-16  8:24 ` [Buildroot] [PATCH 1/2] package/x11r7/xlib_libXfont: " Thomas Petazzoni
2018-10-01 21:28 ` Peter Korsgaard

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=87efd91hkz.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --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