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] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released - host-m4 build error on Ubuntu 18.10
Date: Fri, 18 Jan 2019 15:06:49 +0100	[thread overview]
Message-ID: <20190118140649.ggohxc2wumusq37j@pengutronix.de> (raw)
In-Reply-To: <20190118132302.j7zw3t6lbdjf7wzz@pengutronix.de>

On Fri, Jan 18, 2019 at 02:23:02PM +0100, Roland Hieber wrote:
> On Fri, Jan 18, 2019 at 11:34:22AM +0100, Michael Olbrich wrote:
> > On Fri, Jan 18, 2019 at 10:07:45AM +0100, Roland Hieber wrote:
> > > On Sat, Sep 29, 2018 at 05:57:53PM +0200, Andreas Pretzsch wrote:
> > > > 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.
> > 
> > Did you try building the toolchain with ptxdist-2018.09.0 (with -f)? Does
> > it work?
> > 
> > > > @ PTX: This might be worth mentioning in the building instructions or
> > > > at a similar place.
> > 
> > Hmm, we don't really have a place to put version specific notes. And the
> > generic build instructions are out of date too... :-/.
> > 
> > > mol, do you think it is feasible to release a 2018.02.1 toolchain with
> > > the host-m4 (and probably other host-glibc related) patches?
> > 
> > Well, we could start fixing this in a stable branch. Any volunteers? :-)
> > And maybe a source only release. That's easy. Building all the binary
> > toolchains it what makes a release a lot of work.
> 
> The m4 patch [1] works for me, but I've also run into issues with building
> gdb against Python 3.7 on Debian unstable:
> 
>     python/python.c: In function 'bool do_start_initialization()':
>     python/python.c:1710:45: error: too few arguments to function 'int _PyImport_FixupBuiltin(PyObject*, const char*, PyObject*)'
>        _PyImport_FixupBuiltin (gdb_module, "_gdb");
>                                                  ^
> 
> There is a patch [2] available upstream, but this will break if the
> build host uses python < 3.7. Which configurations do we want to target
> for a stable branch?

The Debian packages for OSELAS.Toolchain-2018.12.0 use Python 3.5 on
stretch and 3.7 on buster, so building against either version works for gdb
8.2 so maybe you're missing some other patch?

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:[~2019-01-18 14:06 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 ` [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released - host-m4 build error on Ubuntu 18.10 Andreas Pretzsch
2019-01-18  9:07   ` Roland Hieber
2019-01-18 10:34     ` Michael Olbrich
2019-01-18 13:23       ` Roland Hieber
2019-01-18 14:06         ` 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=20190118140649.ggohxc2wumusq37j@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