Re: Toolchain Connect sessions
On 25 October 2011 09:54, Michael Hope wrote: > Hi there. Connect is just around the corner. Have a look at: > https://wiki.linaro.org/MichaelHope/Sandbox/Q4.11Plans > > for a summary of the toolchain sessions and hacking topics. None of these sessions except the Yocto one seem to be showing up in the toolchain track schedule at: http://connect.linaro.org/events/event/linaro-connect-q411/#schedule (admittedly one or two are kernel or other team blueprints) -- is this intentional? (Also, should there be a blueprint for the A15 KVM discussion?) -- PMM ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: Toolchain Connect sessions
On 26 October 2011 14:57, Peter Maydell wrote: > On 25 October 2011 09:54, Michael Hope wrote: >> Hi there. Connect is just around the corner. Have a look at: >> https://wiki.linaro.org/MichaelHope/Sandbox/Q4.11Plans >> >> for a summary of the toolchain sessions and hacking topics. > > None of these sessions except the Yocto one seem to be showing > up in the toolchain track schedule at: > http://connect.linaro.org/events/event/linaro-connect-q411/#schedule > (admittedly one or two are kernel or other team blueprints) -- > is this intentional? Ramana has kindly pointed out that I was confused by the UI on that page -- some (but not all!) of the track session displays are too wide for the popup window, so you have to click on the popup and then use the cursor-right key to scroll to see Thursday and Friday... -- PMM ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: [ACTIVITY] WW42
On Tue, Oct 25, 2011 at 4:27 PM, Zhenqiang Chen wrote: >> mkedwards has these scripted up at: >> https://github.com/mkedwards/crosstool-ng/tree/master/scripts/build/companion_libs >> >> We should add these in upstream. I'd rather focus on GCC first, get >> that out as a prototype, then add GDB. > > I tried tried mkedwards's extention. The GDB-cross can build. > >> GCC and similar ship with a copy of zlib. I wonder if we should use that? > > zlib is used to build binutils, which is built before GCC. > If you install a 32-bit binary toolchain on 64-bit system, you might > have link error. By default, there is no 32-bit zlib on 64-bit system. > You have to install 32-bit zlib manually. Yip, but both binutils and GCC include a local copy of the zlib source that can be statically linked in during the build. It might be easier than doing it separetly, especially as zlib is messy to build. > >>> (3) Currently, the embedded toolchain source packages are released >>> as a tarball, which includes gcc, gmp, etc. New scripts are required >>> to support it. >> >> We should check what needs to be done to meet the licenses. All of >> the tarballs used in building the binary are in .build/taraballs. > > I will add scripts to copy the tarballs to .build/tarballs. >From I guess? >>> (4) To make sure the toolchain can run with lower version glibc like >>> redhat4/5, the embedded toolchain requires lower version native >>> gcc4.3.6 to build it. >> >> Why is this? The RHEL 5 GCC 4.1 builds the glibc compiler just fine. > > There is no problem if users build and run the toolchain on the same platform. > > We expect users can install and use the binary toolchain on systems > without rebuilding it. > E.g. If we build toolchain on Ubuntu 10.4, can users use it on RHEL4? The glibc is more of a concern than the compiler. RHEL 5 is the earliest version we need to support which is GLIBC 2.5 based. Ubuntu 8.10 uses GLIBC 2.8 and might turn on other features like hardening or the stack protector which could cause trouble. I think we should build and test the binary under RHEL 5 itself. -- Michael ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
Re: [ACTIVITY] WW42
>> zlib is used to build binutils, which is built before GCC. >> If you install a 32-bit binary toolchain on 64-bit system, you might >> have link error. By default, there is no 32-bit zlib on 64-bit system. >> You have to install 32-bit zlib manually. > > Yip, but both binutils and GCC include a local copy of the zlib source > that can be statically linked in during the build. It might be easier > than doing it separetly, especially as zlib is messy to build. Are you sure? I check binutils-2.21 source code. There is no zlib related source code like zlib.h. If it has, we should not build zlib separately. (3) Currently, the embedded toolchain source packages are released as a tarball, which includes gcc, gmp, etc. New scripts are required to support it. >>> >>> We should check what needs to be done to meet the licenses. All of >>> the tarballs used in building the binary are in .build/taraballs. >> >> I will add scripts to copy the tarballs to .build/tarballs. > > From I guess? The root cause for this gap is that current embedded toolchain release creates some source packages from internal git server. And the package name is not in standard format: NAME-VERSION. The script will be a workaround to build and test the embedded toolchain. I will work with local team to improve the build process for future release. All the source packages should get from public links with standard format. > The glibc is more of a concern than the compiler. RHEL 5 is the > earliest version we need to support which is GLIBC 2.5 based. Ubuntu > 8.10 uses GLIBC 2.8 and might turn on other features like hardening or > the stack protector which could cause trouble. > > I think we should build and test the binary under RHEL 5 itself. Stack protector is the issue on RHEL5. For us, we should build and test the binary under RHEL5. What do we release: series of toolchains for different versions of Linux or just one which can run on most popular linux versions? If we only release one binary, what's the preferred build system? And we should make sure it can run on different linux systems. Thanks! -Zhenqiang ___ linaro-toolchain mailing list linaro-toolchain@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-toolchain
