Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released - host-m4 build error on Ubuntu 18.10

2019-01-18 Thread Michael Olbrich 
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- |

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released - host-m4 build error on Ubuntu 18.10

2019-01-18 Thread Roland Hieber 
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?

[1]: 
https://git.pengutronix.de/cgit/rhi/OSELAS.Toolchain/commit/?h=rhi/for-stable/OSELAS.Toolchain-2018.02.x=15f8bd0a1a8c82fdc722793b429b47c31d85dbb4
[2]: https://sourceware.org/ml/gdb-patches/2018-05/msg00863.html

-- 
Roland Hieber | r.hie...@pengutronix.de |
Pengutronix e.K.  | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917- |

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released - host-m4 build error on Ubuntu 18.10

2019-01-18 Thread Michael Olbrich 
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.

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- |

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released - host-m4 build error on Ubuntu 18.10

2019-01-18 Thread Roland Hieber 
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.
> 
> @ PTX: This might be worth mentioning in the building instructions or
> at a similar place.

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?

 - Roland
-- 
Roland Hieber | r.hie...@pengutronix.de |
Pengutronix e.K.  | https://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim | Phone: +49-5121-206917-5086 |
Amtsgericht Hildesheim, HRA 2686  | Fax:   +49-5121-206917- |

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released - host-m4 build error on Ubuntu 18.10

2018-09-29 Thread Andreas Pretzsch 
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 PretzschTel. +49-(0)7307-936088-1
Lange Strasse 28a   Fax: +49-(0)7307-936088-9
89250 Senden, Germany   email: a...@cn-eng.de


___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released

2018-02-19 Thread Michael Olbrich 
Hi,

On Tue, Feb 13, 2018 at 03:37:10PM +0100, Michael Olbrich wrote:
> On Tue, Feb 13, 2018 at 01:59:14PM +, Denis OSTERLAND wrote:
> > Do you plan to upload the deb file to debian.pengutronix.de?
> 
> Yes, but it will take a bit to compile those. gdb uses Python 3 now, but
> that means that I have to rebuilt the toolchains for all supported Debian
> releases because they all have different Python 3 minor versions.

The binary toolchains are now available on debian.pengutronix.de. Make sure
you set the correct debian release in the sources.list instead of just
using 'sid'. It makes a difference with this release.

Regards,
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- |

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released

2018-02-19 Thread Michael Olbrich 
Hallo,

On Mon, Feb 19, 2018 at 09:11:25AM +0100, Alexander Dahl wrote:
> On Sun, Feb 18, 2018 at 03:00:22PM -0500, Jon Ringle wrote:
> > I built the arm-v5te toolchain, and it built:
> > oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo14.04+1_amd64.deb
> 
> So you probably used Ubuntu 14.04?
> 
> > But on https://debian.pengutronix.de/debian/pool/main/o/oselas.toolchain/ I
> > see:
> > oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1_amd64.deb
> > oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo8+1_amd64.deb
> > oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo9+1_amd64.deb
> > 
> > What is the cause for the difference in `bpo8+1`, `bpo9+1` and the
> > `bpo14.04+1` in the filename?
> 
> From my personal analysis I think, this is spread over several files
> in OSELAS.Toolchain repository. In `rules/image-toolchain-deb.make`
> IMAGE_TOOLCHAIN_DEB_VERSION_EXT is set by a function defined in
> `scripts/lib/ptxd_make_debian_version_ext.sh`. This gets ${VERSION_ID}
> from your build host `/etc/os-version`, which is 8 for Debian jessie,
> 9 for Debian stretch and probably 14.04 for the Ubuntu you are using,
> so it depends on the build host. I would guess the 'bpo' means
> something like 'backports', at least Debian backports uses similar
> markings.
> 
> The rest of those version numbers is like this: Something creates the
> file `.tarball-version`, maybe it's just included in the tarball, not
> in Git repository. In `rules/image-toolchain-deb.make` the script
> `scripts/setlocalversion` is called with that as a parameter, which
> probably outputs some version from Git, if using the Git repo instead
> of a tarball. This is assigned to IMAGE_TOOLCHAIN_DEB_VERSION in
> `rules/image-toolchain-deb.make` … yes I think this is it.

