From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] configure is never called from Makefile.autotools.in
Date: Fri, 24 Aug 2007 16:01:45 +0200 [thread overview]
Message-ID: <20070824140145.GA13635@aon.at> (raw)
In-Reply-To: <f90898420708240638w6f3ed01bld3aee41bacf00374@mail.gmail.com>
On Fri, Aug 24, 2007 at 03:38:01PM +0200, Simon Pasch wrote:
>x11r7-building fails with current snapshot because of commit 19657
>(Makefile.autotools.in)
>
>"if $(PKG)_SKIP_CONFIGURE is non-empty then ./configure is skipped"
>doesn't seem to work.
>
>Instead ./configure is never called...Although I tried playing around
>with the variable LIBXCB_SKIP_CONFIGURE, etc.
Could be. I'll back it out since autotools packages always have a
configure (as opposed to the package i tried to build with the
autotools.in file).
Sorry for the inconvenience..
I'm not 100% happy with Makefile.autotools.in, btw:
rp-pppoe, for example, has it's configure not in the toplevel dir but in
src/. From the looks, the autotools.in can't cope with such a layout,
currently.
Furthermore, for all autotools packages, it is easily possible to build
outside of the sourcetree, so stepping into an empty build_dir and
calling $(PKG)_CONFIGURE_DIR/configure ... (where this would default to
just the $(PKG)_DIR) would be nice, mid-term (think project_build
stuff).
>
>Just by the way...You do a great job here...Fast and reliable. It is a
>pleasure to work with buildroot, uclibc, busybox!
nice to hear. Thanks for your kind words :)
cheers,
prev parent reply other threads:[~2007-08-24 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-24 13:38 [Buildroot] configure is never called from Makefile.autotools.in Simon Pasch
2007-08-24 14:01 ` Bernhard Fischer [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=20070824140145.GA13635@aon.at \
--to=rep.dot.nop@gmail.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