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

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

[Michael Olbrich]

Hi,

I'm happy to announce that I've just released OSELAS.Toolchain-2016.06.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 5.4.0
 - glibc 2.23
 - kernel headers 4.6
 - gdb 7.11

The old AVR toolchains have been removed. They have been unmodified for a
long time, so the old releases can be used.
One new toolchain was added for arm-cortexm4-uclinuxeabihf.

Download the release here:
http://www.pengutronix.de/oselas/toolchain/download/

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

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

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

[Clemens Gruber]

Hi,

On Wed, Jun 22, 2016 at 02:10:06PM +0200, Michael Olbrich wrote:
> Hi,
> 
> I'm happy to announce that I've just released OSELAS.Toolchain-2016.06.0.

Nice, thank you!

I am getting an error during the cross-gcc build however.

Here is the last part of the build log:

(snip)

Exporting license information...
'/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/sysroot-arm-v7a-linux-gnueabihf/usr/lib/libgcc_s.so' -> '../../../arm-v7a-linux-gnueabihf/lib/libgcc_s.so'
'/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/sysroot-arm-v7a-linux-gnueabihf/usr/lib/libgcc_s.so.1' -> '../../../arm-v7a-linux-gnueabihf/lib/libgcc_s.so.1'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/sysroot-arm-v7a-linux-gnueabihf/usr/lib/libgomp.so'
'libgomp.so' -> '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/sysroot-arm-v7a-linux-gnueabihf/usr/lib/libgomp.so'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/sysroot-arm-v7a-linux-gnueabihf/usr/lib/libgomp.so.1'
'libgomp.so.1' -> '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/sysroot-arm-v7a-linux-gnueabihf/usr/lib/libgomp.so.1'
'/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/sysroot-arm-v7a-linux-gnueabihf/usr/lib/libgomp.so.1.0.0' -> '../../../arm-v7a-linux-gnueabihf/lib/libgomp.so.1.0.0'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/sysroot-arm-v7a-linux-gnueabihf/usr/lib/libstdc++.so'
'libstdc++.so' -> '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/sysroot-arm-v7a-linux-gnueabihf/usr/lib/libstdc++.so'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/sysroot-arm-v7a-linux-gnueabihf/usr/lib/libstdc++.so.6'
'libstdc++.so.6' -> '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/sysroot-arm-v7a-linux-gnueabihf/usr/lib/libstdc++.so.6'
'/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/sysroot-arm-v7a-linux-gnueabihf/usr/lib/libstdc++.so.6.0.21' -> '../../../arm-v7a-linux-gnueabihf/lib/libstdc++.so.6.0.21'
'/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/sysroot-arm-v7a-linux-gnueabihf/usr/lib/libstdc++.so.6.0.21-gdb.py' -> '../../../arm-v7a-linux-gnueabihf/lib/libstdc++.so.6.0.21-gdb.py'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/libexec/gcc/arm-v7a-linux-gnueabihf/5.4.0/liblto_plugin.la'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/lib/libcc1.la'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/lib/gcc/arm-v7a-linux-gnueabihf/5.4.0/plugin/libcc1plugin.la'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/arm-v7a-linux-gnueabihf/lib/libatomic.la'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/arm-v7a-linux-gnueabihf/lib/libgomp.la'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/arm-v7a-linux-gnueabihf/lib/libitm.la'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/arm-v7a-linux-gnueabihf/lib/libubsan.la'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/arm-v7a-linux-gnueabihf/lib/libsupc++.la'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/arm-v7a-linux-gnueabihf/lib/libasan.la'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/arm-v7a-linux-gnueabihf/lib/libstdc++.la'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/arm-v7a-linux-gnueabihf/lib/libgomp-plugin-host_nonshm.la'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/arm-v7a-linux-gnueabihf/lib/libstdc++fs.la'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/arm-v7a-linux-gnueabihf/lib/debug/libstdc++.la'
removed '/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/arm-v7a-linux-gnueabihf/lib/debug/libstdc++fs.la'
sed -i -e 's;;;' \
	/opt/OSELAS.Toolchain-2016.06.0/arm-v7a-linux-gnueabihf/gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/lib/gcc/arm-v7a-linux-gnueabihf/5.4.0/install-tools/mkheaders.conf