Right, the different debian packages are built from the same source but for
different Debian release. This is necessary because the new toolchains uses
Python 3 for gdb and jessie, stretch and buster all use different Python 3
minor release.
The versioning is set up in a way that it works correctly if you install
the toolchain on jessie and then update to stretch (provided you have the
correct sources.list entries).

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- |

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released

2018-02-19 Thread Alexander Dahl 
Hei hei,

On Sun, Feb 18, 2018 at 03:00:22PM -0500, Jon Ringle wrote:
> I built the arm-v5te toolchain, and it built:
> oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo14.04+1_amd64.deb

So you probably used Ubuntu 14.04?

> But on https://debian.pengutronix.de/debian/pool/main/o/oselas.toolchain/ I
> see:
> oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1_amd64.deb
> oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo8+1_amd64.deb
> oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo9+1_amd64.deb
> 
> What is the cause for the difference in `bpo8+1`, `bpo9+1` and the
> `bpo14.04+1` in the filename?

From my personal analysis I think, this is spread over several files
in OSELAS.Toolchain repository. In `rules/image-toolchain-deb.make`
IMAGE_TOOLCHAIN_DEB_VERSION_EXT is set by a function defined in
`scripts/lib/ptxd_make_debian_version_ext.sh`. This gets ${VERSION_ID}
from your build host `/etc/os-version`, which is 8 for Debian jessie,
9 for Debian stretch and probably 14.04 for the Ubuntu you are using,
so it depends on the build host. I would guess the 'bpo' means
something like 'backports', at least Debian backports uses similar
markings.

The rest of those version numbers is like this: Something creates the
file `.tarball-version`, maybe it's just included in the tarball, not
in Git repository. In `rules/image-toolchain-deb.make` the script
`scripts/setlocalversion` is called with that as a parameter, which
probably outputs some version from Git, if using the Git repo instead
of a tarball. This is assigned to IMAGE_TOOLCHAIN_DEB_VERSION in
`rules/image-toolchain-deb.make` … yes I think this is it.

HTH && Greets
Alex

-- 
»With the first link, the chain is forged. The first speech censured, 
the first thought forbidden, the first freedom denied, chains us all 
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: C28E E6B9 0263 95CF 8FAF  08FA 34AD CD00 7221 5CC6 ***


signature.asc
Description: PGP signature
___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released

2018-02-18 Thread Jon Ringle 
I built the arm-v5te toolchain, and it built:
oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo14.04+1_amd64.deb

But on https://debian.pengutronix.de/debian/pool/main/o/oselas.toolchain/ I
see:
oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1_amd64.deb
oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo8+1_amd64.deb
oselas.toolchain-2018.02.0-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo9+1_amd64.deb

What is the cause for the difference in `bpo8+1`, `bpo9+1` and the
`bpo14.04+1` in the filename?

-Jon


On Mon, Feb 12, 2018 at 10:51 AM, Michael Olbrich 
wrote:

> Hi,
>
> I'm happy to announce that I've just released OSELAS.Toolchain-2018.02.0.
>
> This is a major release with significant changes. All components of the
> primary toolchains have been updated to the latest versions. The highlights
> are:
>  - gcc 7.3
>  - glibc 2.27
>  - binutils 2.30
>  - kernel headers 4.15
>  - gdb 8.1
>
> The Cortex-A8 toolchains have been removed. Please use the ARM v7a
> Toolchains instead. The Cortex-M3 and Cortex-M4 toochains have been
> replaces by the more general ARM v7m and v7em toolchains.
>
> Download the release here:
> https://public.pengutronix.de/oselas/toolchain/
>
> Enjoy,
> Michael Olbrich
>
> --
> 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- |
>
> ___
> ptxdist mailing list
> ptxdist@pengutronix.de
>
___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released

2018-02-13 Thread Michael Olbrich 
On Tue, Feb 13, 2018 at 03:05:17PM +0100, Alexander Dahl wrote:
> Am Dienstag, 13. Februar 2018, 14:30:38 CET schrieb Michael Olbrich:
> > > Host is on Debian 9 (stretch), amd64, using icecc:
> 
> ^^
> 
> > Hmm, generating Debian packages is not widely tested outside my local
> > setup, but it should work. Can you add 'set -x' at the beginning of the
> > main() function in scripts/make_deb.sh and send the output?
> 
> ---
> target: oselas.toolchain-2018.02.0-dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-
> glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-
> dirty-0ptx1~bpo9+1_amd64.deb
> ---
> 
> + getopts d:s: opt
> + case "${opt}" in
> + local deb=/mnt/data_2/adahl/src/OSELAS.Toolchain/dist/
> oselas.toolchain-2018.02.0-dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-
> binutils-2.30-kernel-4.15-sanitized_2018.02.0-dirty-0ptx1~bpo9+1_amd64.deb
> + getopts d:s: opt
> + case "${opt}" in
> + local src=/mnt/data_2/adahl/src/OSELAS.Toolchain/inst/opt/
> OSELAS.Toolchain-2018.02.0/arm-v5te-linux-gnueabi/gcc-7.3.1-glibc-2.27-
> binutils-2.30-kernel-4.15-sanitized
> + getopts d:s: opt
> + '[' -z /mnt/data_2/adahl/src/OSELAS.Toolchain/dist/
> oselas.toolchain-2018.02.0-dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-
> binutils-2.30-kernel-4.15-sanitized_2018.02.0-dirty-0ptx1~bpo9+1_amd64.deb -o 
> -z /mnt/data_2/adahl/src/OSELAS.Toolchain/inst/opt/OSELAS.Toolchain-2018.02.0/
> arm-v5te-linux-gnueabi/gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-
> sanitized ']'
> + local 'ifs_orig=
> '
> + IFS=_
> + set -- /mnt/data 2/adahl/src/OSELAS.Toolchain/dist/
> oselas.toolchain-2018.02.0-dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-
> binutils-2.30-kernel-4.15-sanitized 2018.02.0-dirty-0ptx1~bpo9+1 amd64.deb
> + IFS='
> '
> + local package=data
> + local inst=/mnt/
> + local version=2/adahl/src/OSELAS.Toolchain/dist/oselas.toolchain-2018.02.0-
> dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-
> sanitized
> + local arch=2018.02.0-dirty-0ptx1~bpo9+1
> + local prefix=opt/OSELAS.Toolchain-2018.02.0/arm-v5te-linux-gnueabi/
> gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized
> + local destdir=/mnt/data_2/adahl/src/OSELAS.Toolchain/inst/
> + local debian_tmp=/mnt//data-temp
> + '[' -e /mnt//data-temp ']'
> + mkdir -p /mnt//data-temp/tmp /mnt//data-temp/debian
> mkdir: cannot create directory '/mnt//data-temp': Permission denied
> mkdir: cannot create directory '/mnt//data-temp': Permission denied
> 
> 
> 
> The problem is probably the '_' in the path of my working directory?

Indeed. We do some magic with '_' to split the version and arch and this
breaks in your case.

> > This is a bug in gcc on your build host. What distribution (and version)
> > are you using and what is the output of 'gcc --version'?
> 
> Debian GNU/Linux 9 (stretch) on amd64.
> 
> % gcc --version
> gcc (Debian 6.3.0-18) 6.3.0 20170516
> 
> The build without icecc seemed to succeed, if I start it from a (symlinked) 
> directory without '_' anywhere in the path. I get some warnings on the *.deb 
> stage, but it succeeds.

Strange, I've used exactly the same compiler to built at least one
toolchain with icecc enabled.
I'm currently building the Debian packages for buster. stretch is next, so
I'll see if I get any similar errors.

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- |

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released

2018-02-13 Thread Michael Olbrich 
Hi,

On Tue, Feb 13, 2018 at 01:59:14PM +, Denis OSTERLAND wrote:
> Do you plan to upload the deb file to debian.pengutronix.de?

Yes, but it will take a bit to compile those. gdb uses Python 3 now, but
that means that I have to rebuilt the toolchains for all supported Debian
releases because they all have different Python 3 minor versions.

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- |

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released

2018-02-13 Thread Alexander Dahl 
Hei hei,

Am Dienstag, 13. Februar 2018, 14:30:38 CET schrieb Michael Olbrich:
> > Host is on Debian 9 (stretch), amd64, using icecc:

^^

