mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
* [ptxdist] Using external toolchain with penguitronix BSP distribution
@ 2011-10-30 23:57 muntaqa
  2011-11-01 10:13 ` Michael Olbrich
  0 siblings, 1 reply; 8+ messages in thread
From: muntaqa @ 2011-10-30 23:57 UTC (permalink / raw)
  To: ptxdist

Hello,

I am trying to use OSELAS BSP with CodeSourcery toolchain.  
It seems there is a
problem in ptxdist and unable to understand the path setup for external
toolchain using "ptxdist toolchain pathToToolchainBinDir".

I have performed the following:

- ptxdist select configs/ptxconfig
- ptxdist toolchain /home/muntaqa/SourceryARMLinux/bin/
  this creates the softlink properly in the current directory.  But when I run
the next command, it won't find toolchain and finds Penguintronix's toolchain
which is also installed right now in /opt folder.  I had the same issue prior to
installing the penguitronix toolchain that it would not recognize my
CodeSourcery toolchain path.  See text below that shows what I have in
/home/muntaqa/SourceryARMLinux/bin folder.
-ptxdist platform configs/platform-friendlyarm-mini2440/platformconfig-NAND-128M
  this command won't find my sourcery toolchain and default to penguitronix's
toolchain.  Then, I know I need to clear the strings in "ptxdist platformconfig"
dialogs.  But still, it keeps wanting to find something in /opt.  I have
modified and cleared gcc version, libc version, binaries prefix such as
gnuarm-none-linux-eabi. 

Nothing works, it won't recognize the external toolchain and if I have
penguitronix's toolchain installed, it would find it otherwise it makes a path
from the platformconfig items and complains that toolchain does not exist and
tells me to use ptxdist toolchain command to specify a toolchain path ( but I
have already done that.)

I have tried this many times with a clean installation of BSP package in
different locations.  

Can someone send me proper instructions on how to get an external toolchain
configured properly.  I have followed all of the steps in the QuickStart guide
and they don't work.  I need different instructions that will work.

Thanks

    





muntaqa@muntaqa-laptop:~/penguin/OSELAS.BSP-Pengutronix-Mini2440-2011.10.0$ ls
-lrt /home/muntaqa/SourceryARMLinux/bin/
total 16924
-rwxr-xr-x 1 muntaqa muntaqa  363252 2010-11-07 08:53 arm-none-linux-gnueabi
-sprite
-rwxr-xr-x 1 muntaqa muntaqa  340780 2010-11-07 08:53 arm-none-linux-gnueabi
-readelf
-rwxr-xr-x 1 muntaqa muntaqa  630944 2010-11-07 08:53 arm-none-linux-gnueabi
-gprof

-rwxr-xr-x 1 muntaqa muntaqa 3186492 2010-11-07 08:53 arm-none-linux-gnueabi
-gdbtui
-rwxr-xr-x 1 muntaqa muntaqa   26780 2010-11-07 08:53 arm-none-linux-gnueabi
-gcov
-rwxr-xr-x 2 muntaqa muntaqa  222948 2010-11-07 08:53
arm-none-linux-gnueabi-gcc-4.5.1
-rwxr-xr-x 1 muntaqa muntaqa   18612 2010-11-07 08:53 arm-none-linux-gnueabi
-elfedit
-rwxr-xr-x 1 muntaqa muntaqa  224196 2010-11-07 08:53 arm-none-linux-gnueabi
-cpp
-rwxr-xr-x 1 muntaqa muntaqa  572028 2010-11-07 08:53 arm-none-linux-gnueabi-
c++filt
-rwxr-xr-x 2 muntaqa muntaqa  225860 2010-11-07 08:53 arm-none-linux-gnueabi
-c++
-rwxr-xr-x 1 muntaqa muntaqa  569820 2010-11-07 08:53
arm-none-linux-gnueabi-addr2line
-rwxr-xr-x 1 muntaqa muntaqa  572288 2010-11-07 08:53 arm-none-eabi-size
-rwxr-xr-x 1 muntaqa muntaqa 3186492 2010-11-07 08:53 arm-none-eabi-gdb
-rwxr-xr-x 2 muntaqa muntaqa  222948 2010-11-07 08:53 arm-none-eabi-gcc
-rwxr-xr-x 2 muntaqa muntaqa  225860 2010-11-07 08:53 arm-none-eabi-g++
-rwxr-xr-x 1 muntaqa muntaqa  572220 2010-11-07 08:53 arm-none-linux-
gnueabi-strings
-rwxrwxr-x 2 muntaqa muntaqa  593268 2010-11-07 10:53 arm-none-linux-
gnueabi-ranlib
-rwxrwxr-x 2 muntaqa muntaqa  579164 2010-11-07 10:53 arm-none-linux-
gnueabi-nm
-rwxrwxr-x 2 muntaqa muntaqa 1046336 2010-11-07 10:53 arm-none-linux-gnueabi-as
-rwxrwxr-x 2 muntaqa muntaqa  726936 2010-11-07 10:53 arm-none-eabi-strip
-rwxrwxr-x 2 muntaqa muntaqa  866012 2010-11-07 10:53 arm-none-eabi-objdump
-rwxrwxr-x 2 muntaqa muntaqa  726936 2010-11-07 10:53 arm-none-eabi-objcopy
-rwxrwxr-x 2 muntaqa muntaqa  987204 2010-11-07 10:53 arm-none-eabi-ld
-rwxrwxr-x 2 muntaqa muntaqa  593236 2010-11-07 10:53 arm-none-eabi-ar
lrwxrwxrwx 1 muntaqa muntaqa      19 2011-02-20 12:26
arm-none-linux-gnueabi-strip -> arm-none-eabi-strip
lrwxrwxrwx 1 muntaqa muntaqa      18 2011-02-20 12:26
arm-none-linux-gnueabi-size -> arm-none-eabi-size
lrwxrwxrwx 1 muntaqa muntaqa      21 2011-02-20 12:26
arm-none-linux-gnueabi-objdump -> arm-none-eabi-objdump
lrwxrwxrwx 1 muntaqa muntaqa      21 2011-02-20 12:26
arm-none-linux-gnueabi-objcopy -> arm-none-eabi-objcopy
lrwxrwxrwx 1 muntaqa muntaqa    16 2011-02-20 12:27 arm-none-linux-gnueabi-ld
-> arm-none-eabi-ld
lrwxrwxrwx 1 muntaqa muntaqa    17 2011-02-20 12:27 arm-none-linux-gnueabi-gdb
-> arm-none-eabi-gdb
lrwxrwxrwx 1 muntaqa muntaqa    16 2011-02-20 12:27 arm-none-linux-gnueabi-ar
-> arm-none-eabi-ar
lrwxrwxrwx 1 muntaqa muntaqa    17 2011-02-20 12:27 arm-none-linux-gnueabi-g++
-> arm-none-eabi-g++
lrwxrwxrwx 1 muntaqa muntaqa    17 2011-02-20 12:28 arm-none-linux-gnueabi-gcc
-> arm-none-eabi-gcc
muntaqa@muntaqa-laptop:~/penguin/OSELAS.BSP-Pengutronix-Mini2440-2011.10.0$ 








muntaqa@muntaqa-laptop:
~/penguin/OSELAS.BSP-Pengutronix-Mini2440-2011.10.0$ ls -lrt
total 48
drwxr-xr-x 2 muntaqa muntaqa 4096 2011-10-13 10:51 rules
-rw-r--r-- 1 muntaqa muntaqa  177 2011-10-13 10:51 README
drwxr-xr-x 2 muntaqa muntaqa 4096 2011-10-13 10:51 protocol
drwxr-xr-x 3 muntaqa muntaqa 4096 2011-10-13 10:51 projectroot
drwxr-xr-x 3 muntaqa muntaqa 4096 2011-10-13 10:51 local_src
-rw-r--r-- 1 muntaqa muntaqa 3309 2011-10-13 10:51 FAQ
-rw-r--r-- 1 muntaqa muntaqa 2640 2011-10-13 10:51 Changelog
drwxr-xr-x 3 muntaqa muntaqa 4096 2011-10-14 01:14 documentation
drwxr-xr-x 2 muntaqa muntaqa 4096 2011-10-30 17:36 platform
drwxr-xr-x 4 muntaqa muntaqa 4096 2011-10-30 17:43 configs
lrwxrwxrwx 1 muntaqa muntaqa   17 2011-10-30 17:44 selected_ptxconfig ->
configs/ptxconfig
drwxr-xr-x 2 muntaqa muntaqa 4096 2011-10-30 18:31 platform-mini2440
lrwxrwxrwx 1 muntaqa muntaqa   62 2011-10-30 18:44 selected_platformconfig ->
configs/platform-friendlyarm-mini2440/platformconfig-NAND-128M
lrwxrwxrwx 1 muntaqa muntaqa   35 2011-10-30 18:46 selected_toolchain ->
/home/muntaqa/SourceryARMLinux/bin/
muntaqa@muntaqa-laptop:~/penguin/OSELAS.BSP-Pengutronix-Mini2440-2011.10.0$ 






muntaqa@muntaqa-laptop:~/penguin/OSELAS.BSP-Pengutronix-Mini2440-2011.10.0$
ptxdist platform configs/platform-friendlyarm-mini2440/platformconfig-NAND-128M 
info: selected platformconfig:
      'configs/platform-friendlyarm-mini2440/platformconfig-NAND-128M'

info: insufficient information in your platformconfig file
   please use 'ptxdist toolchain </path/to/toolchain>' to select your toolchain

muntaqa@muntaqa-laptop:~/penguin/OSELAS.BSP-Pengutronix-Mini2440-2011.10.0$ 



muntaqa@muntaqa-laptop:~/penguin/OSELAS.BSP-Pengutronix-Mini2440-2011.10.0$ cat
configs/platform-friendlyarm-mini2440/platformconfig-NAND-128M 
#
# Automatically generated make config: don't edit
# PTXdist 2011.10.1
#
PTXCONF_PLATFORMCONFIG_VERSION="2011.10.1"
PTXCONF__platformconfig_MAGIC__=y

#
# ------------------------------------
#

#
# Target Platform Configuration 
#

#
# ------------------------------------
#
PTXCONF_PLATFORM="mini2440"
PTXCONF_PLATFORM_VERSION="-2011.10.0"

#
# 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=""
PTXCONF_CROSSCHAIN_CHECK="4.5.2"
PTXCONF_LIBC_GLIBC=y
# PTXCONF_LIBC_UCLIBC is not set
PTXCONF_GLIBC_VERSION="2.13"
PTXCONF_GNU_TARGET="arm-v4t-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=""
PTXCONF_TARGET_EXTRA_CXXFLAGS=""
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="3.0"
PTXCONF_KERNEL_MD5="398e95866794def22b12dfbc15ce89c0"
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 is not set
# PTXCONF_KERNEL_IMAGE_VMLINUX is not set
# PTXCONF_KERNEL_IMAGE_RAW is not set
# PTXCONF_KERNEL_IMAGE_SIMPLE is not set
PTXCONF_KERNEL_IMAGE="uImage"
# PTXCONF_KERNEL_XZ is not set
# PTXCONF_KERNEL_LZOP is not set

#
# patching & configuration      
#
PTXCONF_KERNEL_SERIES="series"
PTXCONF_KERNEL_CONFIG="kernelconfig-${PTXCONF_KERNEL_VERSION}"

#
# Development features
#
PTXCONF_KERNEL_EXTRA_MAKEVARS="CONFIG_DEBUG_SECTION_MISMATCH=y"
# PTXCONF_HOST_DTC is not set
# PTXCONF_DTC is not set

#
# console options               
#
PTXCONF_CONSOLE_NAME="ttySAC0"
PTXCONF_CONSOLE_SPEED="115200"

#
# bootloaders                   
#
# PTXCONF_AT91BOOTSTRAP is not set
# PTXCONF_AT91BOOTSTRAP2 is not set
PTXCONF_BAREBOX=y
PTXCONF_BAREBOX_VERSION="2011.05.0"
PTXCONF_BAREBOX_MD5="d66774abcf9fa6c9530e13543cc707bc"
PTXCONF_BAREBOX_CONFIG="barebox-NAND-128M.config"
PTXCONF_BAREBOX_ARCH_STRING="arm"
PTXCONF_BAREBOX_EXTRA_ENV=y
PTXCONF_BAREBOX_EXTRA_ENV_PATH="${PTXDIST_PLATFORMCONFIGDIR}/barebox-128m-env"
PTXCONF_BOOTLOADER=y
# PTXCONF_GRUB is not set
# PTXCONF_HOST_MXS_UTILS is not set
# PTXCONF_U_BOOT_V2 is not set
# PTXCONF_U_BOOT is not set
# PTXCONF_X_LOAD is not set

#
# flash                         
#
PTXCONF_FLASH_BLOCKSIZE="128k"

#
# image creation options        
#
# PTXCONF_IMAGE_CPIO is not set
# PTXCONF_IMAGE_CPIO_GZ is not set
# PTXCONF_IMAGE_EXT2 is not set
# PTXCONF_IMAGE_HD is not set

#
# ipkg options                  
#
# PTXCONF_IMAGE_IPKG_PUSH_TO_REPOSITORY is not set
# PTXCONF_IMAGE_INSTALL_FROM_IPKG_REPOSITORY is not set
PTXCONF_IMAGE_IPKG_INDEX=y
PTXCONF_IMAGE_IPKG_EXTRA_ARGS=""
PTXCONF_IMAGE_JFFS2=y
PTXCONF_IMAGE_JFFS2_BLOCKSIZE=0x20000

#
# *** add '-n' here for NAND flash ***
#
PTXCONF_IMAGE_JFFS2_EXTRA_ARGS="-n"
# PTXCONF_IMAGE_JFFS2_SUM is not set
PTXCONF_IMAGE_KERNEL=y
# PTXCONF_IMAGE_KERNEL_INITRAMFS is not set
PTXCONF_IMAGE_KERNEL_INSTALL_EARLY=y
# PTXCONF_IMAGE_KERNEL_LZOP is not set
# PTXCONF_IMAGE_SQUASHFS is not set
PTXCONF_IMAGE_TGZ=y
# PTXCONF_IMAGE_UBI is not set
# PTXCONF_IMAGE_UBIFS is not set
# PTXCONF_IMAGE_UIMAGE is not set
PTXCONF_CROSS_MODULE_INIT_TOOLS=y
# PTXCONF_HOST_CDRKIT is not set
# PTXCONF_HOST_CMAKE is not set
# PTXCONF_HOST_CRAMFS is not set
# PTXCONF_HOST_DOSFSTOOLS is not set
# PTXCONF_HOST_E2FSPROGS is not set
# PTXCONF_HOST_GENEXT2FS is not set
# PTXCONF_HOST_GENPART is not set
# PTXCONF_HOST_GETTEXT is not set
# PTXCONF_HOST_LIBBLKID is not set
# PTXCONF_HOST_LIBBZ2 is not set
# PTXCONF_HOST_LIBCAP is not set
PTXCONF_HOST_LIBLZO=y
PTXCONF_HOST_LIBUUID=y
# PTXCONF_HOST_LZOP is not set
# PTXCONF_HOST_MKELFIMAGE is not set
PTXCONF_HOST_MTD_UTILS=y
# PTXCONF_HOST_MTOOLS is not set
# PTXCONF_HOST_OPENSSL is not set
# PTXCONF_HOST_SQUASHFS_TOOLS is not set
PTXCONF_HOST_UMKIMAGE=y
PTXCONF_HOST_UTIL_LINUX_NG=y
# PTXCONF_HOST_XL_TOOLS is not set
# PTXCONF_HOST_XZ is not set
PTXCONF_HOST_ZLIB=y
muntaqa@muntaqa-laptop:~/penguin/OSELAS.BSP-Pengutronix-Mini2440-2011.10.0$ 




-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [ptxdist] Using external toolchain with penguitronix BSP distribution
  2011-10-30 23:57 [ptxdist] Using external toolchain with penguitronix BSP distribution muntaqa
@ 2011-11-01 10:13 ` Michael Olbrich
  2011-11-02  1:39   ` muntaqa
  0 siblings, 1 reply; 8+ messages in thread
From: Michael Olbrich @ 2011-11-01 10:13 UTC (permalink / raw)
  To: ptxdist

On Sun, Oct 30, 2011 at 11:57:30PM +0000, muntaqa wrote:
> Hello,
> 
> I am trying to use OSELAS BSP with CodeSourcery toolchain.  
> It seems there is a
> problem in ptxdist and unable to understand the path setup for external
> toolchain using "ptxdist toolchain pathToToolchainBinDir".
> 
> I have performed the following:
> 
> - ptxdist select configs/ptxconfig
> - ptxdist toolchain /home/muntaqa/SourceryARMLinux/bin/
>   this creates the softlink properly in the current directory.  But when I run
> the next command, it won't find toolchain and finds Penguintronix's toolchain
> which is also installed right now in /opt folder.  I had the same issue prior to
> installing the penguitronix toolchain that it would not recognize my
> CodeSourcery toolchain path.  See text below that shows what I have in
> /home/muntaqa/SourceryARMLinux/bin folder.
> -ptxdist platform configs/platform-friendlyarm-mini2440/platformconfig-NAND-128M
>   this command won't find my sourcery toolchain and default to penguitronix's
> toolchain.  Then, I know I need to clear the strings in "ptxdist platformconfig"
> dialogs.  But still, it keeps wanting to find something in /opt.  I have
> modified and cleared gcc version, libc version, binaries prefix such as
> gnuarm-none-linux-eabi. 
> 
> Nothing works, it won't recognize the external toolchain and if I have
> penguitronix's toolchain installed, it would find it otherwise it makes a path
> from the platformconfig items and complains that toolchain does not exist and
> tells me to use ptxdist toolchain command to specify a toolchain path ( but I
> have already done that.)
> 
> I have tried this many times with a clean installation of BSP package in
> different locations.  
> 
> Can someone send me proper instructions on how to get an external toolchain
> configured properly.  I have followed all of the steps in the QuickStart guide
> and they don't work.  I need different instructions that will work.
[...]
> #
> # toolchain                     
> #
> PTXCONF_CROSSCHAIN_VENDOR=""

empty is correct.

> PTXCONF_CROSSCHAIN_CHECK="4.5.2"

this must be the output of "gnuarm-none-linux-eabi-gcc -dumpversion".

This is compared with "${PTXCONF_COMPILER_PREFIX}-gcc -dumpversion".

> PTXCONF_LIBC_GLIBC=y
> # PTXCONF_LIBC_UCLIBC is not set
> PTXCONF_GLIBC_VERSION="2.13"

this is only used for toolchain guessing

> PTXCONF_GNU_TARGET="arm-v4t-linux-gnueabi"

PTXCONF_GNU_TARGET="gnuarm-none-linux-eabi"

> PTXCONF_COMPILER_PREFIX="${PTXCONF_GNU_TARGET}-"
> PTXCONF_COMPILER_PREFIX_KERNEL="${PTXCONF_COMPILER_PREFIX}"
> PTXCONF_COMPILER_PREFIX_BOOTLOADER="${PTXCONF_COMPILER_PREFIX}"



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

-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [ptxdist] Using external toolchain with penguitronix BSP distribution
  2011-11-01 10:13 ` Michael Olbrich
