* [Buildroot] Glibc LD_LIBRARAY_PATH error
@ 2014-06-27 20:28 Panahi Parsa
2014-06-27 22:01 ` Thomas Petazzoni
0 siblings, 1 reply; 14+ messages in thread
From: Panahi Parsa @ 2014-06-27 20:28 UTC (permalink / raw)
To: buildroot
Hi I faced this error when making buildroot
parsa at parsa-System-Product-Name:~/Software/Buildroot/buildroot$ make
>>> glibc 2.18 Configuring
mkdir -p
/home/parsa/Software/Buildroot/buildroot/output/build/glibc-2.18/build
# Do the configuration
(cd /home/parsa/Software/Buildroot/buildroot/output/build/glibc-2.18/build;
PATH="/home/parsa/Software/Buildroot/buildroot/output/host/bin:/home/parsa/Software/Buildroot/buildroot/output/host/sbin:/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin:/home/parsa/Software/Buildroot/buildroot/output/host/usr/sbin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"
AR="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-ar"
AS="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-as"
LD="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-ld"
NM="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-nm"
CC="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-gcc"
GCC="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-gcc"
CPP="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-cpp"
CXX="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-g++"
FC="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-gfortran"
RANLIB="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-ranlib"
READELF="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-readelf"
STRIP="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-strip"
OBJCOPY="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-objcopy"
OBJDUMP="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-objdump"
AR_FOR_BUILD="/usr/bin/ar" AS_FOR_BUILD="/usr/bin/as"
CC_FOR_BUILD="/usr/bin/gcc" GCC_FOR_BUILD="/usr/bin/gcc"
CXX_FOR_BUILD="/usr/bin/g++" FC_FOR_BUILD="/usr/bin/ld"
LD_FOR_BUILD="/usr/bin/ld"
CPPFLAGS_FOR_BUILD="-I/home/parsa/Software/Buildroot/buildroot/output/host/usr/include"
CFLAGS_FOR_BUILD="-O2
-I/home/parsa/Software/Buildroot/buildroot/output/host/usr/include"
CXXFLAGS_FOR_BUILD="-O2
-I/home/parsa/Software/Buildroot/buildroot/output/host/usr/include"
LDFLAGS_FOR_BUILD="-L/home/parsa/Software/Buildroot/buildroot/output/host/lib
-L/home/parsa/Software/Buildroot/buildroot/output/host/usr/lib
-Wl,-rpath,/home/parsa/Software/Buildroot/buildroot/output/host/usr/lib"
FCFLAGS_FOR_BUILD=""
DEFAULT_ASSEMBLER="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-as"
DEFAULT_LINKER="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-ld"
CPPFLAGS="-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64"
CFLAGS="-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64
-pipe -O3 " CXXFLAGS="-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE
-D_FILE_OFFSET_BITS=64 -pipe -O3 " LDFLAGS="" FCFLAGS=""
PKG_CONFIG="/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/pkg-config"
STAGING_DIR="/home/parsa/Software/Buildroot/buildroot/output/host/usr/x86_64-buildroot-linux-gnu/sysroot"
CXX=false CFLAGS="-O2 " CPPFLAGS="" CXXFLAGS="-O2 " /bin/bash
/home/parsa/Software/Buildroot/buildroot/output/build/glibc-2.18/./configure
ac_cv_path_BASH_SHELL=/bin/bash libc_cv_forced_unwind=yes
--target=x86_64-buildroot-linux-gnu --host=x86_64-buildroot-linux-gnu
--build=x86_64-unknown-linux-gnu --prefix=/usr --enable-shared --with-fp
--with-pkgversion="Buildroot" --without-cvs --disable-profile --without-gd
--enable-obsolete-rpc
--with-headers=/home/parsa/Software/Buildroot/buildroot/output/host/usr/x86_64-buildroot-linux-gnu/sysroot/usr/include)
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-buildroot-linux-gnu
checking for x86_64-buildroot-linux-gnu-gcc...
/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-gcc
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether
/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-gcc
accepts -g... yes
checking for gcc... gcc
checking whether we are using the GNU C++ compiler... no
checking whether false accepts -g... no
checking for x86_64-buildroot-linux-gnu-readelf...
/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-readelf
checking for sysdeps preconfigure fragments... x86_64 checking whether
/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-gcc
compiles in -mx32 mode by default... no
configure: running configure fragment for add-on libidn
configure: running configure fragment for add-on nptl
checking add-on ports for preconfigure fragments... aarch64 alpha am33 arm
hppa ia64 m68k microblaze mips tile
checking for assembler and linker STT_GNU_IFUNC support... yes
checking whether .text pseudo-op must be used... yes
checking sysdep dirs... sysdeps/unix/sysv/linux/x86_64/64/nptl
sysdeps/unix/sysv/linux/x86_64/64 nptl/sysdeps/unix/sysv/linux/x86_64
nptl/sysdeps/unix/sysv/linux/x86 sysdeps/unix/sysv/linux/x86
sysdeps/unix/sysv/linux/x86_64 sysdeps/unix/sysv/linux/wordsize-64
nptl/sysdeps/unix/sysv/linux nptl/sysdeps/pthread sysdeps/pthread
ports/sysdeps/unix/sysv/linux sysdeps/unix/sysv/linux sysdeps/gnu
sysdeps/unix/inet nptl/sysdeps/unix/sysv ports/sysdeps/unix/sysv
sysdeps/unix/sysv sysdeps/unix/x86_64 nptl/sysdeps/unix ports/sysdeps/unix
sysdeps/unix sysdeps/posix nptl/sysdeps/x86_64/64 sysdeps/x86_64/64
sysdeps/x86_64/fpu/multiarch sysdeps/x86_64/fpu sysdeps/x86/fpu
sysdeps/x86_64/multiarch nptl/sysdeps/x86_64 sysdeps/x86_64 sysdeps/x86
sysdeps/ieee754/ldbl-96 sysdeps/ieee754/dbl-64/wordsize-64
sysdeps/ieee754/dbl-64 sysdeps/ieee754/flt-32 sysdeps/wordsize-64
sysdeps/ieee754 sysdeps/generic
configure: WARNING: add-on ports contributed no useful sysdeps directories
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking whether
/home/parsa/Software/Buildroot/buildroot/output/host/usr/lib/gcc/x86_64-buildroot-linux-gnu/4.8.3/../../../../x86_64-buildroot-linux-gnu/bin/as
is GNU as... yes
checking whether
/home/parsa/Software/Buildroot/buildroot/output/host/usr/lib/gcc/x86_64-buildroot-linux-gnu/4.8.3/../../../../x86_64-buildroot-linux-gnu/bin/ld
is GNU ld... yes
checking for
/home/parsa/Software/Buildroot/buildroot/output/host/usr/lib/gcc/x86_64-buildroot-linux-gnu/4.8.3/../../../../x86_64-buildroot-linux-gnu/bin/as...
/home/parsa/Software/Buildroot/buildroot/output/host/usr/lib/gcc/x86_64-buildroot-linux-gnu/4.8.3/../../../../x86_64-buildroot-linux-gnu/bin/as
checking version of
/home/parsa/Software/Buildroot/buildroot/output/host/usr/lib/gcc/x86_64-buildroot-linux-gnu/4.8.3/../../../../x86_64-buildroot-linux-gnu/bin/as...
2.22, ok
checking for
/home/parsa/Software/Buildroot/buildroot/output/host/usr/lib/gcc/x86_64-buildroot-linux-gnu/4.8.3/../../../../x86_64-buildroot-linux-gnu/bin/ld...
/home/parsa/Software/Buildroot/buildroot/output/host/usr/lib/gcc/x86_64-buildroot-linux-gnu/4.8.3/../../../../x86_64-buildroot-linux-gnu/bin/ld
checking version of
/home/parsa/Software/Buildroot/buildroot/output/host/usr/lib/gcc/x86_64-buildroot-linux-gnu/4.8.3/../../../../x86_64-buildroot-linux-gnu/bin/ld...
2.22, ok
checking for x86_64-buildroot-linux-gnu-gcc... (cached)
/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-gcc
checking version of
/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-gcc...
4.8.3, ok
checking for gnumake... no
checking for gmake... no
checking for make... make
checking version of make... 3.81, ok
checking for gnumsgfmt... no
checking for gmsgfmt... no
checking for msgfmt... msgfmt
checking version of msgfmt... 0.18.1, ok
checking for makeinfo... no
checking for sed... sed
checking version of sed... 4.2.1, ok
checking for gawk... gawk
checking version of gawk... 4.1.0, ok
checking for x86_64-buildroot-linux-gnu-nm...
/home/parsa/Software/Buildroot/buildroot/output/host/usr/bin/x86_64-buildroot-linux-gnu-nm
checking for autoconf... no
configure: WARNING:
*** These auxiliary programs are missing or incompatible versions: makeinfo
autoconf
*** some features will be disabled.
*** Check the INSTALL file for required versions.
checking LD_LIBRARY_PATH variable... contains current directory
configure: error:
*** LD_LIBRARY_PATH shouldn't contain the current directory when
*** building glibc. Please change the environment variable
*** and run configure again.
make: ***
[/home/parsa/Software/Buildroot/buildroot/output/build/glibc-2.18/.stamp_configured]
Error 1
parsa at parsa-System-Product-Name:~/Software/Buildroot/buildroot$
It seems that I should change LD_LIBARAY_PATH to include glibc environment
variables !! Since I'm new to buildroot I don't know how I should do this.
Is there some one who can tell me the steps to solve this problem ?
--
Parsa Panahi
D?partement de g?nie ?lectrique
?tudiant de l'?lectronique num?rique
Sharif Universit? de Technologie - T?h?ran - Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140628/1f4b9755/attachment.html>
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Glibc LD_LIBRARAY_PATH error
2014-06-27 20:28 [Buildroot] Glibc LD_LIBRARAY_PATH error Panahi Parsa
@ 2014-06-27 22:01 ` Thomas Petazzoni
2014-06-28 4:45 ` Panahi Parsa
0 siblings, 1 reply; 14+ messages in thread
From: Thomas Petazzoni @ 2014-06-27 22:01 UTC (permalink / raw)
To: buildroot
Dear Panahi Parsa,
On Sat, 28 Jun 2014 00:58:31 +0430, Panahi Parsa wrote:
> *** These auxiliary programs are missing or incompatible versions: makeinfo
> autoconf
> *** some features will be disabled.
> *** Check the INSTALL file for required versions.
> checking LD_LIBRARY_PATH variable... contains current directory
> configure: error:
> *** LD_LIBRARY_PATH shouldn't contain the current directory when
> *** building glibc. Please change the environment variable
> *** and run configure again.
> make: ***
> [/home/parsa/Software/Buildroot/buildroot/output/build/glibc-2.18/.stamp_configured]
> Error 1
>
> parsa at parsa-System-Product-Name:~/Software/Buildroot/buildroot$
>
> It seems that I should change LD_LIBARAY_PATH to include glibc environment
> variables !! Since I'm new to buildroot I don't know how I should do this.
>
> Is there some one who can tell me the steps to solve this problem ?
Can you post the output of the "env" command in the terminal you used
Buildroot?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Glibc LD_LIBRARAY_PATH error
2014-06-27 22:01 ` Thomas Petazzoni
@ 2014-06-28 4:45 ` Panahi Parsa
2014-06-28 6:36 ` Thomas Petazzoni
0 siblings, 1 reply; 14+ messages in thread
From: Panahi Parsa @ 2014-06-28 4:45 UTC (permalink / raw)
To: buildroot
Hi I've sent the output of env command in my buildroot folder
parsa at parsa-System-Product-Name:~/Software/Buildroot/buildroot$ env
SSH_AGENT_PID=1485
GPG_AGENT_INFO=/tmp/keyring-eVmLaZ/gpg:0:1
TERM=xterm
SHELL=/bin/bash
XDG_SESSION_COOKIE=755755d7fc9010640f716d5300000002-1403930328.483565-169998459
GENICAM_ROOT_V2_3=/opt/pylon3/genicam
WINDOWID=56623110
OLDPWD=/home/parsa
GNOME_KEYRING_CONTROL=/tmp/keyring-eVmLaZ
PYLON_ROOT=/opt/pylon3
USER=parsa
LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lz=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.axv=01;35:*.anx=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.axa=00;36:*.oga=00;36:*.spx=00;36:*.xspf=00;36:
LD_LIBRARY_PATH=/opt/pylon3/lib64:/opt/pylon3/genicam/bin/Linux64_x64:/opt/pylon3/genicam/bin/Linux64_x64/GenApi/Generic::/home/parsa/Software/OPENCV/build/lib:/usr/local/lib:/home/parsa/Software/OPENCV/build/lib
LIBGL_DRIVERS_PATH=/usr/lib/fglrx/dri:/usr/lib/x86_64-linux-gnu/dri:/usr/lib/dri:/usr/lib32/fglrx/dri:/usr/lib/i386-linux-gnu/dri
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
SSH_AUTH_SOCK=/tmp/keyring-eVmLaZ/ssh
SESSION_MANAGER=local/parsa-System-Product-Name:@
/tmp/.ICE-unix/1411,unix/parsa-System-Product-Name:/tmp/.ICE-unix/1411
DEFAULTS_PATH=/usr/share/gconf/ubuntu.default.path
XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg
PATH=/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
DESKTOP_SESSION=ubuntu
PWD=/home/parsa/Software/Buildroot/buildroot
LANG=en_US.UTF-8
MANDATORY_PATH=/usr/share/gconf/ubuntu.mandatory.path
UBUNTU_MENUPROXY=libappmenu.so
COMPIZ_CONFIG_PROFILE=ubuntu
GDMSESSION=ubuntu
SHLVL=1
HOME=/home/parsa
LANGUAGE=en_US:en
GENICAM_CACHE=/opt/pylon3/xml_cache
GNOME_DESKTOP_SESSION_ID=this-is-deprecated
LOGNAME=parsa
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-jgoqOyqvSk,guid=d428726f5fec304f7689199500000005
LESSOPEN=| /usr/bin/lesspipe %s
DISPLAY=:0.0
XDG_CURRENT_DESKTOP=Unity
LESSCLOSE=/usr/bin/lesspipe %s %s
COLORTERM=gnome-terminal
XAUTHORITY=/home/parsa/.Xauthority
_=/usr/bin/env
parsa at parsa-System-Product-Name:~/Software/Buildroot/buildroot$
2014-06-28 2:31 GMT+04:30 Thomas Petazzoni <
thomas.petazzoni@free-electrons.com>:
> Dear Panahi Parsa,
>
> On Sat, 28 Jun 2014 00:58:31 +0430, Panahi Parsa wrote:
>
> > *** These auxiliary programs are missing or incompatible versions:
> makeinfo
> > autoconf
> > *** some features will be disabled.
> > *** Check the INSTALL file for required versions.
> > checking LD_LIBRARY_PATH variable... contains current directory
> > configure: error:
> > *** LD_LIBRARY_PATH shouldn't contain the current directory when
> > *** building glibc. Please change the environment variable
> > *** and run configure again.
> > make: ***
> >
> [/home/parsa/Software/Buildroot/buildroot/output/build/glibc-2.18/.stamp_configured]
> > Error 1
> >
> > parsa at parsa-System-Product-Name:~/Software/Buildroot/buildroot$
> >
> > It seems that I should change LD_LIBARAY_PATH to include glibc
> environment
> > variables !! Since I'm new to buildroot I don't know how I should do
> this.
> >
> > Is there some one who can tell me the steps to solve this problem ?
>
> Can you post the output of the "env" command in the terminal you used
> Buildroot?
>
> Best regards,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>
--
Parsa Panahi
D?partement de g?nie ?lectrique
?tudiant de l'?lectronique num?rique
Sharif Universit? de Technologie - T?h?ran - Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140628/28df6ec8/attachment.html>
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Glibc LD_LIBRARAY_PATH error
2014-06-28 4:45 ` Panahi Parsa
@ 2014-06-28 6:36 ` Thomas Petazzoni
2014-06-28 14:25 ` Panahi Parsa
0 siblings, 1 reply; 14+ messages in thread
From: Thomas Petazzoni @ 2014-06-28 6:36 UTC (permalink / raw)
To: buildroot
Dear Panahi Parsa,
On Sat, 28 Jun 2014 09:15:18 +0430, Panahi Parsa wrote:
> LD_LIBRARY_PATH=/opt/pylon3/lib64:/opt/pylon3/genicam/bin/Linux64_x64:/opt/pylon3/genicam/bin/Linux64_x64/GenApi/Generic::/home/parsa/Software/OPENCV/build/lib:/usr/local/lib:/home/parsa/Software/OPENCV/build/lib
This LD_LIBRARY_PATH value, which has an empty member (notice the
double : in the middle of the variable), is probably was confuses the
glibc build system. Can you adjust your LD_LIBRARY_PATH to remove this
empty member, and restart the build from scratch ("make clean all"),
and let us know if that solves the problem? If it does, we'll add a
check to warn users about this problem.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 14+ messages in thread* [Buildroot] Glibc LD_LIBRARAY_PATH error
2014-06-28 6:36 ` Thomas Petazzoni
@ 2014-06-28 14:25 ` Panahi Parsa
2014-06-28 14:28 ` Thomas Petazzoni
0 siblings, 1 reply; 14+ messages in thread
From: Panahi Parsa @ 2014-06-28 14:25 UTC (permalink / raw)
To: buildroot
Dear Thomas
I looked at my LD_LIBRARY_PATH variable which I've set in /etc/bash.bashrc
and it is:
export PYLON_ROOT=/opt/pylon3
export GENICAM_ROOT_V2_3=${PYLON_ROOT}/genicam
export GENICAM_CACHE=${PYLON_ROOT}/xml_cache
export
LD_LIBRARY_PATH=${PYLON_ROOT}/lib64:${GENICAM_ROOT_V2_3}/bin/Linux64_x64:${GENICAM_ROOT_V2_3}/bin/Linux64_x64/GenApi/Generic
export LD_LIBRARY_PATH=/home/parsa/Softwares/OPENCV/build/lib
as you can see no :: is presented in this file so I don't know how to
remove this :: from LD_LIBRARY_PATH and remake buildroot.
Can you provide some info about removing this :: ?
2014-06-28 11:06 GMT+04:30 Thomas Petazzoni <
thomas.petazzoni@free-electrons.com>:
> Dear Panahi Parsa,
>
> On Sat, 28 Jun 2014 09:15:18 +0430, Panahi Parsa wrote:
>
> >
> LD_LIBRARY_PATH=/opt/pylon3/lib64:/opt/pylon3/genicam/bin/Linux64_x64:/opt/pylon3/genicam/bin/Linux64_x64/GenApi/Generic::/home/parsa/Software/OPENCV/build/lib:/usr/local/lib:/home/parsa/Software/OPENCV/build/lib
>
> This LD_LIBRARY_PATH value, which has an empty member (notice the
> double : in the middle of the variable), is probably was confuses the
> glibc build system. Can you adjust your LD_LIBRARY_PATH to remove this
> empty member, and restart the build from scratch ("make clean all"),
> and let us know if that solves the problem? If it does, we'll add a
> check to warn users about this problem.
>
> Thanks!
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>
--
Parsa Panahi
D?partement de g?nie ?lectrique
?tudiant de l'?lectronique num?rique
Sharif Universit? de Technologie - T?h?ran - Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140628/5a427a03/attachment.html>
^ permalink raw reply [flat|nested] 14+ messages in thread* [Buildroot] Glibc LD_LIBRARAY_PATH error
2014-06-28 14:25 ` Panahi Parsa
@ 2014-06-28 14:28 ` Thomas Petazzoni
2014-06-28 15:12 ` Panahi Parsa
0 siblings, 1 reply; 14+ messages in thread
From: Thomas Petazzoni @ 2014-06-28 14:28 UTC (permalink / raw)
To: buildroot
Dear Panahi Parsa,
On Sat, 28 Jun 2014 18:55:53 +0430, Panahi Parsa wrote:
> I looked at my LD_LIBRARY_PATH variable which I've set in /etc/bash.bashrc
> and it is:
>
> export PYLON_ROOT=/opt/pylon3
> export GENICAM_ROOT_V2_3=${PYLON_ROOT}/genicam
> export GENICAM_CACHE=${PYLON_ROOT}/xml_cache
>
> export
> LD_LIBRARY_PATH=${PYLON_ROOT}/lib64:${GENICAM_ROOT_V2_3}/bin/Linux64_x64:${GENICAM_ROOT_V2_3}/bin/Linux64_x64/GenApi/Generic
>
> export LD_LIBRARY_PATH=/home/parsa/Softwares/OPENCV/build/lib
If you really have this code, then LD_LIBRARY_PATH would be equal to
just /home/parsa/Softwares/OPENCV/build/lib, because this last command
overrides any previous value of LD_LIBRARY_PATH. So clearly, you have
other pieces of code that are touching LD_LIBRARY_PATH.
Can you try, within the Buildroot source directory:
unset LD_LIBRARY_PATH
make clean all
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 14+ messages in thread* [Buildroot] Glibc LD_LIBRARAY_PATH error
2014-06-28 14:28 ` Thomas Petazzoni
@ 2014-06-28 15:12 ` Panahi Parsa
2014-06-28 15:36 ` Panahi Parsa
0 siblings, 1 reply; 14+ messages in thread
From: Panahi Parsa @ 2014-06-28 15:12 UTC (permalink / raw)
To: buildroot
Dear Thomas
you're right I've this one in my /etc/profile
export PYLON_ROOT=/opt/pylon3
export GENICAM_ROOT_V2_3=${PYLON_ROOT}/genicam
export GENICAM_CACHE=${PYLON_ROOT}/xml_cache
export
LD_LIBRARY_PATH=${PYLON_ROOT}/lib64:${GENICAM_ROOT_V2_3}/bin/Linux64_x64:${GENICAM_ROOT_V2_3}/bin/Linux64_x64/GenApi/Generic:$LD_LIBRARY_PATH
export
LD_LIBRARY_PATH=/home/parsa/Softwares/OPENCV/build/lib:$LD_LIBRARY_PATH
I ran your command and it is downloading and making packages and I think it
takes a long time. If I see the problem is solved I'll tell you about it.
Thanks again.
2014-06-28 18:58 GMT+04:30 Thomas Petazzoni <
thomas.petazzoni@free-electrons.com>:
> Dear Panahi Parsa,
>
> On Sat, 28 Jun 2014 18:55:53 +0430, Panahi Parsa wrote:
>
> > I looked at my LD_LIBRARY_PATH variable which I've set in
> /etc/bash.bashrc
> > and it is:
> >
> > export PYLON_ROOT=/opt/pylon3
> > export GENICAM_ROOT_V2_3=${PYLON_ROOT}/genicam
> > export GENICAM_CACHE=${PYLON_ROOT}/xml_cache
> >
> > export
> >
> LD_LIBRARY_PATH=${PYLON_ROOT}/lib64:${GENICAM_ROOT_V2_3}/bin/Linux64_x64:${GENICAM_ROOT_V2_3}/bin/Linux64_x64/GenApi/Generic
> >
> > export LD_LIBRARY_PATH=/home/parsa/Softwares/OPENCV/build/lib
>
> If you really have this code, then LD_LIBRARY_PATH would be equal to
> just /home/parsa/Softwares/OPENCV/build/lib, because this last command
> overrides any previous value of LD_LIBRARY_PATH. So clearly, you have
> other pieces of code that are touching LD_LIBRARY_PATH.
>
> Can you try, within the Buildroot source directory:
>
> unset LD_LIBRARY_PATH
> make clean all
>
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux, Kernel and Android engineering
> http://free-electrons.com
>
--
Parsa Panahi
D?partement de g?nie ?lectrique
?tudiant de l'?lectronique num?rique
Sharif Universit? de Technologie - T?h?ran - Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140628/9dbecaa5/attachment.html>
^ permalink raw reply [flat|nested] 14+ messages in thread* [Buildroot] Glibc LD_LIBRARAY_PATH error
2014-06-28 15:12 ` Panahi Parsa
@ 2014-06-28 15:36 ` Panahi Parsa
2014-06-28 15:44 ` Thomas Petazzoni
0 siblings, 1 reply; 14+ messages in thread
From: Panahi Parsa @ 2014-06-28 15:36 UTC (permalink / raw)
To: buildroot
Dear Thomas
my problem was solved by your solution I mean using "unset LD_LIBRARY_PATH"
solved the problem now I have 5 files in my output/images folder.
1). bzImage 2) grub.img 3) rootfs.cpio 4). rootfs.iso9660
5)rootfs.tar
I've configured buildroot for making a custom linux image for Corei7 and I
expected to give me only one .iso file and not 5 different files !! The
.iso file size as you've said in your lecture on youtube is only 16 MByte
and not 700 MB like ubuntu official releases. Now I got stuck in a dizzy
state about build root :
1). Does burning rootfs.iso9660 into a DVD and running it from my DVD ROM
install my customized ubuntu or I should do something else ?
2). I want to have a small graphic environment like the one used in
Angstrom Distribution is it possible to have that in build root ?
2014-06-28 19:42 GMT+04:30 Panahi Parsa <panahi.par3a@gmail.com>:
> Dear Thomas
> you're right I've this one in my /etc/profile
>
> export PYLON_ROOT=/opt/pylon3
> export GENICAM_ROOT_V2_3=${PYLON_ROOT}/genicam
> export GENICAM_CACHE=${PYLON_ROOT}/xml_cache
>
> export
> LD_LIBRARY_PATH=${PYLON_ROOT}/lib64:${GENICAM_ROOT_V2_3}/bin/Linux64_x64:${GENICAM_ROOT_V2_3}/bin/Linux64_x64/GenApi/Generic:$LD_LIBRARY_PATH
>
> export
> LD_LIBRARY_PATH=/home/parsa/Softwares/OPENCV/build/lib:$LD_LIBRARY_PATH
>
> I ran your command and it is downloading and making packages and I think
> it takes a long time. If I see the problem is solved I'll tell you about it.
>
> Thanks again.
>
>
> 2014-06-28 18:58 GMT+04:30 Thomas Petazzoni <
> thomas.petazzoni at free-electrons.com>:
>
> Dear Panahi Parsa,
>>
>> On Sat, 28 Jun 2014 18:55:53 +0430, Panahi Parsa wrote:
>>
>> > I looked at my LD_LIBRARY_PATH variable which I've set in
>> /etc/bash.bashrc
>> > and it is:
>> >
>> > export PYLON_ROOT=/opt/pylon3
>> > export GENICAM_ROOT_V2_3=${PYLON_ROOT}/genicam
>> > export GENICAM_CACHE=${PYLON_ROOT}/xml_cache
>> >
>> > export
>> >
>> LD_LIBRARY_PATH=${PYLON_ROOT}/lib64:${GENICAM_ROOT_V2_3}/bin/Linux64_x64:${GENICAM_ROOT_V2_3}/bin/Linux64_x64/GenApi/Generic
>> >
>> > export LD_LIBRARY_PATH=/home/parsa/Softwares/OPENCV/build/lib
>>
>> If you really have this code, then LD_LIBRARY_PATH would be equal to
>> just /home/parsa/Softwares/OPENCV/build/lib, because this last command
>> overrides any previous value of LD_LIBRARY_PATH. So clearly, you have
>> other pieces of code that are touching LD_LIBRARY_PATH.
>>
>> Can you try, within the Buildroot source directory:
>>
>> unset LD_LIBRARY_PATH
>> make clean all
>>
>> Thanks,
>>
>> Thomas
>> --
>> Thomas Petazzoni, CTO, Free Electrons
>> Embedded Linux, Kernel and Android engineering
>> http://free-electrons.com
>>
>
>
>
> --
>
>
> Parsa Panahi
> D?partement de g?nie ?lectrique
> ?tudiant de l'?lectronique num?rique
> Sharif Universit? de Technologie - T?h?ran - Iran
>
--
Parsa Panahi
D?partement de g?nie ?lectrique
?tudiant de l'?lectronique num?rique
Sharif Universit? de Technologie - T?h?ran - Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20140628/0091c5f3/attachment.html>
^ permalink raw reply [flat|nested] 14+ messages in thread* [Buildroot] Glibc LD_LIBRARAY_PATH error
2014-06-28 15:36 ` Panahi Parsa
@ 2014-06-28 15:44 ` Thomas Petazzoni
2014-07-01 18:11 ` Arnout Vandecappelle
0 siblings, 1 reply; 14+ messages in thread
From: Thomas Petazzoni @ 2014-06-28 15:44 UTC (permalink / raw)
To: buildroot
Dear Panahi Parsa,
On Sat, 28 Jun 2014 20:06:30 +0430, Panahi Parsa wrote:
> my problem was solved by your solution I mean using "unset LD_LIBRARY_PATH"
Ok. I'm not sure why we don't simply unset the LD_LIBRARY_PATH from our
main Makefile. Probably we should just do it.
> solved the problem now I have 5 files in my output/images folder.
> 1). bzImage 2) grub.img 3) rootfs.cpio 4). rootfs.iso9660
> 5)rootfs.tar
Right.
> I've configured buildroot for making a custom linux image for Corei7 and I
> expected to give me only one .iso file and not 5 different files !!
Well, the tarball has been created because your configuration has the
tarball image enabled. The other files are normal: bzImage is the
kernel image, grub.img is the bootloader, rootfs.cpio is the root
filesystem as cpio, and rootfs.iso9660 is the final ISO image, which
bundles the kernel image and root filesystem.
> The
> .iso file size as you've said in your lecture on youtube is only 16 MByte
> and not 700 MB like ubuntu official releases. Now I got stuck in a dizzy
> state about build root :
>
> 1). Does burning rootfs.iso9660 into a DVD and running it from my DVD ROM
> install my customized ubuntu or I should do something else ?
How can you believe a system generated by Buildroot will install a
"customized ubuntu". Buildroot has nothing to do with Ubuntu, Buildroot
is meant to build from source highly customized embedded Linux systems.
The minimal system only has Busybox (shell and basic command line
utilities). Any other component you may want has to be enabled in "make
menuconfig".
> 2). I want to have a small graphic environment like the one used in
> Angstrom Distribution is it possible to have that in build root ?
We have packages for X.org and Matchbox, which is what Angstrom is
using. You'll have to enable them in "make menuconfig". Though be aware
that Buildroot is not a tool that builds systems that work out of the
box: it merely builds all the packages needed, but there is often some
configuration files and other specific customization needed to make
everything work properly on a given hardware platform.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Glibc LD_LIBRARAY_PATH error
2014-06-28 15:44 ` Thomas Petazzoni
@ 2014-07-01 18:11 ` Arnout Vandecappelle
2014-07-01 20:07 ` Thomas Petazzoni
0 siblings, 1 reply; 14+ messages in thread
From: Arnout Vandecappelle @ 2014-07-01 18:11 UTC (permalink / raw)
To: buildroot
On 28/06/14 17:44, Thomas Petazzoni wrote:
> On Sat, 28 Jun 2014 20:06:30 +0430, Panahi Parsa wrote:
>
>> > my problem was solved by your solution I mean using "unset LD_LIBRARY_PATH"
> Ok. I'm not sure why we don't simply unset the LD_LIBRARY_PATH from our
> main Makefile. Probably we should just do it.
I could imagine an ancient build host where the developer has to build his own
python2.7 or other buildroot-dependencies. Not really realistic, though, because
then the executable should just set its DT_RPATH/DT_RUNPATH.
Also, we already have a check for LD_LIBRARY_PATH in dependencies.sh. It just
doesn't check for empty path elements, only for . path elements.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Glibc LD_LIBRARAY_PATH error
2014-07-01 18:11 ` Arnout Vandecappelle
@ 2014-07-01 20:07 ` Thomas Petazzoni
2014-07-01 21:09 ` Mike Zick
0 siblings, 1 reply; 14+ messages in thread
From: Thomas Petazzoni @ 2014-07-01 20:07 UTC (permalink / raw)
To: buildroot
Dear Arnout Vandecappelle,
On Tue, 01 Jul 2014 20:11:45 +0200, Arnout Vandecappelle wrote:
> >> > my problem was solved by your solution I mean using "unset LD_LIBRARY_PATH"
> > Ok. I'm not sure why we don't simply unset the LD_LIBRARY_PATH from our
> > main Makefile. Probably we should just do it.
>
> I could imagine an ancient build host where the developer has to build his own
> python2.7 or other buildroot-dependencies. Not really realistic, though, because
> then the executable should just set its DT_RPATH/DT_RUNPATH.
Yes.
> Also, we already have a check for LD_LIBRARY_PATH in dependencies.sh. It just
> doesn't check for empty path elements, only for . path elements.
Well, the idea would be to get rid of this check entirely, and replace
it by a simple unexport in the main Makefile.
What do you think?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Glibc LD_LIBRARAY_PATH error
2014-07-01 20:07 ` Thomas Petazzoni
@ 2014-07-01 21:09 ` Mike Zick
2014-07-02 6:47 ` Arnout Vandecappelle
0 siblings, 1 reply; 14+ messages in thread
From: Mike Zick @ 2014-07-01 21:09 UTC (permalink / raw)
To: buildroot
On Tue, 1 Jul 2014 22:07:03 +0200
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
> Dear Arnout Vandecappelle,
>
> On Tue, 01 Jul 2014 20:11:45 +0200, Arnout Vandecappelle wrote:
>
> > >> > my problem was solved by your solution I mean using "unset
> > >> > LD_LIBRARY_PATH"
> > > Ok. I'm not sure why we don't simply unset the LD_LIBRARY_PATH
> > > from our main Makefile. Probably we should just do it.
> >
> > I could imagine an ancient build host where the developer has to
> > build his own python2.7 or other buildroot-dependencies. Not really
> > realistic, though, because then the executable should just set its
> > DT_RPATH/DT_RUNPATH.
>
> Yes.
>
> > Also, we already have a check for LD_LIBRARY_PATH in
> > dependencies.sh. It just doesn't check for empty path elements,
> > only for . path elements.
>
> Well, the idea would be to get rid of this check entirely, and replace
> it by a simple unexport in the main Makefile.
>
What about the (I would hope, unusual) case where a user needs those
LD_LIBRARY_PATH settings to run a POST_**_SCRIPT ?
- - - -
Even a further out use case -
The applications requiring a LD_LIBRARY_PATH setting, where the
application(s) are used in a POST_**_SCRIPT, but the source isn't
available to build-in the appropriate DT_RUNPATH/DT_RPATH?
For this second use case -
How about putting a "host-patchelf" target in the host tools list?
This would allow the use case #2 above user to build the tool to
fix their host application to not require a LD_LIBRARY_PATH setting.
Note:
In my few weeks of use;
I have not been able to break ARM binaries with patchelf-0.8
regardless of the current documentation that claims ARM isn't
fully supported.
Mike
> What do you think?
>
> Best regards,
>
> Thomas
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Glibc LD_LIBRARAY_PATH error
2014-07-01 21:09 ` Mike Zick
@ 2014-07-02 6:47 ` Arnout Vandecappelle
2014-07-02 9:53 ` Mike Zick
0 siblings, 1 reply; 14+ messages in thread
From: Arnout Vandecappelle @ 2014-07-02 6:47 UTC (permalink / raw)
To: buildroot
On 01/07/14 23:09, Mike Zick wrote:
> On Tue, 1 Jul 2014 22:07:03 +0200
> Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:
>
>> Dear Arnout Vandecappelle,
>>
>> On Tue, 01 Jul 2014 20:11:45 +0200, Arnout Vandecappelle wrote:
>>
>>>>>> my problem was solved by your solution I mean using "unset
>>>>>> LD_LIBRARY_PATH"
>>>> Ok. I'm not sure why we don't simply unset the LD_LIBRARY_PATH
>>>> from our main Makefile. Probably we should just do it.
>>>
>>> I could imagine an ancient build host where the developer has to
>>> build his own python2.7 or other buildroot-dependencies. Not really
>>> realistic, though, because then the executable should just set its
>>> DT_RPATH/DT_RUNPATH.
>>
>> Yes.
>>
>>> Also, we already have a check for LD_LIBRARY_PATH in
>>> dependencies.sh. It just doesn't check for empty path elements,
>>> only for . path elements.
>>
>> Well, the idea would be to get rid of this check entirely, and replace
>> it by a simple unexport in the main Makefile.
>>
>
> What about the (I would hope, unusual) case where a user needs those
> LD_LIBRARY_PATH settings to run a POST_**_SCRIPT ?
>
> - - - -
>
> Even a further out use case -
> The applications requiring a LD_LIBRARY_PATH setting, where the
> application(s) are used in a POST_**_SCRIPT, but the source isn't
> available to build-in the appropriate DT_RUNPATH/DT_RPATH?
To be honest, I think that use case is so far out that we don't need to
consider it, and anyway the user has two easy solutions:
- don't use a POST_**_SCRIPT but wrap something around the Makefile;
- create a wrapper for the binaries that require LD_LIBRARY_PATH (like java apps
typically do).
>
> For this second use case -
> How about putting a "host-patchelf" target in the host tools list?
You wouldn't want to patch an out-of-buildroot-tree tool on every build
invocation, would you? Especially since that tool is probably in some shared,
non-writable place...
Regards,
Arnout
>
> This would allow the use case #2 above user to build the tool to
> fix their host application to not require a LD_LIBRARY_PATH setting.
>
> Note:
> In my few weeks of use;
> I have not been able to break ARM binaries with patchelf-0.8
> regardless of the current documentation that claims ARM isn't
> fully supported.
>
> Mike
>> What do you think?
>>
>> Best regards,
>>
>> Thomas
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
^ permalink raw reply [flat|nested] 14+ messages in thread
* [Buildroot] Glibc LD_LIBRARAY_PATH error
2014-07-02 6:47 ` Arnout Vandecappelle
@ 2014-07-02 9:53 ` Mike Zick
0 siblings, 0 replies; 14+ messages in thread
From: Mike Zick @ 2014-07-02 9:53 UTC (permalink / raw)
To: buildroot
On Wed, 02 Jul 2014 08:47:33 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> > Even a further out use case -
> > The applications requiring a LD_LIBRARY_PATH setting, where the
> > application(s) are used in a POST_**_SCRIPT, but the source isn't
> > available to build-in the appropriate DT_RUNPATH/DT_RPATH?
>
> To be honest, I think that use case is so far out that we don't need
> to consider it, and anyway the user has two easy solutions:
>
> - don't use a POST_**_SCRIPT but wrap something around the Makefile;
>
> - create a wrapper for the binaries that require LD_LIBRARY_PATH
> (like java apps typically do).
>
That all sounds reasonable to me.
Call this case "too far out" to consider,
or considered and tossed.
Mike
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2014-07-02 9:53 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-06-27 20:28 [Buildroot] Glibc LD_LIBRARAY_PATH error Panahi Parsa
2014-06-27 22:01 ` Thomas Petazzoni
2014-06-28 4:45 ` Panahi Parsa
2014-06-28 6:36 ` Thomas Petazzoni
2014-06-28 14:25 ` Panahi Parsa
2014-06-28 14:28 ` Thomas Petazzoni
2014-06-28 15:12 ` Panahi Parsa
2014-06-28 15:36 ` Panahi Parsa
2014-06-28 15:44 ` Thomas Petazzoni
2014-07-01 18:11 ` Arnout Vandecappelle
2014-07-01 20:07 ` Thomas Petazzoni
2014-07-01 21:09 ` Mike Zick
2014-07-02 6:47 ` Arnout Vandecappelle
2014-07-02 9:53 ` Mike Zick
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox