From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: crossgcc@sourceware.org
Cc: "Johannes Stezenbach" <js@sig21.net>,
"Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
Subject: Re: Building the GCC manuals
Date: Wed, 09 May 2012 16:13:00 -0000 [thread overview]
Message-ID: <201205091812.33315.yann.morin.1998@free.fr> (raw)
In-Reply-To: <20120509111221.GA5366@sig21.net>
Johannes, Benoît, All,
On Wednesday 09 May 2012 13:12:21 Johannes Stezenbach wrote:
> > On Thursday 03 May 2012 12:41:20 Benoît Thébaudeau wrote:
> > > I get random build issues for Linaro GCC if using parallel jobs, probably
> > > because of some broken dependencies. It often fails at gcc.sh:795:
> > > "CT_DoExecLog ALL make ${JOBSFLAGS} pdf html".
> > >
> > > I was wondering: Why do you use ${JOBSFLAGS} here, but not on line 449:
> > > "CT_DoExecLog ALL make pdf html"?
> FWIW, I'm seeing the same issue and the fix proposed
> by Benoît fixes it for me, too.
OK, I'll push a fix that disables // jobs when building the manuals.
Thanks for the feedback!
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
prev parent reply other threads:[~2012-05-09 16:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <887104308.780104.1336041292100.JavaMail.root@advansee.com>
2012-05-03 10:39 ` Benoît Thébaudeau
2012-05-03 11:10 ` Yann E. MORIN
2012-05-09 11:12 ` Johannes Stezenbach
2012-05-09 16:13 ` Yann E. MORIN [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=201205091812.33315.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=benoit.thebaudeau@advansee.com \
--cc=crossgcc@sourceware.org \
--cc=js@sig21.net \
/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).