public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Stafford Horne <shorne@gmail.com>
Cc: Tamar Christina <Tamar.Christina@arm.com>,
	"newlib@sourceware.org" <newlib@sourceware.org>,
	Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Subject: Re: [PATCH] libgloss: add a little build system generation documentation
Date: Fri, 4 Mar 2022 01:05:59 -0500	[thread overview]
Message-ID: <YiGsR+3BVJ7qneEM@vapier> (raw)
In-Reply-To: <CAAfxs77SMgsdxTCizAXJiY-YyN7AF5ngJaLHUufPeq+DDahCWQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1488 bytes --]

i've pushed this then
-mike

From 845515267b8dfb7198ae5ca9d4a30d58b2a3d995 Mon Sep 17 00:00:00 2001
From: Mike Frysinger <vapier@gentoo.org>
Date: Fri, 4 Mar 2022 01:04:25 -0500
Subject: [PATCH] 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.
---
 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 5325fb2ed4fd..496fae352148 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.
-- 
2.34.1

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-03-04  6:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-25  4:45 Mike Frysinger
2022-02-28 10:39 ` Corinna Vinschen
2022-03-02 13:10   ` Tamar Christina
2022-03-03  4:22     ` Mike Frysinger
2022-03-03 11:44       ` Richard Earnshaw
2022-03-03 11:54         ` Tamar Christina
2022-03-04  0:06           ` Stafford Horne
2022-03-04  6:05             ` 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=YiGsR+3BVJ7qneEM@vapier \
    --to=vapier@gentoo.org \
    --cc=Richard.Earnshaw@foss.arm.com \
    --cc=Tamar.Christina@arm.com \
    --cc=newlib@sourceware.org \
    --cc=shorne@gmail.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).