sed: -e expression #1, char 0: no previous regular expression
make: *** [/home/clemens/Dev/toolchain/rules/cross-gcc.make:167: /home/clemens/Dev/toolchain/platform-arm-v7a-linux-gnueabihf-gcc-5.4.0-glibc-2.23-binutils-2.26-kernel-4.6-sanitized/state/cross-gcc.install] Error 1

--

Any idea why that sed error is occuring?

I am building this on ArchLinux and sed is a GNU sed with version 4.2.2.
My host GCC is version 6.1.1 20160602.

Thanks,
Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

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

[Clemens Gruber]

On Wed, Jun 22, 2016 at 03:22:30PM +0200, Clemens Gruber wrote:
> Hi,
> 
> On Wed, Jun 22, 2016 at 02:10:06PM +0200, Michael Olbrich wrote:
> > Hi,
> > 
> > I'm happy to announce that I've just released OSELAS.Toolchain-2016.06.0.
> 
> Nice, thank you!
> 
> I am getting an error during the cross-gcc build however.
> 
> Here is the last part of the build log:
> 
> (snip)

Reverting commit 334aa73563 ("cleanup sysroot/destdir handling") fixes
the build error!

Regards,
Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

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

[Michael Olbrich]

Hi,

On Wed, Jun 22, 2016 at 03:22:30PM +0200, Clemens Gruber wrote:
> On Wed, Jun 22, 2016 at 02:10:06PM +0200, Michael Olbrich wrote:
> > Hi,
> > 
> > I'm happy to announce that I've just released OSELAS.Toolchain-2016.06.0.
> 
> Nice, thank you!
> 
> I am getting an error during the cross-gcc build however.
> 
> Here is the last part of the build log:

It works if you use the build_one.sh script :-/.

Try this (untested but I think you get the idea):

diff --git a/rules/cross-gcc.make b/rules/cross-gcc.make
index 00da7a008731..4599f47c7cf7 100644
--- a/rules/cross-gcc.make
+++ b/rules/cross-gcc.make
@@ -193,8 +193,10 @@ $(STATEDIR)/cross-gcc.install: $(STATEDIR)/cross-gcc.report
 	done
 
 	@find $(PTXCONF_SYSROOT_CROSS) -name "*.la" -print0 | xargs -0 rm -v -f
+ifneq ($(call remove_quotes,$(PTXCONF_DESTDIR),)
 	sed -i -e 's;$(call remove_quotes,$(PTXCONF_DESTDIR));;' \
 		$(PTXCONF_SYSROOT_CROSS)/lib/gcc/$(PTXCONF_GNU_TARGET)/$(CROSS_GCC_VERSION)/install-tools/mkheaders.conf
+endif
 
 	@$(call touch)
 

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

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

[Bruno Thomsen]

Hi,

I had the same compile issue on a Fedora 23 host but got Michaels patch working with a minor ")" tweak.
Attached working patch just-in-case somebody stumble across the same issue.

/Bruno


diff --git a/rules/cross-gcc.make b/rules/cross-gcc.make
index 00da7a0..068447c 100644
--- a/rules/cross-gcc.make
+++ b/rules/cross-gcc.make
@@ -193,8 +193,10 @@ $(STATEDIR)/cross-gcc.install: $(STATEDIR)/cross-gcc.report
        done
 
        @find $(PTXCONF_SYSROOT_CROSS) -name "*.la" -print0 | xargs -0 rm -v -f
+ifneq ($(call remove_quotes, $(PTXCONF_DESTDIR)),)
        sed -i -e 's;$(call remove_quotes,$(PTXCONF_DESTDIR));;' \
                $(PTXCONF_SYSROOT_CROSS)/lib/gcc/$(PTXCONF_GNU_TARGET)/$(CROSS_GCC_VERSION)/install-tools/mkheaders.conf
+endif
 
        @$(call touch)

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

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

[m.olbrich]

On Tue, Jun 28, 2016 at 12:58:35PM +0000, Bruno Thomsen wrote:
> I had the same compile issue on a Fedora 23 host but got Michaels patch working with a minor ")" tweak.
> Attached working patch just-in-case somebody stumble across the same issue.

Thanks for testing this.

I've pushed this (with the extra ')') to master.

