From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: newlib@sourceware.org
Subject: Re: Unicode update of width and other character properties
Date: Mon, 26 Feb 2018 20:25:00 -0000 [thread overview]
Message-ID: <ccfedaf6-77b7-0cb3-d500-613faf36827a@t-online.de> (raw)
In-Reply-To: <80075f84-c541-95c2-07fd-6dad2f9a01ac@towo.net>
Am 26.02.2018 um 21:02 schrieb Thomas Wolff:
> First I added an include to the generation makefile into Makefile.am,
> then it occurred to me that the generated makefile resides in the target
> hierarchy while the generation should probably be invoked in the source
> directory, so I removed it again.
Which directory the tool is to be invoked in is irrelevant for this.
Anything you put into a Makefile.am will automatically go into
Makefile.in and Makefile, anyway. Well, assuming you actually run the
autotools, that is.
If you need to run things from a inside the src tree, you're supposed to
apply something like
cd $(srcdir) &&
cd $(top_srcdir)/some/where &&
to them just like, e.g. the auto-generated production rules for
Makefile.in and configure do it.
next prev parent reply other threads:[~2018-02-26 20:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 5:36 Thomas Wolff
2017-08-07 10:31 ` Corinna Vinschen
2017-08-07 19:18 ` Thomas Wolff
2017-08-08 8:30 ` Corinna Vinschen
2017-08-17 11:03 ` Thomas Wolff
2017-12-03 14:07 ` Corinna Vinschen
2017-12-03 17:31 ` Thomas Wolff
2017-12-03 17:33 ` Jon Turney
2017-12-04 7:32 ` Brian Inglis
2017-12-04 9:05 ` Corinna Vinschen
2018-02-25 17:14 ` Thomas Wolff
2018-02-26 17:20 ` Corinna Vinschen
2018-02-26 20:02 ` Thomas Wolff
2018-02-26 20:25 ` Hans-Bernhard Bröker [this message]
2017-12-02 11:25 ` Ping: " Thomas Wolff
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=ccfedaf6-77b7-0cb3-d500-613faf36827a@t-online.de \
--to=hbbroeker@t-online.de \
--cc=newlib@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).