@ 2011-11-02  1:39   ` muntaqa
  2011-11-02  8:35     ` Juergen Beisert
  0 siblings, 1 reply; 8+ messages in thread
From: muntaqa @ 2011-11-02  1:39 UTC (permalink / raw)
  To: ptxdist

Thanks for the reply.

Just incase anyone else is interested in this, once setup is performed
correctly, ignore the errors that are confusing.  Toolchain is ready to 
be used and you can start using it even though "ptxdist platform
configs/platform-friendlyarm-mini2440/platformconfig-NAND-128M" outputs
an error.  

My current working settings in that platformconfig-NAND-128M file are:

PTXCONF_CROSSCHAIN_VENDOR=""
PTXCONF_CROSSCHAIN_CHECK="4.5.1" // I just used gcc version from my toolchain
PTXCONF_LIBC_GLIBC=y
# PTXCONF_LIBC_UCLIBC is not set
PTXCONF_GLIBC_VERSION="2.11.1" // I just used glibc version from my toolchain
PTXCONF_GNU_TARGET="arm-none-linux-gnueabi"
PTXCONF_COMPILER_PREFIX="${PTXCONF_GNU_TARGET}-"
PTXCONF_COMPILER_PREFIX_KERNEL="${PTXCONF_COMPILER_PREFIX}"
PTXCONF_COMPILER_PREFIX_BOOTLOADER="${PTXCONF_COMPILER_PREFIX}"