> Hmm, generating Debian packages is not widely tested outside my local
> setup, but it should work. Can you add 'set -x' at the beginning of the
> main() function in scripts/make_deb.sh and send the output?

---
target: oselas.toolchain-2018.02.0-dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-
glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-
dirty-0ptx1~bpo9+1_amd64.deb
---

+ getopts d:s: opt
+ case "${opt}" in
+ local deb=/mnt/data_2/adahl/src/OSELAS.Toolchain/dist/
oselas.toolchain-2018.02.0-dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-
binutils-2.30-kernel-4.15-sanitized_2018.02.0-dirty-0ptx1~bpo9+1_amd64.deb
+ getopts d:s: opt
+ case "${opt}" in
+ local src=/mnt/data_2/adahl/src/OSELAS.Toolchain/inst/opt/
OSELAS.Toolchain-2018.02.0/arm-v5te-linux-gnueabi/gcc-7.3.1-glibc-2.27-
binutils-2.30-kernel-4.15-sanitized
+ getopts d:s: opt
+ '[' -z /mnt/data_2/adahl/src/OSELAS.Toolchain/dist/
oselas.toolchain-2018.02.0-dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-
binutils-2.30-kernel-4.15-sanitized_2018.02.0-dirty-0ptx1~bpo9+1_amd64.deb -o 
-z /mnt/data_2/adahl/src/OSELAS.Toolchain/inst/opt/OSELAS.Toolchain-2018.02.0/
arm-v5te-linux-gnueabi/gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-
sanitized ']'
+ local 'ifs_orig=
'
+ IFS=_
+ set -- /mnt/data 2/adahl/src/OSELAS.Toolchain/dist/
oselas.toolchain-2018.02.0-dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-
binutils-2.30-kernel-4.15-sanitized 2018.02.0-dirty-0ptx1~bpo9+1 amd64.deb
+ IFS='
'
+ local package=data
+ local inst=/mnt/
+ local version=2/adahl/src/OSELAS.Toolchain/dist/oselas.toolchain-2018.02.0-
dirty-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-
sanitized
+ local arch=2018.02.0-dirty-0ptx1~bpo9+1
+ local prefix=opt/OSELAS.Toolchain-2018.02.0/arm-v5te-linux-gnueabi/
gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized
+ local destdir=/mnt/data_2/adahl/src/OSELAS.Toolchain/inst/
+ local debian_tmp=/mnt//data-temp
+ '[' -e /mnt//data-temp ']'
+ mkdir -p /mnt//data-temp/tmp /mnt//data-temp/debian
mkdir: cannot create directory '/mnt//data-temp': Permission denied
mkdir: cannot create directory '/mnt//data-temp': Permission denied



The problem is probably the '_' in the path of my working directory?

> This is a bug in gcc on your build host. What distribution (and version)
> are you using and what is the output of 'gcc --version'?

Debian GNU/Linux 9 (stretch) on amd64.

% gcc --version
gcc (Debian 6.3.0-18) 6.3.0 20170516

The build without icecc seemed to succeed, if I start it from a (symlinked) 
directory without '_' anywhere in the path. I get some warnings on the *.deb 
stage, but it succeeds.

HTH & Greets
Alex


___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released

