Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - xblitz

#1
General Development / Re: Compiling toolchain
July 27, 2012, 06:33:42 PM
Quote from: a1ex on July 27, 2012, 05:51:02 PM
Not sure what's the cause, but when I get that I run make clean, then make, and works. Probably something in the linker script.

wow that's strange!  This was a completely new checkout of the code.. unchanged but Makefile.inc to point to my toolchain ... but your make clean and then remake did the trick! 
#2
General Development / Re: Compiling toolchain
July 27, 2012, 05:34:58 PM
I installed 2 different toolchains: Sourcery and Launhpad.net  arm toolchains .. but the 2 of them make the same copiling error:

.....
[ CC       ]   vram.o
[ CC       ]   morse.o
[ CC       ]   aj_port.o
[ CC       ]   fps-engio.o
[ CC       ]   hdr.o
[ CC       ]   lv-img-engio.o
[ CC       ]   state-object.o
[ CC       ]   tasks.o
[ AR       ]   lib_a-setjmp.o
[ AR       ]   libstdio.a
[ LD       ]   magiclantern
boot-hack.o: In function `my_task_dispatch_hook':
boot-hack.c:(.text+0x60): undefined reference to `_task_overrides_start'
boot-hack.c:(.text+0x64): undefined reference to `_task_overrides_end'
boot-hack.o: In function `my_big_init_task':
boot-hack.c:(.text+0x3c4): undefined reference to `_init_funcs_start'
boot-hack.c:(.text+0x3c8): undefined reference to `_init_funcs_end'
boot-hack.c:(.text+0x3d4): undefined reference to `_tasks_start'
boot-hack.c:(.text+0x3d8): undefined reference to `_tasks_end'
boot-hack.o: In function `copy_and_restart':
boot-hack.c:(.text+0x4e4): undefined reference to `_bss_start'
boot-hack.c:(.text+0x4e8): undefined reference to `_bss_end'
config.o: In function `config_save_file':
config.c:(.text+0x244): undefined reference to `_config_vars_start'
config.c:(.text+0x250): undefined reference to `_config_vars_end'
config.o: In function `config_parse':
config.c:(.text+0x520): undefined reference to `_config_vars_start'
config.c:(.text+0x538): undefined reference to `_config_vars_end'
config.o: In function `get_config_vars_start':
config.c:(.text+0x5c0): undefined reference to `_config_vars_start'
config.o: In function `get_config_vars_end':
config.c:(.text+0x5cc): undefined reference to `_config_vars_end'
property.o: In function `prop_init':
property.c:(.text+0xc8): undefined reference to `_prop_handlers_start'
property.c:(.text+0xd0): undefined reference to `_prop_handlers_end'
property.o: In function `global_property_handler':
property.c:(.text+0x160): undefined reference to `_prop_handlers_start'
property.c:(.text+0x168): undefined reference to `_prop_handlers_end'
collect2: ld returned 1 exit status
make[1]: *** [magiclantern] Error 1
make[1]: Leaving directory `/root/magic-lantern/platform/50D.109'
make: *** [50D] Error 2
#3
Actually this weekend I had put a full battery in my Canon 50D with a pretty recent ML Build .. and I didnt actually use ML but only normal camera Operation for a couple of candid shots at a familly reunion...  put back the camera in the bag and left the camera "ON" like I usually forget ... (since anyways the camera goes to sleep after 1 minute or so..)   but a couple of hours later.. battery was dead!   so I am wondering if ML maybe was keeping the camera awake and still using power?   Im not sure..  I guess I would need to make some tests.. but since i saw this thread I wanted to let everyone know maybe someone else got this kind of behaviour