-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [ptxdist] Using external toolchain with penguitronix BSP distribution
  2011-11-02  1:39   ` muntaqa
@ 2011-11-02  8:35     ` Juergen Beisert
  2011-11-05 13:31       ` muntaqa
  0 siblings, 1 reply; 8+ messages in thread
From: Juergen Beisert @ 2011-11-02  8:35 UTC (permalink / raw)
  To: ptxdist; +Cc: muntaqa

muntaqa wrote:
> Just incase anyone else is interested in this, once setup is performed
> correctly, ignore the errors that are confusing.  Toolchain is ready to
> be used and you can start using it even though "ptxdist platform
> configs/platform-friendlyarm-mini2440/platformconfig-NAND-128M" outputs
> an error.
>
> My current working settings in that platformconfig-NAND-128M file are:
>
> PTXCONF_CROSSCHAIN_VENDOR=""
> PTXCONF_CROSSCHAIN_CHECK="4.5.1" // I just used gcc version from my
> toolchain PTXCONF_LIBC_GLIBC=y
> # PTXCONF_LIBC_UCLIBC is not set
> PTXCONF_GLIBC_VERSION="2.11.1" // I just used glibc version from my
> toolchain PTXCONF_GNU_TARGET="arm-none-linux-gnueabi"
> PTXCONF_COMPILER_PREFIX="${PTXCONF_GNU_TARGET}-"
> PTXCONF_COMPILER_PREFIX_KERNEL="${PTXCONF_COMPILER_PREFIX}"
> PTXCONF_COMPILER_PREFIX_BOOTLOADER="${PTXCONF_COMPILER_PREFIX}"

Out of curiosity: what advantage has your toolchain compared to our OSELAS 
ARMv4 toolchain?

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [ptxdist] Using external toolchain with penguitronix BSP distribution
  2011-11-02  8:35     ` Juergen Beisert
