public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Freddie Chopin <freddie_chopin@op.pl>
To: newlib@sourceware.org
Subject: Re: [PATCH 2/2, newlib] Allow locking routine to be retargeted
Date: Sun, 29 Jan 2017 17:07:00 -0000	[thread overview]
Message-ID: <1485709660.1249.1.camel@op.pl> (raw)
In-Reply-To: <1485688761.1358.1.camel@op.pl>

On Sun, 2017-01-29 at 12:19 +0100, Freddie Chopin wrote:
> Hello!
> 
> After applying this patch to newlib master and _NOT_ enabling the "
> --enable-newlib-retargetable-locking" option, I'm seeing a failure
> during generation of HTML docs:
> ...

Hmm... I also see this failure when the option is enabled, so I guess
there must be something wrong with the documentation of these new
functionalities.

Interesting fact - only the build of HTML fails, PDF documentation is
generated fine.

Regards,
FCh

  reply	other threads:[~2017-01-29 17:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24 16:05 Thomas Preudhomme
2017-01-25 11:39 ` Corinna Vinschen
2017-01-25 20:43   ` Jeff Johnston
2017-01-31 17:19     ` [PATCH 3/3, " Thomas Preudhomme
2017-02-01  8:43       ` Freddie Chopin
2017-02-02 10:21         ` Thomas Preudhomme
2017-02-02 16:16           ` Freddie Chopin
2017-02-02 16:25             ` Freddie Chopin
2017-02-02 23:24           ` Freddie Chopin
2017-02-07 21:36           ` Jeff Johnston
2017-02-08  9:07             ` Thomas Preudhomme
     [not found]               ` <1199540764.24714361.1486590050100.JavaMail.zimbra@redhat.com>
2017-02-10 11:15                 ` Thomas Preudhomme
2017-02-13 22:16                   ` Jeff Johnston
2017-02-01  9:06       ` Freddie Chopin
2017-02-02 10:21         ` Thomas Preudhomme
2017-01-29 11:19 ` [PATCH 2/2, " Freddie Chopin
2017-01-29 17:07   ` Freddie Chopin [this message]
2017-01-29 22:09 ` Freddie Chopin
2017-01-30 18:53 ` Freddie Chopin

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=1485709660.1249.1.camel@op.pl \
    --to=freddie_chopin@op.pl \
    --cc=newlib@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: 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).