2018-02-13 Thread Denis OSTERLAND 
Am Dienstag, den 13.02.2018, 14:30 +0100 schrieb Michael Olbrich:
> Hi,
> 
> On Tue, Feb 13, 2018 at 01:41:59PM +0100, Alexander Dahl wrote:
> > 
> > I had several problems compiling the new toolchain, the main one like in 
> > the 
> > first example, see below.
> > 
> > Am Montag, 12. Februar 2018, 16:51:54 CET schrieb Michael Olbrich:
> > > 
> > > Download the release here:
> > > https://public.pengutronix.de/oselas/toolchain/
> > I didn't download a prebuilt release, but tried to build it myself from 
> > Git. 
> > Host is on Debian 9 (stretch), amd64, using icecc:
> > 
> >   git clean -dxf
> >   git checkout v2018.02.0
> >   ln -s /usr/local/bin/ptxdist-2018.02.0 p
> >   make -f build_all_v2.mk
> > 
> > This ends with:
> > 
> > ---
> > target: 
> > oselas.toolchain-2018.02.0-powerpc-603e-linux-gnu-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo9+1_amd64.deb
> > ---
> > 
> > mkdir: cannot create directory '/mnt//data-temp': Permission denied   
> > mkdir: cannot create directory '/mnt//data-temp': Permission denied   
> > scripts/make_deb.sh: line 37: /mnt//data-temp/debian/control: No such file 
> > or directory
> > scripts/make_deb.sh: line 52: /mnt//data-temp/debian/changelog: No such 
> > file or directory
> > scripts/make_deb.sh: line 59: /mnt//data-temp/debian/compat: No such file 
> > or directory
> > Copy data...
> > tar: /mnt//data-temp/tmp: Cannot open: No such file or directory
> > tar: Error is not recoverable: exiting now
> > scripts/make_deb.sh: line 67: cd: /mnt//data-temp: No such file or directory
> > Generate dependencies...
> > dh_shlibdeps: cannot read debian/control: No such file or directory
> > 
> > /mnt/data_2/adahl/src/OSELAS.Toolchain/rules/image-toolchain-deb.make:28: 
> > recipe for target 
> > '/mnt/data_2/adahl/src/OSELAS.Toolchain/dist/oselas.toolchain-2018.02.0-powerpc-603e-linux-gnu-gcc-
> > 7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo9+1_amd64.deb'
> >  failed
> > make: *** 
> > [/mnt/data_2/adahl/src/OSELAS.Toolchain/dist/oselas.toolchain-2018.02.0-powerpc-603e-linux-gnu-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo9+1_amd64.deb]
> > Error 2
> > build_all_v2.mk:49: die Regel für Ziel 
> > „gstate/powerpc-603e-linux-gnu-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized.build“
> >  scheiterte
> > make: *** 
> > [gstate/powerpc-603e-linux-gnu-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized.build]
> >  Fehler 2
> > make -f build_all_v2.mk  3545,92s user 325,01s system 164% cpu 39:07,55 
> > total
> Hmm, generating Debian packages is not widely tested outside my local
Do you plan to upload the deb file to debian.pengutronix.de?
> setup, but it should work. Can you add 'set -x' at the beginning of the
> main() function in scripts/make_deb.sh and send the output?
> 
> > 
> > Second try, just building one toolchain:
> > 
> >   ./build_one.sh v5te
> > 
> > Result (the failing part):
> > 
> > In file included from /usr/include/c++/6/vector:69:0,
> >  from ../../binutils-2.30/gold/options.h:44,
> >  from ../../binutils-2.30/gold/incremental.cc:30:
> > /usr/include/c++/6/bits/vector.tcc: In member function 'void 
> > std::vector<_Tp, _Alloc>::_M_default_append(std::vector<_Tp, 
> > _Alloc>::size_type) [with _Tp = long unsigned int; _Alloc =
> > std::allocator]':
> > /usr/include/c++/6/bits/vector.tcc:586:5: internal compiler error: in 
> > gt_ggc_mx_symtab_node, at gtype-desc.c:1773
> >  }
> >  ^
> > libtool: link: gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes 
> > -Wshadow -Wstack-usage=262144 -I../../binutils-2.30/binutils/../zlib -g -O2 
> > -static-libstdc++ -static-libgcc -o ar arparse.o
> > arlex.o ar.o not-ranlib.o arsup.o rename.o binemul.o emul_vanilla.o 
> > bucomm.o version.o filemode.o  ../bfd/.libs/libbfd.a 
> > -L/mnt/data_2/adahl/src/OSELAS.Toolchain/platform-arm-v5te-linux-gnueabi-
> > gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized/build-cross/binutils-2.30-build/zlib
> >  -lz ../libiberty/libiberty.a -lfl -ldl
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See  for instructions.
> > Makefile:918: recipe for target 'incremental.o' failed
> > make[5]: *** [incremental.o] Error 1
> > make[5]: *** Waiting for unfinished jobs
> This is a bug in gcc on your build host. What distribution (and version)
> are you using and what is the output of 'gcc --version'?
> 
> > 
> > Third try, build another toolchain, still with icecc:
> > 
> >   ./build_one.sh arm-1136jfs-linux-gnueabihf
> > 
> > Result (failed):
> > 
> > *** Error in `/usr/lib/gcc/x86_64-linux-gnu/6/cc1plus': corrupted size vs.

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released

2018-02-13 Thread Michael Olbrich 
Hi,

On Tue, Feb 13, 2018 at 01:41:59PM +0100, Alexander Dahl wrote:
> I had several problems compiling the new toolchain, the main one like in the 
> first example, see below.
> 
> Am Montag, 12. Februar 2018, 16:51:54 CET schrieb Michael Olbrich:
> > Download the release here:
> > https://public.pengutronix.de/oselas/toolchain/
> 
> I didn't download a prebuilt release, but tried to build it myself from Git. 
> Host is on Debian 9 (stretch), amd64, using icecc:
> 
>   git clean -dxf
>   git checkout v2018.02.0
>   ln -s /usr/local/bin/ptxdist-2018.02.0 p
>   make -f build_all_v2.mk
> 
> This ends with:
> 
> ---
> target: 
> oselas.toolchain-2018.02.0-powerpc-603e-linux-gnu-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo9+1_amd64.deb
> ---
> 
> mkdir: cannot create directory '/mnt//data-temp': Permission denied   
> mkdir: cannot create directory '/mnt//data-temp': Permission denied   
> scripts/make_deb.sh: line 37: /mnt//data-temp/debian/control: No such file or 
> directory
> scripts/make_deb.sh: line 52: /mnt//data-temp/debian/changelog: No such file 
> or directory
> scripts/make_deb.sh: line 59: /mnt//data-temp/debian/compat: No such file or 
> directory
> Copy data...
> tar: /mnt//data-temp/tmp: Cannot open: No such file or directory
> tar: Error is not recoverable: exiting now
> scripts/make_deb.sh: line 67: cd: /mnt//data-temp: No such file or directory
> Generate dependencies...
> dh_shlibdeps: cannot read debian/control: No such file or directory
> 
> /mnt/data_2/adahl/src/OSELAS.Toolchain/rules/image-toolchain-deb.make:28: 
> recipe for target 
> '/mnt/data_2/adahl/src/OSELAS.Toolchain/dist/oselas.toolchain-2018.02.0-powerpc-603e-linux-gnu-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo9+1_amd64.deb'
>  failed
> make: *** 
> [/mnt/data_2/adahl/src/OSELAS.Toolchain/dist/oselas.toolchain-2018.02.0-powerpc-603e-linux-gnu-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo9+1_amd64.deb]
>  Error 2
> build_all_v2.mk:49: die Regel für Ziel 
> „gstate/powerpc-603e-linux-gnu-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized.build“
>  scheiterte
> make: *** 
> [gstate/powerpc-603e-linux-gnu-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized.build]
>  Fehler 2
> make -f build_all_v2.mk  3545,92s user 325,01s system 164% cpu 39:07,55 total

Hmm, generating Debian packages is not widely tested outside my local
setup, but it should work. Can you add 'set -x' at the beginning of the
main() function in scripts/make_deb.sh and send the output?

> Second try, just building one toolchain:
> 
>   ./build_one.sh v5te
> 
> Result (the failing part):
> 
> In file included from /usr/include/c++/6/vector:69:0,
>  from ../../binutils-2.30/gold/options.h:44,
>  from ../../binutils-2.30/gold/incremental.cc:30:
> /usr/include/c++/6/bits/vector.tcc: In member function 'void std::vector<_Tp, 
> _Alloc>::_M_default_append(std::vector<_Tp, _Alloc>::size_type) [with _Tp = 
> long unsigned int; _Alloc = std::allocator]':
> /usr/include/c++/6/bits/vector.tcc:586:5: internal compiler error: in 
> gt_ggc_mx_symtab_node, at gtype-desc.c:1773
>  }
>  ^
> libtool: link: gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow 
> -Wstack-usage=262144 -I../../binutils-2.30/binutils/../zlib -g -O2 
> -static-libstdc++ -static-libgcc -o ar arparse.o arlex.o ar.o not-ranlib.o 
> arsup.o rename.o binemul.o emul_vanilla.o bucomm.o version.o filemode.o  
> ../bfd/.libs/libbfd.a 
> -L/mnt/data_2/adahl/src/OSELAS.Toolchain/platform-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized/build-cross/binutils-2.30-build/zlib
>  -lz ../libiberty/libiberty.a -lfl -ldl
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See  for instructions.
> Makefile:918: recipe for target 'incremental.o' failed
> make[5]: *** [incremental.o] Error 1
> make[5]: *** Waiting for unfinished jobs

This is a bug in gcc on your build host. What distribution (and version)
are you using and what is the output of 'gcc --version'?

> Third try, build another toolchain, still with icecc:
> 
>   ./build_one.sh arm-1136jfs-linux-gnueabihf
> 
> Result (failed):
> 
> *** Error in `/usr/lib/gcc/x86_64-linux-gnu/6/cc1plus': corrupted size vs. 
> prev_size: 0x04723fe0 ***
> === Backtrace: =
> /lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x7f11d1d7dbcb]
> /lib/x86_64-linux-gnu/libc.so.6(+0x76f96)[0x7f11d1d83f96]
> /lib/x86_64-linux-gnu/libc.so.6(+0x77388)[0x7f11d1d84388]
> /lib/x86_64-linux-gnu/libc.so.6(+0x78dca)[0x7f11d1d85dca]
>

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released

