From: Mike Frysinger <vapier@gentoo.org>
To: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
Cc: newlib@sourceware.org
Subject: Re: Generate porting.info in build tree rather than source tree
Date: Fri, 4 Nov 2022 07:29:51 +0700 [thread overview]
Message-ID: <Y2Rc//StgimNQgxW@vapier> (raw)
In-Reply-To: <e8b2e663-e901-4e78-2ed8-8785369a6a65@foss.st.com>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On 31 Oct 2022 16:10, Torbjorn SVENSSON wrote:
> On 2022-10-30 08:12, Mike Frysinger wrote:
> > On 29 Oct 2022 17:38, Torbjorn SVENSSON wrote:
> >> Okay, so in that case, something changed in the newlib build process to
> >> generate and install the porting.info file
> >
> > porting.info is part of libgloss, not newlib. i understand the source tarball
> > is packaged overall as "newlib" so it can be a little confusing.
> >
> > older versions build & install porting.info if you use the install-info target.
> > but it wouldn't do it by default.
>
> Might be so, but not for the default make target (the one I used). What
> make target should I use to build everything, just like the build system
> did before your improvement, but avoid the .info files?
the GNU project provides no such target/config. you can prob cheat by
setting MAKEINFO to a stub program. or just build the info pages. i
don't see why building them is a problem in the first place.
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-11-04 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 15:40 Torbjorn SVENSSON
2022-10-29 13:32 ` Mike Frysinger
2022-10-29 15:38 ` Torbjorn SVENSSON
2022-10-30 7:12 ` Mike Frysinger
2022-10-31 15:10 ` Torbjorn SVENSSON
2022-11-04 0:29 ` Mike Frysinger [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=Y2Rc//StgimNQgxW@vapier \
--to=vapier@gentoo.org \
--cc=newlib@sourceware.org \
--cc=torbjorn.svensson@foss.st.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.
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).