Have you noticed anything else? I'll probably create a stable release for
this. It would be great if I got some feedback if there are anny other
issues that should be fixed.

Michael

> diff --git a/rules/cross-gcc.make b/rules/cross-gcc.make
> index 00da7a0..068447c 100644
> --- a/rules/cross-gcc.make
> +++ b/rules/cross-gcc.make
> @@ -193,8 +193,10 @@ $(STATEDIR)/cross-gcc.install: $(STATEDIR)/cross-gcc.report
>         done
>  
>         @find $(PTXCONF_SYSROOT_CROSS) -name "*.la" -print0 | xargs -0 rm -v -f
> +ifneq ($(call remove_quotes, $(PTXCONF_DESTDIR)),)
>         sed -i -e 's;$(call remove_quotes,$(PTXCONF_DESTDIR));;' \
>                 $(PTXCONF_SYSROOT_CROSS)/lib/gcc/$(PTXCONF_GNU_TARGET)/$(CROSS_GCC_VERSION)/install-tools/mkheaders.conf
> +endif
>  
>         @$(call touch)
> 

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

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

[Ladislav Michl]

On Thu, Jun 30, 2016 at 09:10:18AM +0200, m.olbrich@pengutronix.de wrote:
> On Tue, Jun 28, 2016 at 12:58:35PM +0000, Bruno Thomsen wrote:
> > I had the same compile issue on a Fedora 23 host but got Michaels patch working with a minor ")" tweak.
> > Attached working patch just-in-case somebody stumble across the same issue.
> 
> Thanks for testing this.
> 
> I've pushed this (with the extra ')') to master.
> 
> Have you noticed anything else? I'll probably create a stable release for
> this. It would be great if I got some feedback if there are anny other
> issues that should be fixed.

This one? http://article.gmane.org/gmane.comp.embedded.ptxdist.devel/13933
No patch for it yet, I'll give it a try in the evening.

	ladis

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

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

[Michael Olbrich]

On Thu, Jun 30, 2016 at 09:48:49AM +0200, Ladislav Michl wrote:
> On Thu, Jun 30, 2016 at 09:10:18AM +0200, m.olbrich@pengutronix.de wrote:
> > On Tue, Jun 28, 2016 at 12:58:35PM +0000, Bruno Thomsen wrote:
> > > I had the same compile issue on a Fedora 23 host but got Michaels patch working with a minor ")" tweak.
> > > Attached working patch just-in-case somebody stumble across the same issue.
> > 
> > Thanks for testing this.
> > 
> > I've pushed this (with the extra ')') to master.
> > 
> > Have you noticed anything else? I'll probably create a stable release for
> > this. It would be great if I got some feedback if there are anny other
> > issues that should be fixed.
> 
> This one? http://article.gmane.org/gmane.comp.embedded.ptxdist.devel/13933
> No patch for it yet, I'll give it a try in the evening.

I meant issues with the Toolchain.

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

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

[Clemens Gruber]

On Thu, Jun 30, 2016 at 09:10:18AM +0200, m.olbrich@pengutronix.de wrote:
> I've pushed this (with the extra ')') to master.
> 
> Have you noticed anything else? I'll probably create a stable release for
> this. It would be great if I got some feedback if there are anny other
> issues that should be fixed.

Looks good to me!

--

There is only one longstanding issue, which is probably a ptxdist
problem but it is occuring during the toolchain build as well:
The problem seems to be that some _MD5 lines are removed from the config
during clean or at other stages of the build and are then missing if
built again.
For example PTXCONF_GLIBC_HEADERS_MD5, PTXCONF_GLIBC_CRT_MD5, etc.
After ptxdist clean, only PTXCONF_GLIBC_MD5="..." remains and I have to
manually add all other variations for the build to succeed.