2018-02-13 Thread Alexander Dahl 
Hei hei,

I had several problems compiling the new toolchain, the main one like in the 
first example, see below.

Am Montag, 12. Februar 2018, 16:51:54 CET schrieb Michael Olbrich:
> Download the release here:
> https://public.pengutronix.de/oselas/toolchain/

I didn't download a prebuilt release, but tried to build it myself from Git. 
Host is on Debian 9 (stretch), amd64, using icecc:

  git clean -dxf
  git checkout v2018.02.0
  ln -s /usr/local/bin/ptxdist-2018.02.0 p
  make -f build_all_v2.mk

This ends with:

---
target: 
oselas.toolchain-2018.02.0-powerpc-603e-linux-gnu-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo9+1_amd64.deb
---

mkdir: cannot create directory '/mnt//data-temp': Permission denied   
mkdir: cannot create directory '/mnt//data-temp': Permission denied   
scripts/make_deb.sh: line 37: /mnt//data-temp/debian/control: No such file or 
directory
scripts/make_deb.sh: line 52: /mnt//data-temp/debian/changelog: No such file or 
directory
scripts/make_deb.sh: line 59: /mnt//data-temp/debian/compat: No such file or 
directory
Copy data...
tar: /mnt//data-temp/tmp: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
scripts/make_deb.sh: line 67: cd: /mnt//data-temp: No such file or directory
Generate dependencies...
dh_shlibdeps: cannot read debian/control: No such file or directory

