From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: newlib@sourceware.org
Cc: Sam Edge <sam.edge@gmx.com>
Subject: Re: Online documentation revisions
Date: Wed, 27 Sep 2023 16:19:11 -0600 [thread overview]
Message-ID: <6284c3ec-9231-9820-4a32-684bd8a56f00@Shaw.ca> (raw)
In-Reply-To: <aa2f58c1-6b79-49a9-9ce6-5701638d09e1@gmx.com>
On 2023-09-27 02:42, Sam Edge wrote:
> On 26/09/2023 18:12, Sam Edge via Newlib wrote:
> > On 26/09/2023 18:00, Brian Inglis wrote:
> > > Had a similar issue wanting to see libc docs for Cygwin builds.
> > >
> > > Check out repo at that rev, configure into out of tree build and
> install dirs, then under e.g. build-3.0.0/newlib run to get into your
> e.g. install-3.0.0/usr/share/{info,man} dirs:
> > >
> > > $ make info man && make install info man
> > >
> >
> > Oh well. Guessed as much.
> >
> > Thanks for the TL;DR instructions. :-)
> >
>
> Well, that didn't work - see build.log attached. (Building on a Ubuntu
> 22.04 LTS based host by the way.)
>
> Oh wait. Those are to build the manual pages. I'm after the one page
> HTML document for a non-cygwin bare-metal (e.g. arm-none-eabi-) build,
> sorry.
>
> I've cloned from https://sourceware.org/git/newlib-cygwin.git and
> checked out newlib-3.0.0 (for example).
>
> I have the GCC cross toolchain available if required but I don't want to
> build the binaries, just the all-on-one-page HTML documentation file.
>
> What am I missing?
Sorry - doh! - there is a process as part of the build - requires makedoc to be
built - and install- concatenated try:
make doc info html && make install-html
We may be treading uncharted waters, and you may need to just pick up the bits
of html generated, or do a full make to get html generated properly.
See newlib HOWTO!
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-09-27 22:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 15:27 Sam Edge
2023-09-26 17:00 ` Brian Inglis
2023-09-26 17:12 ` Sam Edge
2023-09-27 8:42 ` Sam Edge
2023-09-27 22:19 ` Brian Inglis [this message]
2023-09-28 6:37 ` Sam Edge
2023-10-15 9:13 ` Mike Frysinger
2024-01-03 23:11 ` Jeff Johnston
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=6284c3ec-9231-9820-4a32-684bd8a56f00@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=newlib@sourceware.org \
--cc=sam.edge@gmx.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).