I also experienced this problem when building gdbserver in my BSP:
I have to manually add a PTXCONF_GDBSERVER_MD5="" line for ptxdist
targetinstall gdbserver --update-md5 to succeed. It gets removed by
ptxdist again later on. Only PTXCONF_GDB_MD5=".." remains and if I now
enter ptxdist clean gdbserver && ptxdist targetinstall gdbserver, the
build fails again, until I add PTXCONF_GDBSERVER_MD5=".." to the
ptxconfig.

Can you reproduce this?

Thanks,
Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

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

[Michael Olbrich]

On Thu, Jun 30, 2016 at 06:08:39PM +0200, Clemens Gruber wrote:
> There is only one longstanding issue, which is probably a ptxdist
> problem but it is occuring during the toolchain build as well:
> The problem seems to be that some _MD5 lines are removed from the config
> during clean or at other stages of the build and are then missing if
> built again.
> For example PTXCONF_GLIBC_HEADERS_MD5, PTXCONF_GLIBC_CRT_MD5, etc.
> After ptxdist clean, only PTXCONF_GLIBC_MD5="..." remains and I have to
> manually add all other variations for the build to succeed.
> 
> I also experienced this problem when building gdbserver in my BSP:
> I have to manually add a PTXCONF_GDBSERVER_MD5="" line for ptxdist
> targetinstall gdbserver --update-md5 to succeed. It gets removed by
> ptxdist again later on. Only PTXCONF_GDB_MD5=".." remains and if I now
> enter ptxdist clean gdbserver && ptxdist targetinstall gdbserver, the
> build fails again, until I add PTXCONF_GDBSERVER_MD5=".." to the
> ptxconfig.
> 
> Can you reproduce this?

You're saying, that PTXdist modifies the ptxconfig when you run 'ptxdist
clean gdbserver'? I've never seen anything like this. Can you create a
minimal BSP that has this problem and send it to me?

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

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

[Clemens Gruber]

On Fri, Jul 01, 2016 at 08:33:29AM +0200, Michael Olbrich wrote:
> On Thu, Jun 30, 2016 at 06:08:39PM +0200, Clemens Gruber wrote:
> > There is only one longstanding issue, which is probably a ptxdist
> > problem but it is occuring during the toolchain build as well:
> > The problem seems to be that some _MD5 lines are removed from the config
> > during clean or at other stages of the build and are then missing if
> > built again.
> > For example PTXCONF_GLIBC_HEADERS_MD5, PTXCONF_GLIBC_CRT_MD5, etc.
> > After ptxdist clean, only PTXCONF_GLIBC_MD5="..." remains and I have to
> > manually add all other variations for the build to succeed.
> > 
> > I also experienced this problem when building gdbserver in my BSP:
> > I have to manually add a PTXCONF_GDBSERVER_MD5="" line for ptxdist
> > targetinstall gdbserver --update-md5 to succeed. It gets removed by
> > ptxdist again later on. Only PTXCONF_GDB_MD5=".." remains and if I now
> > enter ptxdist clean gdbserver && ptxdist targetinstall gdbserver, the
> > build fails again, until I add PTXCONF_GDBSERVER_MD5=".." to the
> > ptxconfig.
> > 
> > Can you reproduce this?
> 
> You're saying, that PTXdist modifies the ptxconfig when you run 'ptxdist
> clean gdbserver'? I've never seen anything like this. Can you create a
> minimal BSP that has this problem and send it to me?

No, it's as follows:

I think it only appears if I for example change the GDB version of the
BSP. For example, just change your GDB version in the BSP to 7.11.1.
Then run ptxdist clean gdb gdbserver and ptxdist go, which stops with:
ptxdist: error: Wrong md5sum for 'gdbserver'
(/home/clemens/shared-src/gdb-7.11.1.tar.gz)

Nothing wrong so far.

So I run ptxdist go --update-md5 and after that, the error I meant,
appears:
sed: couldn't open temporary file
/usr/local/lib/ptxdist-2016.06.0/rules/sedx2aZZd: Permission denied
ptxdist: error: Could not update md5sum for 'gdbserver': GDBSERVER_MD5
not found

