mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: [PATCH libc-test] include $(B)/config.mak instead of config.mak
Date: Thu, 22 Aug 2019 21:39:45 +0200	[thread overview]
Message-ID: <20190822193945.GR22009@port70.net> (raw)
In-Reply-To: <20190814025229.aydkh3glw5syo6ue@gmail.com>

* Fangrui Song <i@maskray.me> [2019-08-14 02:52:29 +0000]:
> --- a/Makefile
> +++ b/Makefile
> @@ -34,9 +34,9 @@ all:
>  %: s.%
>  %: SCCS/s.%
>  
> -config.mak:
> +$(B)/config.mak:
>  	cp config.mak.def $@
> --include config.mak
> +-include $(B)/config.mak
>  

this can break existing usage
by default B=src not .

for now you can include $(B)/config.mak
into your top level config.mak


      reply	other threads:[~2019-08-22 19:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-14  2:52 Fangrui Song
2019-08-22 19:39 ` Szabolcs Nagy [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=20190822193945.GR22009@port70.net \
    --to=nsz@port70.net \
    --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).