From: Andreas Pretzsch <apr@cn-eng.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released - host-m4 build error on Ubuntu 18.10
Date: Sat, 29 Sep 2018 17:57:53 +0200 [thread overview]
Message-ID: <ae0febef07c6b16404a33dc7685daee1d1c6d0b8.camel@cn-eng.de> (raw)
In-Reply-To: <20180212155154.gn3omnmv23djbw4u@pengutronix.de>
During build of the toolchain (at least in configs arm-v7a-linux-
gnueabihf, arm-v7m-eabi, arm-v7em-eabihf) on an Ubuntu 18.10-beta host,
build stopped here with an host-m4 error:
fseeko.c: In function 'rpl_fseeko':
fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib."
#error "Please port gnulib fseeko.c to your platform! Look at the code in fseeko.c, then report this to bug-gnulib."
^~~~~
GEN charset.alias
make[4]: *** [Makefile:1910: fseeko.o] Error 1
make[4]: *** Waiting for unfinished jobs....
CC vasprintf.o
freadahead.c: In function 'freadahead':
freadahead.c:92:3: error: #error "Please port gnulib freadahead.c to your platform! Look at the definition of fflush, fread, ungetc on your system, then report this to bug-gnulib."
#error "Please port gnulib freadahead.c to your platform! Look at the definition of fflush, fread, ungetc on your system, then report this to bug-gnulib."
^~~~~
make[4]: *** [Makefile:1910: freadahead.o] Error 1
Reason is the glibc 2.28 on the build host (libc6:amd64 2.28-0ubuntu1).
Same probably applies to other distributions.
In up-to-date ptxdist, there is a patch included fixing this issue:
commit cba1e28 "m4/coreutil: add gnulib patches for GLibc-2.28" from
Rouven Czerwinski, dating 2018-08-23.
With this, m4 is patched accordingly, and build succeeds.
The OSELAS.Toolchain-2018.02.0 ptxdist project refers to ptxdist-
2018.02.0 by default. Above patch is part of ptxdist-2018.09.0.
So until there is a revised version of OSELAS.Toolchain, either use
ptxdist-2018.09.0 or later for building, or include the patch in the
toolchain project.
@ PTX: This might be worth mentioning in the building instructions or
at a similar place.
Thanks for providing OSELAS.Toolchain,
Andreas
--
carpe noctem engineering
Ingenieurbuero fuer Hard- & Software-Entwicklung Andreas Pretzsch
Dipl.-Ing. (FH) Andreas Pretzsch Tel. +49-(0)7307-936088-1
Lange Strasse 28a Fax: +49-(0)7307-936088-9
89250 Senden, Germany email: apr@cn-eng.de
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2018-09-29 15:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 15:51 [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released Michael Olbrich
2018-02-13 10:00 ` Roland Hieber
2018-02-13 10:04 ` Michael Olbrich
2018-02-13 12:41 ` Alexander Dahl
2018-02-13 13:30 ` Michael Olbrich
2018-02-13 13:59 ` Denis OSTERLAND
2018-02-13 14:37 ` Michael Olbrich
2018-02-19 9:38 ` Michael Olbrich
2018-02-13 14:05 ` Alexander Dahl
2018-02-13 14:44 ` Michael Olbrich
2018-02-18 20:00 ` Jon Ringle
2018-02-19 8:11 ` Alexander Dahl
2018-02-19 9:34 ` Michael Olbrich
2018-09-29 15:57 ` Andreas Pretzsch [this message]
2019-01-18 9:07 ` [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released - host-m4 build error on Ubuntu 18.10 Roland Hieber
2019-01-18 10:34 ` Michael Olbrich
2019-01-18 13:23 ` Roland Hieber
2019-01-18 14:06 ` Michael Olbrich
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=ae0febef07c6b16404a33dc7685daee1d1c6d0b8.camel@cn-eng.de \
--to=apr@cn-eng.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