Re: [ptxdist] Detect if x86 target is 32 or 64bit?
On Wednesday 04 January 2012 17:59:57 Michael Olbrich wrote: Hi, On Wed, Jan 04, 2012 at 03:27:46PM +0100, Alexander Stein wrote: how can I detect if a x86 target is 32 or 64bit? I'm working on a package rule for gnu-efi and elilo which need to know if it should generate ia32, x86_64 (or ia64) binaries. I just know about PTXCONF_ARCH_X86 but this does not show what I want. There is also PTXCONF_KERNEL_ARCH_X86_64 for 64bit but this needs a linux kernel configured. Any other ideas? This is not yet supported. You'll need to add ARCH_X86_64 and ARCH_IA64 to platforms/architecture.in and set the correct defaults for HAS_HARDFLOAT etc. Send patches :-) I doubt it's the best way to just add ARCH_X86_64 (and maybe ARCH_IA64). A lot of rules files use ifdef PTXCONF_ARCH_X86. So this has to be reworked to be useable in X86_64, as most cases don't make a difference to 32 or 64 Bit. Maybe it's better, to add a 64Bit entry in the optimization. Thoughts? Regards, Alexander -- Dipl.-Inf. Alexander Stein SYS TEC electronic GmbH August-Bebel-Str. 29 D-07973 Greiz Tel: +49-3661-6279-0, Fax: +49-3661-6279-99 eMail:alexander.st...@systec-electronic.com Internet: http://www.systec-electronic.com Managing Director: Dipl.-Phys. Siegmar Schmidt Commercial registry: Amtsgericht Jena, HRB 205563 -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] Detect if x86 target is 32 or 64bit?
On Tue, Jan 31, 2012 at 09:21:30AM +0100, Alexander Stein wrote: On Wednesday 04 January 2012 17:59:57 Michael Olbrich wrote: On Wed, Jan 04, 2012 at 03:27:46PM +0100, Alexander Stein wrote: how can I detect if a x86 target is 32 or 64bit? I'm working on a package rule for gnu-efi and elilo which need to know if it should generate ia32, x86_64 (or ia64) binaries. I just know about PTXCONF_ARCH_X86 but this does not show what I want. There is also PTXCONF_KERNEL_ARCH_X86_64 for 64bit but this needs a linux kernel configured. Any other ideas? This is not yet supported. You'll need to add ARCH_X86_64 and ARCH_IA64 to platforms/architecture.in and set the correct defaults for HAS_HARDFLOAT etc. Send patches :-) I doubt it's the best way to just add ARCH_X86_64 (and maybe ARCH_IA64). A lot of rules files use ifdef PTXCONF_ARCH_X86. So this has to be reworked to be useable in X86_64, as most cases don't make a difference to 32 or 64 Bit. Maybe it's better, to add a 64Bit entry in the optimization. Thoughts? I have no idea which way will be easier to implement. But I don't think adding to the optimization is the best. There will be places where you need to separate 32 vs 64 bit (e.g. SIZEOF_LONG_DOUBLE). So I guess you should start with a (ARCH_X86_32|ARCH_X86_64) choice and check if any ifdef PTXCONF_ARCH_X86 need to be changed. If there are few/no uses of ARCH_X86 left then we can rename ARCH_X86_32 to ARCH_X86. 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] [PATCH v3] replace umkimage by u-boot sources
On Sat, Jan 28, 2012 at 12:38:08AM +0100, Andreas Bießmann wrote: This patch removes the forked mkimage u-boot tool and uses the mainline u-boot code to build this tool. Signed-off-by: Andreas Bießmann andr...@biessmann.de --- Changes since v1: * add ROOTFS_FW_ENV_CONFIG parameter which installes /etc/fw_env.config * changes requested by Michael Changes since v2: * fix wrong 'fw_saveenv' command - use correct 'fw_setenv' ...f8dcdbe5c690c-compiler.h-add-uint-typedef.patch | 26 -- patches/u-boot-mkimage-2010.03-1/series|1 - platforms/hosttools.in |2 +- platforms/image_uimage.in |8 +- platforms/kernel.in|2 +- rules/host-u-boot-tools.in |5 + rules/host-u-boot-tools.make | 35 + rules/host-umkimage.in |8 -- rules/host-umkimage.make | 37 - rules/rootfs.in|9 ++ rules/rootfs.make |3 + rules/templates/template-kernel-in |2 +- rules/u-boot-tools.in | 32 rules/u-boot-tools.make| 81 rules/umkimage.in |8 -- rules/umkimage.make| 66 16 files changed, 172 insertions(+), 153 deletions(-) delete mode 100644 patches/u-boot-mkimage-2010.03-1/b050c72d52c4e30d5b978ab6758f8dcdbe5c690c-compiler.h-add-uint-typedef.patch delete mode 100644 patches/u-boot-mkimage-2010.03-1/series create mode 100644 rules/host-u-boot-tools.in create mode 100644 rules/host-u-boot-tools.make delete mode 100644 rules/host-umkimage.in delete mode 100644 rules/host-umkimage.make create mode 100644 rules/u-boot-tools.in create mode 100644 rules/u-boot-tools.make delete mode 100644 rules/umkimage.in delete mode 100644 rules/umkimage.make diff --git a/patches/u-boot-mkimage-2010.03-1/b050c72d52c4e30d5b978ab6758f8dcdbe5c690c-compiler.h-add-uint-typedef.patch b/patches/u-boot-mkimage-2010.03-1/b050c72d52c4e30d5b978ab6758f8dcdbe5c690c-compiler.h-add-uint-typedef.patch deleted file mode 100644 index f20a663..000 --- a/patches/u-boot-mkimage-2010.03-1/b050c72d52c4e30d5b978ab6758f8dcdbe5c690c-compiler.h-add-uint-typedef.patch +++ /dev/null @@ -1,26 +0,0 @@ -commit b050c72d52c4e30d5b978ab6758f8dcdbe5c690c -Author: Mike Frysinger vap...@gentoo.org -Date: Tue Apr 20 05:49:30 2010 -0400 - -compiler.h: add uint typedef - -Recent crc changes started using the uint type in headers that are used -on the build system. This subsequently broke mingw targets as they do not -provide such a type. So add this basic typedef to compiler.h so that we -do not have to worry about this breaking again in the future. - -Signed-off-by: Mike Frysinger vap...@gentoo.org -Signed-off-by: Remy Bohmer li...@bohmer.net - -diff --git a/include/compiler.h b/include/compiler.h -index 332618e..8030bf6 100644 a/include/compiler.h -+++ b/include/compiler.h -@@ -55,6 +55,7 @@ typedef unsigned int uint; - typedef uint8_t __u8; - typedef uint16_t __u16; - typedef uint32_t __u32; -+typedef unsigned int uint; - - #define uswap_16(x) \ - x) 0xff00) 8) | \ diff --git a/patches/u-boot-mkimage-2010.03-1/series b/patches/u-boot-mkimage-2010.03-1/series deleted file mode 100644 index dbf4bb4..000 --- a/patches/u-boot-mkimage-2010.03-1/series +++ /dev/null @@ -1 +0,0 @@ -b050c72d52c4e30d5b978ab6758f8dcdbe5c690c-compiler.h-add-uint-typedef.patch diff --git a/platforms/hosttools.in b/platforms/hosttools.in index 155b30b..e9ce0fc 100644 --- a/platforms/hosttools.in +++ b/platforms/hosttools.in @@ -19,7 +19,7 @@ source rules/host-mtd-utils.in source rules/host-mtools.in source rules/host-openssl.in source rules/host-squashfs-tools.in -source rules/host-umkimage.in +source rules/host-u-boot-tools.in source rules/host-util-linux-ng.in source rules/host-xl-tools.in source rules/host-xz.in diff --git a/platforms/image_uimage.in b/platforms/image_uimage.in index 62119c4..719793d 100644 --- a/platforms/image_uimage.in +++ b/platforms/image_uimage.in @@ -3,7 +3,7 @@ menuconfig IMAGE_UIMAGE bool prompt Generate images/uRamdisk - select HOST_UMKIMAGE + select HOST_U_BOOT_TOOLS select IMAGE_EXT2 select IMAGE_EXT2_GZIP help @@ -21,16 +21,16 @@ config IMAGE_UIMAGE_NAME config IMAGE_UIMAGE_EXTRA_ARGS string default - prompt extra arguments passed to umkimage + prompt extra arguments passed to mkimage help - If needed you can add extra arguments for umkimage here + If needed you can add extra arguments
Re: [ptxdist] [PATCH] add patch for building at91bootstrap with gcc 4.6.x
Hei Michael,
Am 30.01.2012 15:20, schrieb Michael Olbrich:
See my mail from January 13th, where I described the problem. It occurs
with the OSELAS toolchain 2011.11.0 compiling for arm-v5te.
Yes, I tried that and didn't get any build error. Which at91bootstrap
config do I select to this error?
Okay I try to give some more information. Meanwhile I switched to the
2011.11.1 toolchain, but the error can be reproduced with this:
arm-v5te-linux-gnueabi-gcc -nostartfiles -nostdlib
-Wl,-Map=nandflash_at91sam9g20ek.map,--cref -T
./../../elf32-littlearm.lds -Ttext 0x20 -n -o
nandflash_at91sam9g20ek.elf crt0_gnu.o at91sam9g20ek.o main.o gpio.o
pmc.o debug.o sdramc.o nandflash.o _udivsi3.o _umodsi3.o div0.o udiv.o
string.o
/home/adahl/opt/OSELAS.Toolchain-2011.11.1/arm-v5te-linux-gnueabi/gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/bin/../lib/gcc/arm-v5te-linux-gnueabi/4.6.2/../../../../arm-v5te-linux-gnueabi/bin/ld:
section .text.startup loaded at [00200e84,00200eab] overlaps section
data loaded at [00200e84,00200f47]
collect2: ld returned 1 exit status
You see the toolchain is for arm-v5te-linux-gnueabi and uses gcc 4.6,
it's the toolchain build from the tag v2011.11.1 from the git repo
http://git.pengutronix.de/?p=OSELAS.Toolchain.git;a=summary and the
toolchain is built on the same up-to-date i686 Debian Squeeze VMware
virtual machine where I try to compile the at91bootstrap.
In the platformconfig I chose this:
% grep -irn bootstrap configs
configs/arm-ncl/platformconfig:124:PTXCONF_AT91BOOTSTRAP=y
configs/arm-ncl/platformconfig:125:PTXCONF_AT91BOOTSTRAP_VERSION=1.16
configs/arm-ncl/platformconfig:126:PTXCONF_AT91BOOTSTRAP_MD5=2d222312cf0af81c56db8747d6a38c7c
configs/arm-ncl/platformconfig:127:PTXCONF_AT91BOOTSTRAP_CONFIG=at91sam9g20ek
configs/arm-ncl/platformconfig:128:#
PTXCONF_AT91BOOTSTRAP_BOOT_DATAFLASH is not set
configs/arm-ncl/platformconfig:129:PTXCONF_AT91BOOTSTRAP_BOOT_NAND=y
configs/arm-ncl/platformconfig:130:# PTXCONF_AT91BOOTSTRAP2 is not set
I did a `ptxdist clean at91bootstrap` before and made sure there are no
customized rules or patches used, it's at91bootstrap as it comes with
ptxdist 2012.01.0, which is the version I use for testing this. Do you
need any more information to reproduce this? I attached the
platformconfig, hope this is helpful somehow.
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: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***#
# Automatically generated make config: don't edit
# PTXdist 2012.01.0
#
PTXCONF_PLATFORMCONFIG_VERSION=2012.01.0
PTXCONF__platformconfig_MAGIC__=y
#
#
#
#
# Target Platform Configuration
#
#
#
#
PTXCONF_PLATFORM=at91sam9g20ncl
PTXCONF_PLATFORM_VERSION=1
#
# architecture
#
# PTXCONF_ARCH_ALPHA is not set
# PTXCONF_ARCH_AVR32 is not set
# PTXCONF_ARCH_AVR is not set
PTXCONF_ARCH_ARM=y
# PTXCONF_ARCH_BLACKFIN is not set
# PTXCONF_ARCH_X86 is not set
# PTXCONF_ARCH_MINGW is not set
# PTXCONF_ARCH_PPC is not set
# PTXCONF_ARCH_M68K is not set
# PTXCONF_ARCH_SPARC is not set
# PTXCONF_ARCH_MICROBLAZE is not set
# PTXCONF_ARCH_MIPS is not set
# PTXCONF_ARCH_CRIS is not set
# PTXCONF_ARCH_PARISC is not set
# PTXCONF_ARCH_SH is not set
PTXCONF_ARCH_SUPPORTS_ENDIAN_BIG=y
PTXCONF_ARCH_SUPPORTS_ENDIAN_LITTLE=y
# PTXCONF_ENDIAN_BIG is not set
PTXCONF_ENDIAN_LITTLE=y
# PTXCONF_ARCH_ARM_V6 is not set
# PTXCONF_ARCH_ARM_IWMMXT is not set
# PTXCONF_ARCH_ARM_NEON is not set
# PTXCONF_HAS_HARDFLOAT is not set
PTXCONF_HAS_MMU=y
PTXCONF_SIZEOF_LONG_DOUBLE=8
PTXCONF_ARCH_STRING=arm
#
# paths directories
#
PTXCONF_SYSROOT_TARGET=${PTXDIST_PLATFORMDIR}/sysroot-target
PTXCONF_SYSROOT_HOST=${PTXDIST_PLATFORMDIR}/sysroot-host
PTXCONF_SYSROOT_CROSS=${PTXDIST_PLATFORMDIR}/sysroot-cross
#
# toolchain
#
PTXCONF_CROSSCHAIN_VENDOR=OSELAS.Toolchain-2011.11.1
PTXCONF_CROSSCHAIN_CHECK=4.6.2
PTXCONF_LIBC_GLIBC=y
# PTXCONF_LIBC_UCLIBC is not set
PTXCONF_GLIBC_VERSION=2.14.1
PTXCONF_GNU_TARGET=arm-v5te-linux-gnueabi
PTXCONF_COMPILER_PREFIX=${PTXCONF_GNU_TARGET}-
PTXCONF_COMPILER_PREFIX_KERNEL=${PTXCONF_COMPILER_PREFIX}
PTXCONF_COMPILER_PREFIX_BOOTLOADER=${PTXCONF_COMPILER_PREFIX}
#
# extra toolchain options
#
PTXCONF_TARGET_EXTRA_CPPFLAGS=
PTXCONF_TARGET_EXTRA_CFLAGS=-Wcast-align
PTXCONF_TARGET_EXTRA_CXXFLAGS=-Wcast-align
PTXCONF_TARGET_EXTRA_LDFLAGS=
PTXCONF_KERNEL=y
# PTXCONF_KERNEL_INSTALL is not set
PTXCONF_KERNEL_MODULES=y
PTXCONF_KERNEL_MODULES_INSTALL=y
PTXCONF_KERNEL_MODULES_BUILD=modules
PTXCONF_KERNEL_VERSION=2.6.36.4
PTXCONF_KERNEL_MD5=c05dd941d0e249695e9f7256e1bf
PTXCONF_KERNEL_ARCH_STRING=arm
# PTXCONF_KERNEL_IMAGE_BZ is not set
# PTXCONF_KERNEL_IMAGE_Z is not set
PTXCONF_KERNEL_IMAGE_U=y
# PTXCONF_KERNEL_IMAGE_VM
[ptxdist] xmlrpc-c compile issue
Hi all, I am trying to migrate from an old ptxdist-2011.01.0 to ptxdist-2012.01.0. Doing so, I encounter an issue with the xmlrpc-c package. I tried to revert to the xmlrpc-c version to the one used in the old version (xmlrpc-c-1.06.38). It does not work either (same patches are applied). It seems that the automake thing is too old to work properly. Problem is that I'm not an expert in this. Below is the log when it fails. Cheers, Ben --88888 patchin: autogen: running '/usr/local/lib/ptxdist-2012.01.0/patches/xmlrpc-c-1.06.41/autogen.sh' automake: no `Makefile.am' found for any configure output libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. configure.in:4: warning: The macro `AM_CONFIG_HEADER' is obsolete. configure.in:4: You should run autoupdate. aclocal.m4:9006: AM_CONFIG_HEADER is expanded from... configure.in:4: the top level configure.in:253: warning: The macro `AC_STDC_HEADERS' is obsolete. configure.in:253: You should run autoupdate. ../../lib/autoconf/oldnames.m4:75: AC_STDC_HEADERS is expanded from... configure.in:253: the top level configure.in:308: warning: The macro `AC_TRY_COMPILE' is obsolete. configure.in:308: You should run autoupdate. ../../lib/autoconf/general.m4:2615: AC_TRY_COMPILE is expanded from... configure.in:308: the top level configure.in:321: warning: The macro `AC_TRY_COMPILE' is obsolete. configure.in:321: You should run autoupdate. ../../lib/autoconf/general.m4:2615: AC_TRY_COMPILE is expanded from... configure.in:321: the top level configure.in:634: warning: The macro `AM_PROG_LIBTOOL' is obsolete. configure.in:634: You should run autoupdate. aclocal.m4:129: AM_PROG_LIBTOOL is expanded from... configure.in:634: the top level configure.in:644: warning: AC_OUTPUT should be used without arguments. configure.in:644: You should run autoupdate. patchin: autogen: done patchin: fixup: XX/platform-X/build-target/xmlrpc-c-1.06.41/configure XX/platform-X/build-target/xmlrpc-c-1.06.41/ltmain.sh patchin: fixup: done finished target xmlrpc-c.extract target: xmlrpc-c.prepare checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for arm-v5te-linux-gnueabi-strip... arm-v5te-linux-gnueabi-strip checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... x86_64-host-linux-gnu checking host system type... arm-v5te-linux-gnueabi checking whether to build Wininet client XML transport module... no checking whether to build Curl client XML transport module... yes checking whether to build Libwww client XML transport module... no checking whether to build Abyss server module... yes checking whether to build CGI server module... yes checking whether to build C++ wrappers and tools... no checking for arm-v5te-linux-gnueabi-gcc... arm-v5te-linux-gnueabi-gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... yes checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether arm-v5te-linux-gnueabi-gcc accepts -g... yes checking for arm-v5te-linux-gnueabi-gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of arm-v5te-linux-gnueabi-gcc... none checking for socket... yes checking how to run the C preprocessor... arm-v5te-linux-gnueabi-cpp checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking wchar.h usability... yes checking wchar.h presence... yes checking for wchar.h... yes checking sys/filio.h usability... no checking sys/filio.h presence... no checking for sys/filio.h... no checking sys/ioctl.h usability... yes checking sys/ioctl.h presence... yes checking for sys/ioctl.h... yes checking stdarg.h usability... yes checking stdarg.h presence... yes checking for stdarg.h... yes checking for size_t... yes checking whether va_list is an array... no checking whether compiler has __attribute__... yes checking for vsnprintf... yes checking for wcsncmp... yes checking for setgroups... yes checking for asprintf... yes checking
Re: [ptxdist] [PATCH] add patch for building at91bootstrap with gcc 4.6.x
On Tue, Jan 31, 2012 at 05:54:41PM +0100, Alexander Dahl wrote: Am 30.01.2012 15:20, schrieb Michael Olbrich: See my mail from January 13th, where I described the problem. It occurs with the OSELAS toolchain 2011.11.0 compiling for arm-v5te. Yes, I tried that and didn't get any build error. Which at91bootstrap config do I select to this error? Okay I try to give some more information. Meanwhile I switched to the 2011.11.1 toolchain, but the error can be reproduced with this: arm-v5te-linux-gnueabi-gcc -nostartfiles -nostdlib -Wl,-Map=nandflash_at91sam9g20ek.map,--cref -T ./../../elf32-littlearm.lds -Ttext 0x20 -n -o nandflash_at91sam9g20ek.elf crt0_gnu.o at91sam9g20ek.o main.o gpio.o pmc.o debug.o sdramc.o nandflash.o _udivsi3.o _umodsi3.o div0.o udiv.o string.o /home/adahl/opt/OSELAS.Toolchain-2011.11.1/arm-v5te-linux-gnueabi/gcc-4.6.2-glibc-2.14.1-binutils-2.21.1a-kernel-2.6.39-sanitized/bin/../lib/gcc/arm-v5te-linux-gnueabi/4.6.2/../../../../arm-v5te-linux-gnueabi/bin/ld: section .text.startup loaded at [00200e84,00200eab] overlaps section data loaded at [00200e84,00200f47] collect2: ld returned 1 exit status You see the toolchain is for arm-v5te-linux-gnueabi and uses gcc 4.6, it's the toolchain build from the tag v2011.11.1 from the git repo http://git.pengutronix.de/?p=OSELAS.Toolchain.git;a=summary and the toolchain is built on the same up-to-date i686 Debian Squeeze VMware virtual machine where I try to compile the at91bootstrap. In the platformconfig I chose this: % grep -irn bootstrap configs configs/arm-ncl/platformconfig:124:PTXCONF_AT91BOOTSTRAP=y configs/arm-ncl/platformconfig:125:PTXCONF_AT91BOOTSTRAP_VERSION=1.16 configs/arm-ncl/platformconfig:126:PTXCONF_AT91BOOTSTRAP_MD5=2d222312cf0af81c56db8747d6a38c7c configs/arm-ncl/platformconfig:127:PTXCONF_AT91BOOTSTRAP_CONFIG=at91sam9g20ek configs/arm-ncl/platformconfig:128:# PTXCONF_AT91BOOTSTRAP_BOOT_DATAFLASH is not set configs/arm-ncl/platformconfig:129:PTXCONF_AT91BOOTSTRAP_BOOT_NAND=y configs/arm-ncl/platformconfig:130:# PTXCONF_AT91BOOTSTRAP2 is not set I did a `ptxdist clean at91bootstrap` before and made sure there are no customized rules or patches used, it's at91bootstrap as it comes with ptxdist 2012.01.0, which is the version I use for testing this. Do you need any more information to reproduce this? I attached the platformconfig, hope this is helpful somehow. Yes thank you. Now I can reproduce this. It only happens with NAND and the default in ptxdist is dataflash... I've looked at the patch more closely. The file is indented with tabs and your patch uses spaces. Please fix that. Also fix the patch header as I described in my last mail. See e.g. the other patch to see how it should look like. 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] xmlrpc-c compile issue
Hi, On Tue, Jan 31, 2012 at 07:02:00PM +, Benoît BURNICHON wrote: I am trying to migrate from an old ptxdist-2011.01.0 to ptxdist-2012.01.0. Doing so, I encounter an issue with the xmlrpc-c package. I tried to revert to the xmlrpc-c version to the one used in the old version (xmlrpc-c-1.06.38). It does not work either (same patches are applied). It seems that the automake thing is too old to work properly. Problem is that I'm not an expert in this. Below is the log when it fails. The configure.in is broken. I pushed a patch to fix this to master. You can use that or enable PTXCONF_XMLRPC_C_CPLUSPLUS as a workaround. 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
[ptxdist] [PATCH v4] replace umkimage by u-boot sources
This patch removes the forked mkimage u-boot tool and uses the mainline
u-boot code to build this tool.
Signed-off-by: Andreas Bießmann andr...@biessmann.de
---
Changes since v1:
* add ROOTFS_FW_ENV_CONFIG parameter which installes /etc/fw_env.config
* changes requested by Michael
Changes since v2:
* fix wrong 'fw_saveenv' command - use correct 'fw_setenv'
Changes since v3:
* install host-u-boot-tools into $(HOST_U_BOOT_TOOLS_PKGDIR) rather than
into $(PTXCONF_SYSROOT_HOST)
* remove /etc/fw_env.config from rootfs.{in|make} and install with
u-boot-tools
* remove get for u-boot-tools
* install u-boot-tools into $(U_BOOT_TOOLS_PKGDIR) before packaging
.. but use /usr/bin/mkimage and /usr/sbin/fw_printenv cause mkimage
may be used by normal users (Michael requested to install both into
/usr/sbin, but most distros use /usr/bin for mkimage)
* add a generic/etc/fw_env.config with all comments but no function
additionally give some hints in help text for CONFIG_U_BOOT_TOOLS_TOOL_ENV
generic/etc/fw_env.config | 19 +
...f8dcdbe5c690c-compiler.h-add-uint-typedef.patch | 26 --
patches/u-boot-mkimage-2010.03-1/series|1 -
platforms/hosttools.in |2 +-
platforms/image_uimage.in |8 +-
platforms/kernel.in|2 +-
rules/host-u-boot-tools.in |5 +
rules/host-u-boot-tools.make | 35
rules/host-umkimage.in |8 --
rules/host-umkimage.make | 37 -
rules/templates/template-kernel-in |2 +-
rules/u-boot-tools.in | 36 +
rules/u-boot-tools.make| 82
rules/umkimage.in |8 --
rules/umkimage.make| 66
15 files changed, 184 insertions(+), 153 deletions(-)
create mode 100644 generic/etc/fw_env.config
delete mode 100644
patches/u-boot-mkimage-2010.03-1/b050c72d52c4e30d5b978ab6758f8dcdbe5c690c-compiler.h-add-uint-typedef.patch
delete mode 100644 patches/u-boot-mkimage-2010.03-1/series
create mode 100644 rules/host-u-boot-tools.in
create mode 100644 rules/host-u-boot-tools.make
delete mode 100644 rules/host-umkimage.in
delete mode 100644 rules/host-umkimage.make
create mode 100644 rules/u-boot-tools.in
create mode 100644 rules/u-boot-tools.make
delete mode 100644 rules/umkimage.in
delete mode 100644 rules/umkimage.make
diff --git a/generic/etc/fw_env.config b/generic/etc/fw_env.config
new file mode 100644
index 000..bc6890d
--- /dev/null
+++ b/generic/etc/fw_env.config
@@ -0,0 +1,19 @@
+# Configuration file for fw_(printenv/saveenv) utility.
+# Up to two entries are valid, in this case the redundant
+# environment sector is assumed present.
+# Notice, that the Number of sectors is ignored on NOR and SPI-dataflash.
+# Futhermore, if the Flash sector size is ommitted, this value is assumed to
+# be the same as the Environment size, which is valid for NOR and SPI-dataflash
+
+# NOR example
+# MTD device name Device offset Env. size Flash sector size
Number of sectors
+#/dev/mtd1 0x 0x4000 0x4000
+#/dev/mtd2 0x 0x4000 0x4000
+
+# MTD SPI-dataflash example
+# MTD device name Device offset Env. size Flash sector size
Number of sectors
+#/dev/mtd5 0x4200 0x4200
+#/dev/mtd6 0x4200 0x4200
+
+# NAND example
+#/dev/mtd0 0x4000 0x4000 0x2
2
diff --git
a/patches/u-boot-mkimage-2010.03-1/b050c72d52c4e30d5b978ab6758f8dcdbe5c690c-compiler.h-add-uint-typedef.patch
b/patches/u-boot-mkimage-2010.03-1/b050c72d52c4e30d5b978ab6758f8dcdbe5c690c-compiler.h-add-uint-typedef.patch
deleted file mode 100644
index f20a663..000
---
a/patches/u-boot-mkimage-2010.03-1/b050c72d52c4e30d5b978ab6758f8dcdbe5c690c-compiler.h-add-uint-typedef.patch
+++ /dev/null
@@ -1,26 +0,0 @@
-commit b050c72d52c4e30d5b978ab6758f8dcdbe5c690c
-Author: Mike Frysinger vap...@gentoo.org
-Date: Tue Apr 20 05:49:30 2010 -0400
-
-compiler.h: add uint typedef
-
-Recent crc changes started using the uint type in headers that are used
-on the build system. This subsequently broke mingw targets as they do not
-provide such a type. So add this basic typedef to compiler.h so that we
-do not have to worry about this breaking again in the future.
-
-Signed-off-by: Mike Frysinger vap...@gentoo.org
-Signed-off-by: Remy Bohmer li...@bohmer.net
-
-diff --git a/include/compiler.h b/include/compiler.h
-index 332618e..8030bf6 100644
a/include/compiler.h
-+++ b/include/compiler.h
-@@ -55,6 +55,7 @@ typedef unsigned int uint;
- typedef uint8_t
[ptxdist] beaglebone
Hi Does anybody by chance have a beaglebone ptxdist whe (s)he likes to share? Best regards Tim -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] mxs-utils and the MX28
Hi, I have a Ptxdist (2011.07.0) build for the MX53 and I and looking at also building for the mx28. I see under the platformconfig bootloaders there is a mxs-utils option for the mx28/23. That all built and now I see the elftosb host binary which I know is used in the FSL SDK. Do I need to build the mx28 bootlets out of Ptxdist and then us the elftosb, much like the SDK, to create the bootable SB file? I'm lost on this last step of creating the bootlets like the mx28 SDK so I can use Ptxdist for the mx28. Any pointers is much appreciated. Thanks, Jeff -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] beaglebone
Hi, * Tim Sander ti...@vlsi.informatik.tu-darmstadt.de [2012-02-01 00:53]: Hi Does anybody by chance have a beaglebone ptxdist whe (s)he likes to share? % hg clone https://bitbucket.org/bwalle/ptxdist-arm-boards -r 26030b06fd4a However, the kernel configuration is not tested to have DVI output. Regards, Bernhard -- ptxdist mailing list ptxdist@pengutronix.de
