mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Patch to allow configure out-with source directory
Date: Wed, 4 Mar 2015 12:45:55 -0500	[thread overview]
Message-ID: <20150304174555.GK23507@brightrain.aerifal.cx> (raw)
In-Reply-To: <54F7384E.8040002@skarnet.org>

On Wed, Mar 04, 2015 at 05:52:30PM +0100, Laurent Bercot wrote:
> On 04/03/2015 17:41, Rich Felker wrote:
> >Could you clarify what problem it solves? I don't think this is
> >anywhere near sufficient to support out-of-tree builds. That's a
> >difficult problem which nsz worked on in the past but didn't complete
> >because we kept running into corner cases that broke.
> 
>  Is there a discussion archive or some log of that attempt and the
> problems you ran into ?
> 
>  I shamelessly stole the musl Makefile's design to use in my
> software - I hardly knew the make language at the time, and wanted
> to study a small and clean case - and was considering implementing
> out-of-tree builds at some point in the (distant) future. If there
> were some notes describing the obstacles you faced, it would help
> me when I get to it - or more likely convince me, like it
> apparently convinced you, that it's just not worth it.

The first problem you face is how the implicit rules are written,
especially the ones for asm files that replace C files. They depend on
make's implicit application of leading directories. But I'm pretty
sure nsz had this worked out clearly and it was more subtle corner
cases that kept biting. He could probably explain better.

Another issue I recall is the presence of generated include files and
the bits symlink in the include tree. This is part of the build
process I want to revisit/change anyway when refactoring the bits
headers to reduce duplication, so understanding the obstacles to
out-of-tree builds before getting started with that would be a big
help.

Rich


  reply	other threads:[~2015-03-04 17:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04  9:25 Neil Henning
2015-03-04 16:41 ` Rich Felker
2015-03-04 16:52   ` Neil Henning
2015-03-04 16:52   ` Laurent Bercot
2015-03-04 17:45     ` Rich Felker [this message]
2015-03-04 23:53       ` Szabolcs Nagy
2015-03-05  0:02         ` Laurent Bercot

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=20150304174555.GK23507@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).