@ 2011-11-05 13:31       ` muntaqa
  2011-11-05 14:54         ` Juergen Beisert
  0 siblings, 1 reply; 8+ messages in thread
From: muntaqa @ 2011-11-05 13:31 UTC (permalink / raw)
  To: ptxdist

Juergen Beisert <jbe@...> writes:

> 
> muntaqa wrote:
> > Just incase anyone else is interested in this, once setup is performed
> > correctly, ignore the errors that are confusing.  Toolchain is ready to
> > be used and you can start using it even though "ptxdist platform
> > configs/platform-friendlyarm-mini2440/platformconfig-NAND-128M" outputs
> > an error.
> >
> > My current working settings in that platformconfig-NAND-128M file are:
> >
> > PTXCONF_CROSSCHAIN_VENDOR=""
> > PTXCONF_CROSSCHAIN_CHECK="4.5.1" // I just used gcc version from my
> > toolchain PTXCONF_LIBC_GLIBC=y
> > # PTXCONF_LIBC_UCLIBC is not set
> > PTXCONF_GLIBC_VERSION="2.11.1" // I just used glibc version from my
> > toolchain PTXCONF_GNU_TARGET="arm-none-linux-gnueabi"
> > PTXCONF_COMPILER_PREFIX="${PTXCONF_GNU_TARGET}-"
> > PTXCONF_COMPILER_PREFIX_KERNEL="${PTXCONF_COMPILER_PREFIX}"
> > PTXCONF_COMPILER_PREFIX_BOOTLOADER="${PTXCONF_COMPILER_PREFIX}"
> 
> Out of curiosity: what advantage has your toolchain compared to our OSELAS 
> ARMv4 toolchain?
> 
> Regards,
> Juergen
> 
This is CodeSourcery open source toolchain.  I had chosen it a while ago 
when building the project with buildroot.  I have been using it for a while
and have built and debugged all of my applications with it on mini2440.  At this
point, I did not want to discover or spend time on any other problems since I
have a working system except that I am trying to add QT applications
to my mini2440 platform.
Reason I switched to Pengutronix is that buildroot gave me some trouble when
building QT thru it plus it had always given me kernel panic errors when
installing the jffs2 root image (so I had been simply using tar balls on top
of the stock kernel/rootfs that mini2440 is shipped with).  I thought switching
to Pengutronix would finally let me burn a true image and I can organize my
project much better.