/mnt/data_2/adahl/src/OSELAS.Toolchain/rules/image-toolchain-deb.make:28: 
recipe for target 
'/mnt/data_2/adahl/src/OSELAS.Toolchain/dist/oselas.toolchain-2018.02.0-powerpc-603e-linux-gnu-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo9+1_amd64.deb'
 failed
make: *** 
[/mnt/data_2/adahl/src/OSELAS.Toolchain/dist/oselas.toolchain-2018.02.0-powerpc-603e-linux-gnu-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized_2018.02.0-0ptx1~bpo9+1_amd64.deb]
 Error 2
build_all_v2.mk:49: die Regel für Ziel 
„gstate/powerpc-603e-linux-gnu-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized.build“
 scheiterte
make: *** 
[gstate/powerpc-603e-linux-gnu-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized.build]
 Fehler 2
make -f build_all_v2.mk  3545,92s user 325,01s system 164% cpu 39:07,55 total



Second try, just building one toolchain:

  ./build_one.sh v5te

Result (the failing part):

In file included from /usr/include/c++/6/vector:69:0,
 from ../../binutils-2.30/gold/options.h:44,
 from ../../binutils-2.30/gold/incremental.cc:30:
/usr/include/c++/6/bits/vector.tcc: In member function 'void std::vector<_Tp, 
_Alloc>::_M_default_append(std::vector<_Tp, _Alloc>::size_type) [with _Tp = 
long unsigned int; _Alloc = std::allocator]':
/usr/include/c++/6/bits/vector.tcc:586:5: internal compiler error: in 
gt_ggc_mx_symtab_node, at gtype-desc.c:1773
 }
 ^