Then I have to add GDBSERVER_MD5="" and run ptxdist go --update-md5
again, which works.

After the build finished, the GDBSERVER_MD5 is still in place.
But the next time I go into ptxdist menu, even if I change nothing, when
exiting, I am asked if I want to save my new configuration and after
that, the GDBSERVER_MD5 entry vanishes.

Please try above steps with anyone of your BSPs, I don't think it
depends upon anything special in the BSP.

Thanks,
Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

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

[Michael Olbrich]

On Fri, Jul 01, 2016 at 10:39:39AM +0200, Clemens Gruber wrote:
> On Fri, Jul 01, 2016 at 08:33:29AM +0200, Michael Olbrich wrote:
> > On Thu, Jun 30, 2016 at 06:08:39PM +0200, Clemens Gruber wrote:
> > > There is only one longstanding issue, which is probably a ptxdist
> > > problem but it is occuring during the toolchain build as well:
> > > The problem seems to be that some _MD5 lines are removed from the config
> > > during clean or at other stages of the build and are then missing if
> > > built again.
> > > For example PTXCONF_GLIBC_HEADERS_MD5, PTXCONF_GLIBC_CRT_MD5, etc.
> > > After ptxdist clean, only PTXCONF_GLIBC_MD5="..." remains and I have to
> > > manually add all other variations for the build to succeed.
> > > 
> > > I also experienced this problem when building gdbserver in my BSP:
> > > I have to manually add a PTXCONF_GDBSERVER_MD5="" line for ptxdist
> > > targetinstall gdbserver --update-md5 to succeed. It gets removed by
> > > ptxdist again later on. Only PTXCONF_GDB_MD5=".." remains and if I now
> > > enter ptxdist clean gdbserver && ptxdist targetinstall gdbserver, the
> > > build fails again, until I add PTXCONF_GDBSERVER_MD5=".." to the
> > > ptxconfig.
> > > 
> > > Can you reproduce this?
> > 
> > You're saying, that PTXdist modifies the ptxconfig when you run 'ptxdist
> > clean gdbserver'? I've never seen anything like this. Can you create a
> > minimal BSP that has this problem and send it to me?
> 
> No, it's as follows:
> 
> I think it only appears if I for example change the GDB version of the
> BSP. For example, just change your GDB version in the BSP to 7.11.1.
> Then run ptxdist clean gdb gdbserver and ptxdist go, which stops with:
> ptxdist: error: Wrong md5sum for 'gdbserver'
> (/home/clemens/shared-src/gdb-7.11.1.tar.gz)
> 
> Nothing wrong so far.
> 
> So I run ptxdist go --update-md5 and after that, the error I meant,
> appears:
> sed: couldn't open temporary file
> /usr/local/lib/ptxdist-2016.06.0/rules/sedx2aZZd: Permission denied
> ptxdist: error: Could not update md5sum for 'gdbserver': GDBSERVER_MD5
> not found
> 
> Then I have to add GDBSERVER_MD5="" and run ptxdist go --update-md5
> again, which works.
> 
> After the build finished, the GDBSERVER_MD5 is still in place.
> But the next time I go into ptxdist menu, even if I change nothing, when
> exiting, I am asked if I want to save my new configuration and after
> that, the GDBSERVER_MD5 entry vanishes.
> 
> Please try above steps with anyone of your BSPs, I don't think it
> depends upon anything special in the BSP.

Now I get it. You cannot update the md5sum for gdbserver with
'--update-md5'. You need to do it manually. gdb and gdbserver share the
md5sum and the kconfig symbol is PTXCONF_GDB_MD5. Run
"md5sum /home/clemens/shared-src/gdb-7.11.1.tar.gz" and enter the result in
'ptxdist menuconfig' or edit the ptxconfig manually to update
PTXCONF_GDB_MD5.

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

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

[Clemens Gruber]