Currently, I still have kernel panic messages when building the rootfs using
Pengutronix and CodeSourcery.  It seems perhaps that it is because of 
gcc 4.5.1 that is being used in my version of CodeSourcery.  When I use your
toolchain, I
can burn an image properly and do not receive kernel panic messages.  Your
toolchain uses gcc 4.5.2.

One issue that I see though with Pengutronix is that any time I change a
selection or add anything to QT configuration in Penguitronix ptxdist
menuconfig, it rebuilds the whole QT (ends up costing me couple of hours 
plus I am not able to try anything quickly.)

I would like to start using pengutronix as long as it would be less 
frustrating than buildroot.

BTW, my best wishes to you on this project, you guys have done alot of 
good work and looking at your documentation the working environment, it seems
very promising.

Regards,
Muntaqa




-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [ptxdist] Using external toolchain with penguitronix BSP distribution
  2011-11-05 13:31       ` muntaqa
@ 2011-11-05 14:54         ` Juergen Beisert
  2011-11-15 14:32           ` muntaqa
  0 siblings, 1 reply; 8+ messages in thread
From: Juergen Beisert @ 2011-11-05 14:54 UTC (permalink / raw)
  To: ptxdist; +Cc: oselas, muntaqa

muntaqa wrote:
> Juergen Beisert <jbe@...> writes:
> > Out of curiosity: what advantage has your toolchain compared to our
> > OSELAS ARMv4 toolchain?
>
> This is CodeSourcery open source toolchain.  I had chosen it a while ago
> when building the project with buildroot.  I have been using it for a while
> and have built and debugged all of my applications with it on mini2440.  At
> this point, I did not want to discover or spend time on any other problems
> since I have a working system except that I am trying to add QT
> applications to my mini2440 platform.

Okay.

> Reason I switched to Pengutronix is that buildroot gave me some trouble
> when building QT thru it plus it had always given me kernel panic errors
> when installing the jffs2 root image (so I had been simply using tar balls
> on top of the stock kernel/rootfs that mini2440 is shipped with).  I
> thought switching to Pengutronix would finally let me burn a true image and
> I can organize my project much better.
>
> Currently, I still have kernel panic messages when building the rootfs
> using Pengutronix and CodeSourcery.  It seems perhaps that it is because of
> gcc 4.5.1 that is being used in my version of CodeSourcery.  When I use
> your toolchain, I can burn an image properly and do not receive kernel panic
> messages.  Your toolchain uses gcc 4.5.2.

Do all supported kernels show the same panic? Sometimes one kernel has trouble 
with a specific gcc version, and other kernels not. Did you try all kernels 
from the BSP with your CodeSourcery toolchain?

> One issue that I see though with Pengutronix is that any time I change a
> selection or add anything to QT configuration in Penguitronix ptxdist
> menuconfig, it rebuilds the whole QT (ends up costing me couple of hours
> plus I am not able to try anything quickly.)

On our new 24 core/96 GiB RAM machine Qt4 builds really quick in a few 
minutes. ;-)

Maybe you should start with a full blown Qt4, do your development with it, and 
when it is finished, you can try to shrink the library by disabling some of 
its options.

> I would like to start using pengutronix as long as it would be less
> frustrating than buildroot.

I don't know buildroot. I work with PTXdist since years.

> BTW, my best wishes to you on this project, you guys have done alot of
> good work and looking at your documentation the working environment, it
> seems very promising.

Thanks.

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [ptxdist] Using external toolchain with penguitronix BSP distribution
  2011-11-05 14:54         ` Juergen Beisert
