Re: [U-Boot] Compiling fw_printenv tool

2014-01-17 Thread Detlev Zundel
Hi Alexey, [...] > In case someone needs that (before the Makefile changes are accepted), > I used the > > make HOSTCC='arm-none-linuex-gnueabi-gcc -static' env > command to get it working. We usually do put options into the HOSTCC variable. Of course one can argue about that, but the make docu

Re: [U-Boot] Compiling fw_printenv tool

2014-01-17 Thread Alexey Smishlayev
On 2014.01.17. 16:30, Detlev Zundel wrote: Hi Alexey, [...] I've googled it and sorted it out. The problem was that executable was dynamically linked and the *.so was not found on the embedded system. I compiled it with -static and it runs. I'm glad you solved the problem. I only like for su

Re: [U-Boot] Compiling fw_printenv tool

2014-01-17 Thread Detlev Zundel
Hi Gerhard, [...] Ok, thinking about your answer it kind of makes sense that fw_printenv can easily be used _out of tree_ without much hassle. On the other hand, as part of the build process, it is surely "something to run on the target" and thus something to compile with CC and not HOSTCC. Bu

Re: [U-Boot] Compiling fw_printenv tool

2014-01-17 Thread Detlev Zundel
Hi Masahiro-san, >> > How do I cross compile it for my embedded system? Do I just set the >> > HOSTCC environment variable in the Makefile? >> >> No changes in any makefiles are needed, just do >> >> make HOSTCC=arm-none-linuex-gnueabi-gcc env > > It looks weird to me. You're not alone actually

Re: [U-Boot] Compiling fw_printenv tool

2014-01-17 Thread Detlev Zundel
Hi Alexey, [...] > I've googled it and sorted it out. The problem was that executable was > dynamically linked and the *.so was not found on the embedded > system. I compiled it with -static and it runs. I'm glad you solved the problem. I only like for such answers to show up in archives so tha

Re: [U-Boot] Compiling fw_printenv tool

2014-01-15 Thread Gerhard Sittig
On Tue, Jan 14, 2014 at 20:47 +0900, Masahiro Yamada wrote: > > Hello Detlev > > > > > How do I cross compile it for my embedded system? Do I just set the > > > HOSTCC environment variable in the Makefile? > > > > No changes in any makefiles are needed, just do > > > > make HOSTCC=arm-none-lin

Re: [U-Boot] Compiling fw_printenv tool

2014-01-14 Thread Masahiro Yamada
Hello Detlev > > How do I cross compile it for my embedded system? Do I just set the > > HOSTCC environment variable in the Makefile? > > No changes in any makefiles are needed, just do > > make HOSTCC=arm-none-linuex-gnueabi-gcc env It looks weird to me. I think HOSTCC should be always "gcc"

Re: [U-Boot] Compiling fw_printenv tool

2014-01-14 Thread Alexey Smishlayev
Hello Detlev, On 2014.01.14. 12:54, Detlev Zundel wrote: Hi Alexey, Dear Detlev, I ran $ make HOSTCC=arm-none-linux-gnueabi-gcc env and got the tools/env/fw_printenv executable. But the Make command returned error: strip: Unable to recognise the format of the input file `fw_printenv' make[1]:

Re: [U-Boot] Compiling fw_printenv tool

2014-01-14 Thread Detlev Zundel
Hi Alexey, > Dear Detlev, > > I ran > $ make HOSTCC=arm-none-linux-gnueabi-gcc env > and got the tools/env/fw_printenv executable. But the Make command > returned error: > strip: Unable to recognise the format of the input file `fw_printenv' > make[1]: *** [fw_printenv] Error 1 > > I guess, HOSTST

Re: [U-Boot] Compiling fw_printenv tool

2013-11-29 Thread Alexey Smishlayev
Dear Detlev, I ran $ make HOSTCC=arm-none-linux-gnueabi-gcc env and got the tools/env/fw_printenv executable. But the Make command returned error: strip: Unable to recognise the format of the input file `fw_printenv' make[1]: *** [fw_printenv] Error 1 I guess, HOSTSTRIP variable also has to be

Re: [U-Boot] Compiling fw_printenv tool

2013-11-29 Thread Detlev Zundel
Hi Alexey, > I'm trying to compile fw_printenv, to work with U-Boot environment > variables under my linux os. I'm using commands: > $ cd u-boot/ > $ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- env > > The tool compiles successfully, I get the executable under > u-boot/tools/env/fw_printen