public inbox for newlib-cvs@sourceware.org help / color / mirror / Atom feed
From: Michael Frysinger <vapier@sourceware.org> To: newlib-cvs@sourceware.org Subject: [newlib-cygwin] libgloss: add new Build System Internals node to the menu Date: Fri, 4 Mar 2022 06:05:18 +0000 (GMT) [thread overview] Message-ID: <20220304060518.DFE853858D37@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=845515267b8dfb7198ae5ca9d4a30d58b2a3d995 commit 845515267b8dfb7198ae5ca9d4a30d58b2a3d995 Author: Mike Frysinger <vapier@gentoo.org> Date: Fri Mar 4 01:04:25 2022 -0500 libgloss: add new Build System Internals node to the menu Seems that some versions of texinfo require the @menu to have all entries at the top level, so add the new build one to it. Diff: --- libgloss/doc/porting.texi | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/libgloss/doc/porting.texi b/libgloss/doc/porting.texi index 5325fb2ed..496fae352 100644 --- a/libgloss/doc/porting.texi +++ b/libgloss/doc/porting.texi @@ -136,6 +136,7 @@ new library is called Libgloss, for Gnu Low-level OS support. * Building libgloss:: How to configure and built libgloss for a target. * Board support:: How to add support for a new board. +* Build System Internals:: How the libgloss build system works. @end menu @node Supported targets, Building libgloss, Libgloss, Libgloss @@ -311,7 +312,7 @@ used. This is done so libgloss will build automatically with a fresh, and uninstalled object tree. It also makes it easier to debug the other tools using libgloss's test suites. -@node Board support, , Building libgloss, Libgloss +@node Board support @section Adding Support for a New Board This section explains how to add support for a new board to libgloss.
reply other threads:[~2022-03-04 6:05 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220304060518.DFE853858D37@sourceware.org \ --to=vapier@sourceware.org \ --cc=newlib-cvs@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: linkBe 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).