libtool: link: gcc -W -Wall -Wstrict-prototypes -Wmissing-prototypes -Wshadow 
-Wstack-usage=262144 -I../../binutils-2.30/binutils/../zlib -g -O2 
-static-libstdc++ -static-libgcc -o ar arparse.o arlex.o ar.o not-ranlib.o 
arsup.o rename.o binemul.o emul_vanilla.o bucomm.o version.o filemode.o  
../bfd/.libs/libbfd.a 
-L/mnt/data_2/adahl/src/OSELAS.Toolchain/platform-arm-v5te-linux-gnueabi-gcc-7.3.1-glibc-2.27-binutils-2.30-kernel-4.15-sanitized/build-cross/binutils-2.30-build/zlib
 -lz ../libiberty/libiberty.a -lfl -ldl
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
Makefile:918: recipe for target 'incremental.o' failed
make[5]: *** [incremental.o] Error 1
make[5]: *** Waiting for unfinished jobs



Third try, build another toolchain, still with icecc:

  ./build_one.sh arm-1136jfs-linux-gnueabihf

Result (failed):

*** Error in `/usr/lib/gcc/x86_64-linux-gnu/6/cc1plus': corrupted size vs. 
prev_size: 0x04723fe0 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bcb)[0x7f11d1d7dbcb]
/lib/x86_64-linux-gnu/libc.so.6(+0x76f96)[0x7f11d1d83f96]
/lib/x86_64-linux-gnu/libc.so.6(+0x77388)[0x7f11d1d84388]
/lib/x86_64-linux-gnu/libc.so.6(+0x78dca)[0x7f11d1d85dca]
/lib/x86_64-linux-gnu/libc.so.6(__libc_calloc+0x27b)[0x7f11d1d88b4b]
/usr/lib/gcc/x86_64-linux-gnu/6/cc1plus(xcalloc+0x21)[0x118ea81]
/usr/lib/gcc/x86_64-linux-gnu/6/cc1plus(_Z27delete_trivially_dead_insnsP8rtx_insni+0x53)[0x104d4c3]
/usr/lib/gcc/x86_64-linux-gnu/6/cc1plus[0x1054d0a]
/usr/lib/gcc/x86_64-linux-gnu/6/cc1plus(_Z16execute_one_passP8opt_pass+0x163)[0xa25f23]
/usr/lib/gcc/x86_64-linux-gnu/6/cc1plus[0xa26468]
/usr/lib/gcc/x86_64-linux-gnu/6/cc1plus[0xa2647a]
/usr/lib/gcc/x86_64-linux-gnu/6/cc1plus(_Z17execute_pass_listP8functionP8opt_pass+0x15)[0xa264c5]

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released

2018-02-13 Thread Michael Olbrich 
On Tue, Feb 13, 2018 at 11:00:48AM +0100, Roland Hieber wrote:
> On 12.02.2018 16:51, Michael Olbrich wrote:
> >  - gcc 7.3
> 
> Thank you! This means we get retpoline support with gcc?

Yes, but that's x86_64 only for now, so probably not relevant for most
embedded systems.

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- |

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released

2018-02-13 Thread Roland Hieber 
On 12.02.2018 16:51, Michael Olbrich wrote:
>  - gcc 7.3

Thank you! This means we get retpoline support with gcc?

 - Roland

___
ptxdist mailing list
ptxdist@pengutronix.de

[ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2018.02.0 released

2018-02-12 Thread Michael Olbrich 
Hi,

I'm happy to announce that I've just released OSELAS.Toolchain-2018.02.0.

This is a major release with significant changes. All components of the
primary toolchains have been updated to the latest versions. The highlights
are:
 - gcc 7.3
 - glibc 2.27
 - binutils 2.30
 - kernel headers 4.15
 - gdb 8.1

The Cortex-A8 toolchains have been removed. Please use the ARM v7a
Toolchains instead. The Cortex-M3 and Cortex-M4 toochains have been
replaces by the more general ARM v7m and v7em toolchains.

Download the release here:
https://public.pengutronix.de/oselas/toolchain/

Enjoy,
Michael Olbrich

-- 
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- |


signature.asc
Description: PGP signature
___
ptxdist mailing list
ptxdist@pengutronix.de