mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] toolchain build error on doc/gcc.info
Date: Tue, 24 Jun 2014 09:58:15 +0200	[thread overview]
Message-ID: <20140624075815.GI21175@pengutronix.de> (raw)
In-Reply-To: <loom.20140624T091600-206@post.gmane.org>

On Tue, Jun 24, 2014 at 07:24:10AM +0000, Pavlo Ponomarov wrote:
> I'm trying to build OSELAS.Toolchain-2012.12.1 with
> arm-cortexa8-linux-gnueabihf on Ubuntu 14.04. I've made following steps:
> 1. Installed ptxdist 2013.1.0
> 2. In OSELAS.Toolchain folder selected toolchain target and now I see it in
> ptxdist menuconfig
> 3. ptxdist go
> After 5 minuter it stops with error:
> 
> /home/pavlo/OSELAS.Toolchain-2012.12.1/
> platform-arm-cortexa8-linux-gnueabihf-gcc-4.7.3-glibc-2.16.0-binutils-2.22-
> kernel-3.6-sanitized/
> build-cross/gcc-linaro-4.7-2012.11/gcc/doc/md.texi:3814: warning: 
> node next `Disable Insn Alternatives' in menu `Machine Constraints' 
> and in sectioning `Define Constraints' differ
> doc/md.texi:3814: warning: node prev `Disable Insn Alternatives' in menu 
> `Modifiers' and in sectioning `Machine Constraints' differ
> doc/md.texi:3907: warning: node prev `Define Constraints' in menu 
> `Machine Constraints' and in sectioning `Disable Insn Alternatives' differ
> make[3]: *** [doc/gccint.info] Error 1
> rm gcc.pod
> make[3]: Leaving directory `/home/pavlo/OSELAS.Toolchain-2012.12.1/
> platform-arm-cortexa8-linux-gnueabihf-gcc-4.7.3-glibc-2.16.0-binutils-2.22-
> kernel-3.6-sanitized/build-cross/gcc-linaro-4.7-2012.11-first-build/gcc'
> make[2]: *** [all-gcc] Error 2
> make[2]: Leaving directory `/home/pavlo/OSELAS.Toolchain-2012.12.1/
> platform-arm-cortexa8-linux-gnueabihf-gcc-4.7.3-glibc-2.16.0-binutils-2.22-
> kernel-3.6-sanitized/build-cross/gcc-linaro-4.7-2012.11-first-build'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/home/pavlo/OSELAS.Toolchain-2012.12.1/
> platform-arm-cortexa8-linux-gnueabihf-gcc-4.7.3-glibc-2.16.0-binutils-2.22-
> kernel-3.6-sanitized/build-cross/gcc-linaro-4.7-2012.11-first-build'
> make: *** [/home/pavlo/OSELAS.Toolchain-2012.12.1/
> platform-arm-cortexa8-linux-gnueabihf-gcc-4.7.3-glibc-2.16.0-binutils-2.22-
> kernel-3.6-sanitized/state/cross-gcc-first.compile] Error 2
> 
> Can you help me with that?

You're 'makeinfo' is too new. Is there a reason why you use
OSELAS.Toolchain-2012.12.1 and not the latest release
OSELAS.Toolchain-2013.12.2? This problem ist fixed there. If you need this
version, then you can either try to downgrade makeinfo or patch the file
that causes the error. It's just unused documentation, so it doesn't need
to be correct, just not fail.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2014-06-24  7:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24  7:24 Pavlo Ponomarov
2014-06-24  7:58 ` Michael Olbrich [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=20140624075815.GI21175@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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