@ 2011-11-15 14:32           ` muntaqa
  2011-11-15 14:57             ` Juergen Beisert
  0 siblings, 1 reply; 8+ messages in thread
From: muntaqa @ 2011-11-15 14:32 UTC (permalink / raw)
  To: ptxdist

Juergen Beisert <jbe@...> writes:

> 
> muntaqa wrote:
> > Juergen Beisert <jbe@...> writes:
> > > Out of curiosity: what advantage has your toolchain compared to our
> > > OSELAS ARMv4 toolchain?
> >
> > This is CodeSourcery open source toolchain.  I had chosen it a while ago
> > when building the project with buildroot.  I have been using it for a while
> > and have built and debugged all of my applications with it on mini2440.  At
> > this point, I did not want to discover or spend time on any other problems
> > since I have a working system except that I am trying to add QT
> > applications to my mini2440 platform.
> 
> Okay.
> 
> > Reason I switched to Pengutronix is that buildroot gave me some trouble
> > when building QT thru it plus it had always given me kernel panic errors
> > when installing the jffs2 root image (so I had been simply using tar balls
> > on top of the stock kernel/rootfs that mini2440 is shipped with).  I
> > thought switching to Pengutronix would finally let me burn a true image and
> > I can organize my project much better.
> >
> > Currently, I still have kernel panic messages when building the rootfs
> > using Pengutronix and CodeSourcery.  It seems perhaps that it is because of
> > gcc 4.5.1 that is being used in my version of CodeSourcery.  When I use
> > your toolchain, I can burn an image properly and do not receive kernel panic
> > messages.  Your toolchain uses gcc 4.5.2.
> 
> Do all supported kernels show the same panic? Sometimes one kernel has trouble 
> with a specific gcc version, and other kernels not. Did you try all kernels 
> from the BSP with your CodeSourcery toolchain?
> 
> > One issue that I see though with Pengutronix is that any time I change a
> > selection or add anything to QT configuration in Penguitronix ptxdist
> > menuconfig, it rebuilds the whole QT (ends up costing me couple of hours
> > plus I am not able to try anything quickly.)
> 
> On our new 24 core/96 GiB RAM machine Qt4 builds really quick in a few 
> minutes. 
> 
> Maybe you should start with a full blown Qt4, do your development with it, and 
> when it is finished, you can try to shrink the library by disabling some of 
> its options.
> 
> > I would like to start using pengutronix as long as it would be less
> > frustrating than buildroot.
> 
> I don't know buildroot. I work with PTXdist since years.
> 
> > BTW, my best wishes to you on this project, you guys have done alot of
> > good work and looking at your documentation the working environment, it
> > seems very promising.
> 
> Thanks.
> 
> Regards,
> Juergen
> 

Hello Juergen,

I am wondering if you would be able to help me with kernel panic issue?  I have
tried different gcc versions of CodeSourcery with about three kernel versions
and I always get kernel panics when booting mini2440.  I am following your quick
start guide for either botting from nfs or nand.  I follow the procedure for
nand updates etc.  Is there an inherent problem with burning JFFS2 format on
mini2440 or is it Code Sourcery that perhaps has a problem?  Any help
would be much appreciated.  Please let me know what information I need to
provide for you to be able to help me?  Below is the platformconfig settings:

