From: Mike Frysinger <vapier@gentoo.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: Indu Bhagat <indu.bhagat@oracle.com>,
weimin.pan@oracle.com, nickc@redhat.com, binutils@sourceware.org
Subject: Re: [PATCH,V4 11/11] doc: add SFrame spec file
Date: Sun, 11 Dec 2022 16:29:49 +0900 [thread overview]
Message-ID: <Y5WG7cIFiL7beOqH@vapier> (raw)
In-Reply-To: <38e04026-4570-91c1-ab2c-414ba54f9b45@suse.com>
[-- Attachment #1: Type: text/plain, Size: 1042 bytes --]
On 22 Nov 2022 09:09, Jan Beulich via Binutils wrote:
> On 09.11.2022 09:42, Indu Bhagat via Binutils wrote:
> > --- /dev/null
> > +++ b/libsframe/doc/sframe-spec.texi
> > @@ -0,0 +1,619 @@
> > +\input texinfo @c -*- Texinfo -*-
> > +@setfilename sframe-spec.info
> > +@settitle The SFrame Format
> > +@ifnottex
> > +@xrefautomaticsectiontitle on
>
> I'm unaware of a specification of a minimum makeinfo version that's
> required for building binutils, yet my admittedly ancient makeinfo
> 4.12 chokes on this.
there is no min version required to build binutils, although there are
min versions to build its documentation.
configure.ac: # For an installed makeinfo, we require it to be from texinfo 4.7 or
gprofng/configure.ac: MAKEINFO="@echo $MAKEINFO is too old, 6.5 or newer required; true"
libctf/configure.ac: # We require texinfo to be 6.3 or later, for a working synindex
libiberty/configure.ac: MAKEINFO="@echo $MAKEINFO is too old, 4.0 or newer required; true"
-mike
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-11 7:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 8:42 [PATCH,V4 00/11] Definition and support for SFrame unwind format Indu Bhagat
2022-11-09 8:42 ` [PATCH,V4 01/11] sframe.h: Add SFrame format definition Indu Bhagat
2022-11-09 8:42 ` [PATCH,V4 02/11] gas: add new command line option --gsframe Indu Bhagat
2022-11-09 8:42 ` [PATCH,V4 03/11] gas: generate .sframe from CFI directives Indu Bhagat
2022-11-09 8:42 ` [PATCH,V4 04/11] gas: testsuite: add new tests for SFrame unwind info Indu Bhagat
2022-11-09 8:42 ` [PATCH,V4 05/11] libsframe: add the SFrame library Indu Bhagat
2022-11-09 8:42 ` [PATCH,V4 06/11] bfd: linker: merge .sframe sections Indu Bhagat
2022-11-09 8:42 ` [PATCH,V4 07/11] readelf/objdump: support for SFrame section Indu Bhagat
2022-11-09 8:42 ` [PATCH,V4 08/11] src-release.sh: Add libsframe Indu Bhagat
2022-11-09 8:42 ` [PATCH,V4 09/11] binutils/NEWS: add text for SFrame support Indu Bhagat
2022-11-09 8:42 ` [PATCH,V4 10/11] gas/NEWS: add text about new command line option and " Indu Bhagat
2022-11-09 8:42 ` [PATCH,V4 11/11] doc: add SFrame spec file Indu Bhagat
2022-11-22 8:09 ` Jan Beulich
2022-11-22 19:44 ` Indu Bhagat
2022-12-11 7:29 ` Mike Frysinger [this message]
2022-11-15 12:20 ` [PATCH,V4 00/11] Definition and support for SFrame unwind format Nick Clifton
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=Y5WG7cIFiL7beOqH@vapier \
--to=vapier@gentoo.org \
--cc=binutils@sourceware.org \
--cc=indu.bhagat@oracle.com \
--cc=jbeulich@suse.com \
--cc=nickc@redhat.com \
--cc=weimin.pan@oracle.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).