On Fri, Jul 01, 2016 at 12:28:50PM +0200, Michael Olbrich wrote:
> Now I get it. You cannot update the md5sum for gdbserver with
> '--update-md5'. You need to do it manually. gdb and gdbserver share the
> md5sum and the kconfig symbol is PTXCONF_GDB_MD5. Run
> "md5sum /home/clemens/shared-src/gdb-7.11.1.tar.gz" and enter the result in
> 'ptxdist menuconfig' or edit the ptxconfig manually to update
> PTXCONF_GDB_MD5.

Hm, OK, I am entering it manually now, but would this be hard to
implement in ptxdist to automatically set a kconfig symbol if it does
not exist yet?
Same problem appears when updating toolchain components.

And why is the PTXCONF_GDBSERVER_MD5 kconfig symbol removed from ptxconfig when
leaving ptxdist menu?

Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

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

[Michael Olbrich]

Hi,

On Fri, Jul 01, 2016 at 04:25:54PM +0200, Clemens Gruber wrote:
> On Fri, Jul 01, 2016 at 12:28:50PM +0200, Michael Olbrich wrote:
> > Now I get it. You cannot update the md5sum for gdbserver with
> > '--update-md5'. You need to do it manually. gdb and gdbserver share the
> > md5sum and the kconfig symbol is PTXCONF_GDB_MD5. Run
> > "md5sum /home/clemens/shared-src/gdb-7.11.1.tar.gz" and enter the result in
> > 'ptxdist menuconfig' or edit the ptxconfig manually to update
> > PTXCONF_GDB_MD5.
> 
> Hm, OK, I am entering it manually now, but would this be hard to
> implement in ptxdist to automatically set a kconfig symbol if it does
> not exist yet?
> Same problem appears when updating toolchain components.

Updating md5sums with '--update-md5' when updating toolchain components
works for me. I have no idea why this doesn't work for you.

> And why is the PTXCONF_GDBSERVER_MD5 kconfig symbol removed from ptxconfig when
> leaving ptxdist menu?

There is no PTXCONF_GDBSERVER_MD5. In this case gdbserver reuses
PTXCONF_GDB_MD5, which is the reason why '--update-md5' doesn't work here.

'--update-md5' tries to guess where to update the md5. It checks
'PTXCONF_<PKG>_MD5' first. If that cannot be found, it tries to update
'<PKG>_MD5' in <pkg>.make.

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

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

[Clemens Gruber]

Hi,

On Mon, Jul 04, 2016 at 08:35:44AM +0200, Michael Olbrich wrote:
> Updating md5sums with '--update-md5' when updating toolchain components
> works for me. I have no idea why this doesn't work for you.

You explained this in the last paragraph. It's only affecting symbols
like PTXCONF_GDBSERVER_MD5, which should not exist at all.
So that's fine. For PTXCONF_GDB_MD5, --update-md5 works for me too.

What's odd though is that the toolchain build process expects not only
the PTXCONF_<PKG>_MD5 lines but also lines where PKG is CROSS_GCC or
GLIBC_FIRST, GLIBC_HEADERS or GLIBC_CRT.
Only if I add those it continues. And next time I change something via
ptxdist menu, they get cleaned up again (because they should not exist
in the first place).

But then, why are these symbols necessary for the build?
Shouldn't cross-gcc just use PTXCONF_GCC_MD5 and glibc-first just use
PTXCONF_GLIBC_MD5 instead of PTXCONF_GLIBC_FIRST_MD5?

> There is no PTXCONF_GDBSERVER_MD5. In this case gdbserver reuses
> PTXCONF_GDB_MD5, which is the reason why '--update-md5' doesn't work here.

I think it's this very process of reusing kconfig symbols like
PTXCONF_GDB_MD5 during the gdbserver build, which does not work as
expected.

Same behavior as with the toolchain builds. When I change one of the
versions through ptxdist menu and do a clean rebuild, this occurs.

Could this be some kind of fallback if the MD5 hash in PTXCONF_GDB_MD5 
is not correct after the version update, trying other symbol names like
PTXCONF_GDBSERVER_MD5?

Thanks for your help!

Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de