#
# Automatically generated make config: don't edit
# PTXdist 2011.10.1
#
PTXCONF_PLATFORMCONFIG_VERSION="2011.10.1"
PTXCONF__platformconfig_MAGIC__=y

#
# ------------------------------------
#

#
# Target Platform Configuration 
#

#
# ------------------------------------
#
PTXCONF_PLATFORM="mini2440"
PTXCONF_PLATFORM_VERSION="-2011.10.0"

#
# 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=""
PTXCONF_CROSSCHAIN_CHECK="4.5.2"
PTXCONF_LIBC_GLIBC=y
# PTXCONF_LIBC_UCLIBC is not set
PTXCONF_GLIBC_VERSION="2.13"
PTXCONF_GNU_TARGET="arm-none-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="-march=armv4t -mtune=arm920t"
PTXCONF_TARGET_EXTRA_CFLAGS="-march=armv4t -mtune=arm920t"
PTXCONF_TARGET_EXTRA_CXXFLAGS="-march=armv4t -mtune=arm920t"
PTXCONF_TARGET_EXTRA_LDFLAGS="-march=armv4t -mtune=arm920t"
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="3.0"
#PTXCONF_KERNEL_MD5="398e95866794def22b12dfbc15ce89c0"
PTXCONF_KERNEL_VERSION="2.6.38"
PTXCONF_KERNEL_MD5="398e95866794def22b12dfbc15ce89c0"
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 is not set
# PTXCONF_KERNEL_IMAGE_VMLINUX is not set
# PTXCONF_KERNEL_IMAGE_RAW is not set
# PTXCONF_KERNEL_IMAGE_SIMPLE is not set
PTXCONF_KERNEL_IMAGE="uImage"
# PTXCONF_KERNEL_XZ is not set
# PTXCONF_KERNEL_LZOP is not set

#
# patching & configuration      
#
PTXCONF_KERNEL_SERIES="series"
PTXCONF_KERNEL_CONFIG="kernelconfig-${PTXCONF_KERNEL_VERSION}"

#
# Development features
#
PTXCONF_KERNEL_EXTRA_MAKEVARS="CONFIG_DEBUG_SECTION_MISMATCH=y"
# PTXCONF_HOST_DTC is not set
# PTXCONF_DTC is not set

#
# console options               
#
PTXCONF_CONSOLE_NAME="ttySAC0"
PTXCONF_CONSOLE_SPEED="115200"

#
# bootloaders                   
#
# PTXCONF_AT91BOOTSTRAP is not set
# PTXCONF_AT91BOOTSTRAP2 is not set
PTXCONF_BAREBOX=y
PTXCONF_BAREBOX_VERSION="2011.05.0"
PTXCONF_BAREBOX_MD5="d66774abcf9fa6c9530e13543cc707bc"
PTXCONF_BAREBOX_CONFIG="barebox-NAND-128M.config"
PTXCONF_BAREBOX_ARCH_STRING="arm"
PTXCONF_BAREBOX_EXTRA_ENV=y
PTXCONF_BAREBOX_EXTRA_ENV_PATH="${PTXDIST_PLATFORMCONFIGDIR}/barebox-128m-env"
PTXCONF_BOOTLOADER=y
# PTXCONF_GRUB is not set
# PTXCONF_HOST_MXS_UTILS is not set
# PTXCONF_U_BOOT_V2 is not set
# PTXCONF_U_BOOT is not set
# PTXCONF_X_LOAD is not set

#
# flash                         
#
PTXCONF_FLASH_BLOCKSIZE="128k"

#
# image creation options        
#
# PTXCONF_IMAGE_CPIO is not set
# PTXCONF_IMAGE_CPIO_GZ is not set
# PTXCONF_IMAGE_EXT2 is not set
# PTXCONF_IMAGE_HD is not set

#
# ipkg options                  
#
# PTXCONF_IMAGE_IPKG_PUSH_TO_REPOSITORY is not set
# PTXCONF_IMAGE_INSTALL_FROM_IPKG_REPOSITORY is not set
PTXCONF_IMAGE_IPKG_INDEX=y
PTXCONF_IMAGE_IPKG_EXTRA_ARGS=""
PTXCONF_IMAGE_JFFS2=y
PTXCONF_IMAGE_JFFS2_BLOCKSIZE=0x20000

#
# *** add '-n' here for NAND flash ***
#
PTXCONF_IMAGE_JFFS2_EXTRA_ARGS="-n"
# PTXCONF_IMAGE_JFFS2_SUM is not set
PTXCONF_IMAGE_KERNEL=y
# PTXCONF_IMAGE_KERNEL_INITRAMFS is not set
PTXCONF_IMAGE_KERNEL_INSTALL_EARLY=y
# PTXCONF_IMAGE_KERNEL_LZOP is not set
# PTXCONF_IMAGE_SQUASHFS is not set
PTXCONF_IMAGE_TGZ=y
# PTXCONF_IMAGE_UBI is not set
# PTXCONF_IMAGE_UBIFS is not set
# PTXCONF_IMAGE_UIMAGE is not set
PTXCONF_CROSS_MODULE_INIT_TOOLS=y
# PTXCONF_HOST_CDRKIT is not set
# PTXCONF_HOST_CMAKE is not set
# PTXCONF_HOST_CRAMFS is not set
# PTXCONF_HOST_DOSFSTOOLS is not set
# PTXCONF_HOST_E2FSPROGS is not set
# PTXCONF_HOST_GENEXT2FS is not set
# PTXCONF_HOST_GENPART is not set
# PTXCONF_HOST_GETTEXT is not set
# PTXCONF_HOST_LIBBLKID is not set
# PTXCONF_HOST_LIBBZ2 is not set
# PTXCONF_HOST_LIBCAP is not set
PTXCONF_HOST_LIBLZO=y
PTXCONF_HOST_LIBUUID=y
# PTXCONF_HOST_LZOP is not set
# PTXCONF_HOST_MKELFIMAGE is not set
PTXCONF_HOST_MTD_UTILS=y
# PTXCONF_HOST_MTOOLS is not set
# PTXCONF_HOST_OPENSSL is not set
# PTXCONF_HOST_SQUASHFS_TOOLS is not set
PTXCONF_HOST_UMKIMAGE=y
PTXCONF_HOST_UTIL_LINUX_NG=y
# PTXCONF_HOST_XL_TOOLS is not set
# PTXCONF_HOST_XZ is not set
PTXCONF_HOST_ZLIB=y





-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [ptxdist] Using external toolchain with penguitronix BSP distribution
  2011-11-15 14:32           ` muntaqa
@ 2011-11-15 14:57             ` Juergen Beisert
  0 siblings, 0 replies; 8+ messages in thread
From: Juergen Beisert @ 2011-11-15 14:57 UTC (permalink / raw)
  To: ptxdist; +Cc: muntaqa

Hi muntaqa,

muntaqa wrote:
> Juergen Beisert <jbe@...> writes:
> > muntaqa wrote:
> > > Juergen Beisert <jbe@...> writes:
> > > > Out of curiosity: what advantage has your toolchain compared to our
> > > > OSELAS ARMv4 toolchain?
> > >
> > > This is CodeSourcery open source toolchain.  I had chosen it a while
> > > ago when building the project with buildroot.  I have been using it for
> > > a while and have built and debugged all of my applications with it on
> > > mini2440.  At this point, I did not want to discover or spend time on
> > > any other problems since I have a working system except that I am
> > > trying to add QT applications to my mini2440 platform.
> >
> > Okay.
> >
> > > Reason I switched to Pengutronix is that buildroot gave me some trouble
> > > when building QT thru it plus it had always given me kernel panic
> > > errors when installing the jffs2 root image (so I had been simply using
> > > tar balls on top of the stock kernel/rootfs that mini2440 is shipped
> > > with).  I thought switching to Pengutronix would finally let me burn a
> > > true image and I can organize my project much better.
> > >
> > > Currently, I still have kernel panic messages when building the rootfs
> > > using Pengutronix and CodeSourcery.  It seems perhaps that it is
> > > because of gcc 4.5.1 that is being used in my version of CodeSourcery. 
> > > When I use your toolchain, I can burn an image properly and do not
> > > receive kernel panic messages.  Your toolchain uses gcc 4.5.2.
> >
> > Do all supported kernels show the same panic? Sometimes one kernel has
> > trouble with a specific gcc version, and other kernels not. Did you try
> > all kernels from the BSP with your CodeSourcery toolchain?
> >
> > > One issue that I see though with Pengutronix is that any time I change
> > > a selection or add anything to QT configuration in Penguitronix ptxdist
> > > menuconfig, it rebuilds the whole QT (ends up costing me couple of
> > > hours plus I am not able to try anything quickly.)
> >
> > On our new 24 core/96 GiB RAM machine Qt4 builds really quick in a few
> > minutes.
> >
> > Maybe you should start with a full blown Qt4, do your development with
> > it, and when it is finished, you can try to shrink the library by
> > disabling some of its options.
> >
> > > I would like to start using pengutronix as long as it would be less
> > > frustrating than buildroot.
> >
> > I don't know buildroot. I work with PTXdist since years.
> >
> > > BTW, my best wishes to you on this project, you guys have done alot of
> > > good work and looking at your documentation the working environment, it
> > > seems very promising.
>
> I am wondering if you would be able to help me with kernel panic issue?  I
> have tried different gcc versions of CodeSourcery with about three kernel
> versions and I always get kernel panics when booting mini2440.  I am
> following your quick start guide for either botting from nfs or nand.  I
> follow the procedure for nand updates etc.  Is there an inherent problem
> with burning JFFS2 format on mini2440 or is it Code Sourcery that perhaps
> has a problem?  Any help would be much appreciated.  Please let me know
> what information I need to provide for you to be able to help me?

First, we are now Mini2440 specific, not PTXdist. So, we should change to the  
oselas@community mailing list. If you are not subscribed yet, please do so. 
Take a look at our 'http://www.pengutronix.de/mailinglists/index_en.html', 
refer 'OSELAS Community'.

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Beisert             |
Linux Solutions for Science and Industry      | http://www.pengutronix.de/  |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2011-11-15 14:57 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-10-30 23:57 [ptxdist] Using external toolchain with penguitronix BSP distribution muntaqa
2011-11-01 10:13 ` Michael Olbrich
2011-11-02  1:39   ` muntaqa
2011-11-02  8:35     ` Juergen Beisert
2011-11-05 13:31       ` muntaqa
2011-11-05 14:54         ` Juergen Beisert
2011-11-15 14:32           ` muntaqa
2011-11-15 14:57             ` Juergen Beisert

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox