Messages

Did more green bar confirm tests in sunlight. Green bar confirm may display prior to sharpest focus. 
...
It seems that your problem is trying to use Magic Zoom and Focus Peak at the same time. As stated in my last post, Focus Peak dots are not displayed when magic zoom window is being displayed. In your setup (+) zoom, MZ is displayed until you hit the button again. You should have focus peak dots when MZ is not displayed.

Thanks kihlbahkt for your detailed reply and the indoor and outdoor tests! I want to get the most out of everything you looked into. Since I mainly shoot landscapes with a fixed focal length lens, I will attempt to do this by outlining my manual focus process for landscapes.

(By the way I use old m42 Pentax screw mount manual focus lenses with an adapter that contains no corrective optics - the Canon 600D dimensions accommodate the m42 register requirements for achieving infinity focus without a corrective optic in the adapter. Also, I don't believe I observed any difference in the problems I am describing here when I was using my Canon 18-55mm kit lens, but I will confirm that.)

A couple quick comments first:
1. Yes, Green bar confirm may indeed display prior to sharpest focus. So then I am inclined to use x10 magnification to check it.
2. As for there being a problem using Magic Zoom (MZ) and Focus Peak (FP) at the same time, they are two separate features which I have enabled in Magic Lantern (ML) at the same time. I just want to be clear there's no problem there.

Now, my manual focus process: Initially I don't have MZ window open, and I rely on FP for red dots on high contrast lines. Then I open MZ window with x3 magnification and continue focus watching for Green Bar confirm (and yes, FP is momentarily inactive with MZ open). Then I use ML feature to zoom by pressing shutter button halfway and continue manual focus at x10 magnification as needed for various landscape details.

I suspect my manual focus process is revealing some problems in ML:
1. FP red dots often peak then become fewer when I stop adjusting focus. (But you do not observe this behavior, correct?)
2. Green bar confirm in MZ seems somewhat random. (Instead, you see Green Bar confirm sometimes before sharpest focus, correct?)
3. Regardless of "Increase SharpContrast" setting I no longer see increased sharpness "somewhat like focus peaking" (per the User Guide) anywhere - not in LiveView, or FP, or MZ, or x5 or x10 magnification. (I am not sure I understand what you observed in this case. Can you comment more on this?)

I hope all that makes sense and that you would please comment further - particularly on the questions I've asked above.

Thanks!

I have read through the FAQ, looked over the current posts, and searched for solutions to problems I am having with some Magic Lantern manual focus features. But I have not found any posts that address the manual focus features I am having problems with (Focus Peak, Magic Zoom, and SharpContrast) on my Canon T3i (600D). So I will describe the problems in reference to how they should work according to the Magic Lantern v2.3 User Guide.

Problem: The User Guide regarding Focus Peak says "High-contrast lines will be marked by blinking dots showing which part of the image is in focus." In my case on my Canon T3i (600D) lots of blinking dots do appear around high-contrast lines as I adjust the manual focus ring on the lens, but the dots appear only briefly and then most of them disappear leaving a relatively small number of blinking dots around high-contrast lines. I've tried adjusting Focus Peak settings in the Overlay menu, but I have not found settings that make the Focus Peak feature consistently mark high-contrast lines with lots of blinking dots that persist around the portion of the image that is in fact in focus after I have stopped adjusting the manual focus on the lens.

Problem: The User Guide regarding Magic Zoom says "Displays a zoom box for focus assist ... When ML believes you have achieved perfect focus, Magic Zoom will display a focus confirmation (customizable)." I use Magic Zoom in the Zoom In (+) trigger mode with "Green Bars" as focus confirmation. In my case on my Canon T3i (600D) focus confirmation (Green Bars) often illuminates at the top and bottom of the zoom window when the portion of the image being focused on is *not* actually in focus. And when the Green Bars do appear when "perfect" focus is achieved they often appear only briefly and then disappear even if my hand is not touching the focus ring on the lens and the portion of the image in the Magic Zoom window is in fact still in focus.

Problem: The User Guide regarding "Increase SharpContrast" says "when zoom is active, sharpness and contrast are maximized. Increased sharpness works somewhat like focus peaking." This is the most important Magic Lantern focus feature to me. It's enabled by selecting "Increase SharpContrast" in "LiveView zoom settings" of the Prefs menu. This feature has worked only once for me - and it was AMAZING! Specifically, after enabling it, I'm sure I pressed Zoom In (+) and I thought the Magic Zoom window popped up and I could see Focus Peak like behavior occurring within the zoom window (with magnification) as I adjusted the manual focus ring on the lens. But now no matter what I try I can't get any Focus Peak like activity when zoom is active either through pressing Zoom In (+) or by holding the shutter button halfway down.

If anyone cares to comment on how I may be misusing any of these features and how I might use them correctly I would be very grateful. Shortly here I will begin to split these problems into separate posts so anyone who is interested can focus on a specific problem. And for any problem that remains unresolved I will open a bug report as appropriate.

Thanks!

I believe this topic offers some insight into some of my questions.
http://www.magiclantern.fm/forum/index.php?topic=1266.0

Namely, the autoexec.bin for a specific platform contains the .fir code for that platform. And so then to get that code on my camera I would run make install in the appropriate platform directory. Is this correct?

Having repeated the above steps but from within ~/magic-lantern/platform/600D.102$ is it time now to put the SD card back into my T3i (600D) camera? Are there any extra steps after putting the SD card into the camera? Do I simple turn on the camera? How do I tell if the camera is running my newly built ML?

Do you have the card mounted under /media/EOS_DIGITAL?

Exactly! I've got the card mounted under /media/EOS_DIGITAL! Somehow Ubuntu just knew to mount it there when I plugged it in. I guess this works because this is the SD card that has the currently installed ML 2.3 release. Very clever ML people!

Now finally I'm running "make install" (no sudo this time) with some confidence for the first time and  ... And it appears to have successfully written some files to the card! Fantastic!!!

Now let's have a look and see what got installed/updated on my SD card in comparison to the ML 2.3 files that were previously on the card.
./EOS_DIGITAL/autoexec.bin (newly built but which autoexec.bin from my build is it? guess I will have to compare sizes and timestamps)
./EOS_DIGITAL/*.fir (none were updated. my understanding is new .fir code for a specific platform is stuffed into that platform's autoexec.bin???)
./EOS_DIGITAL/ML/cropmks/*.bmp (all of these files are newly built but why?)
./EOS_DIGITAL/ML/data/*.lut (all of these files are newly built and again why?)
./EOS_DIGITAL/ML/data/FONTS.DAT (newly built and yet again why?)
./EOS_DIGITAL/ML/doc/menuidx.data (not updated. but what is it???)
./EOS_DIGITAL/ML/doc/*.bmh (none got updated. but I never did "make docs" so maybe I could try that for my next make install)
./EOS_DIGITAL/ML/README (no comment needed)
./EOS_DIGITAL/SETTINGS/MAGIC.CFG (not updated ... apparently contains my current ML 2.3 settings)

So the most important update appears to be ./EOS_DIGITAL/autoexec.bin which upon comparing sizes and timestamps is the same autoexec.bin from my ~/magic-lattern/platform/all folder. So now the question is which .fir code if any does it contain? Or am I confused? Do I need to repeat all of this but from within the platform folder of my device (i.e. T3i or 600D as it is referred to here)

Do you have the card mounted under /media/EOS_DIGITAL?

No. I am just beginning to get the idea I need to do something like that.

And I'm looking at Makefile.inc and I see I'm missing a few things like definitions for PLUGINS_DIR and CF_CARD.

So there's a whole gamut of details regarding building ML and then ... actually installing it to a real CF card or SD card ... and I am missing those details. Is this explained anywhere? I really need more detailed help here on this step.

Actually the errors from: "sudo make install" are worse than what I just reported.


/home/vtrandal/magic-lantern/plugins/lua/../symtblgen.rb:25: command not found: arm-elf-readelf -r lua
Found 0 symbols
rm lua.bin.reloc
make[2]: Leaving directory `/home/vtrandal/magic-lantern/plugins/lua'
make[2]: Entering directory `/home/vtrandal/magic-lantern/plugins/testplug'
[ LD       ]   testplug
[ OBJCOPY  ]   testplug.bin.reloc
[ SYMTBLG  ]   testplug.bin
/home/vtrandal/magic-lantern/plugins/testplug/../symtblgen.rb:25: command not found: arm-elf-readelf -r testplug
Found 0 symbols
rm testplug.bin.reloc
make[2]: Leaving directory `/home/vtrandal/magic-lantern/plugins/testplug'
make[1]: Leaving directory `/home/vtrandal/magic-lantern/plugins'
mkdir -p /media/EOS_DIGITAL/ML/
mkdir -p /media/EOS_DIGITAL/ML/settings/
mkdir -p /media/EOS_DIGITAL/ML/data/
mkdir -p /media/EOS_DIGITAL/ML/cropmks/
cp platform/all/autoexec.bin /media/EOS_DIGITAL
cp /home/vtrandal/magic-lantern/src/FONTS.DAT /media/EOS_DIGITAL/ML/data/
cp vram/*.lut /media/EOS_DIGITAL/ML/data/
cp /home/vtrandal/magic-lantern/cropmks/*.bmp /media/EOS_DIGITAL/ML/cropmks/
umount /media/EOS_DIGITAL
umount: /media/EOS_DIGITAL: not mounted
make: *** [install] Error 1

"make install" should do the trick. You can run it from main dir or from a platform dir.

Thanks. I even tried: "sudo make install" and that had errors.

But even if it succeeded just exactly what is the output supposed to be and what specifically do I do with any of the output files? For example what files do I copy to my SD card? And how do I prepare my camera to run my ML build? And many more such questions which I am hoping are documented somewhere that I somehow must be overlooking. I can't seem to find answers to these questions even if they are right in front of my face. I'm lost. Sorry.

Anyway here are the errors I get with: "sudo make install"

mkdir -p /media/EOS_DIGITAL/ML/
mkdir -p /media/EOS_DIGITAL/ML/settings/
mkdir -p /media/EOS_DIGITAL/ML/data/
mkdir -p /media/EOS_DIGITAL/ML/cropmks/
cp platform/all/autoexec.bin /media/EOS_DIGITAL
cp /home/vtrandal/magic-lantern/src/FONTS.DAT /media/EOS_DIGITAL/ML/data/
cp vram/*.lut /media/EOS_DIGITAL/ML/data/
cp /home/vtrandal/magic-lantern/cropmks/*.bmp /media/EOS_DIGITAL/ML/cropmks/
umount /media/EOS_DIGITAL
umount: /media/EOS_DIGITAL: not mounted
make: *** [install] Error 1

You mean this? https://docs.google.com/spreadsheet/viewform?formkey=dG1FMjVQUEtjWV8zSlpaeEZtZDBQZ2c6MQ

Wow that is really professional looking, but I need something much more basic than that. I don't even know what is the output from the compiler. What file or files do I copy to my SD card and what do I do after that? Do I need to low level format again or just overwrite something on a working 2.3 installation?

I don't even know step one on how test ML once I've built it. I'm completely lost. Why don't I get .fir files when I build? Just exactly what is the output of the compiler and where is it? I've got a ton of questions. Sorry I can't seem to find this. I must be overlooking something in the FAQ.

I'm really sorry if this is in an FAQ somewhere but I can't find it.

This is the most informative thread I have read regarding Magic Lantern development. For us non-developers the tools that are available to us compile the code to an autoexec.bin file? It also generates a magiclantern.bin file. What's that for?

From what I have read in this thread I assume that after successfully installing ML 2.3, I can then replace the autoexec.bin on my SD card with the freshly built autoexec.bin for my T3i (600D) to test it? Do I leave everything else on the SD card as is?

Thank you.

With that change the build does seem to progress further.

But it now terminates with an error similar to that described here:
http://www.magiclantern.fm/forum/index.php?topic=1768.0

So, a little progress.

I too am now getting this error since I added mlong-calls to CFLAGS in Makefile.inc. At least the build seems to take a little longer to fail.

As an alternative I installed Ubuntu 10.04.4 LTS 32-bit, and I guess it builds ML OK.

But the build just stops as follows:
Found 40 symbols
rm testplug.bin.reloc
make[2]: Leaving directory `/home/vtrandal/magic-lantern/plugins/testplug'
make[1]: Leaving directory `/home/vtrandal/magic-lantern/plugins'
vtrandal@ubuntu:~/magic-lantern$

And I can't quite tell exactly what or where the output is. Using locate I find a lot of new autoexec.bin files but no new .fir files.

Use -mlong-calls on 64-bit systems. It will produce slightly larger binaries. From my experience, I have no problems compiling and running ML on 64-bit systems. I use Ubuntu 12.04 64-bit native, not VM.

Sounds good to me. But I have no clue what that is. Can you explain?

I just made a long post in General Development Discussion about my difficulty building ML using the ARM toolchain I built in my 64-bit Ubuntu 10.04 VM.

From reading this thread I gather that it's because my Ubuntu 10.04 is 64-bit and building a correctly functioning ARM toolchain for ML is just not yet working in 64-bit Linux distributions? I guess I failed to read the fine print somewhere My bad.

Oh well I'm installing Ubuntu 12.04 LTS 32-bit right now. I hope that's a good direction to go in. I would much rather have another Ubuntu VM to backup and maintain that develop ML in Windows 7.

I'm just finished downloading Ubuntu 12.04 LTS 32-bit. And I'm going to install it with Vmware Workstation and create a dedicated 32-bit ML development environment. Sound OK? I really don't to do ML development in Windows 7.

After reading topic: ARM Toolchain in General Development Discussion, I gather that building the ARM toolchain for ML under my 64-bit Ubuntu 10.04 installation just isn't going to result in compiler that will work correctly. Is that a correct conclusion?

This is based on the instructions provided at http://www.magiclantern.fm/develop
When I refer to the instructions I mean the instructions at the above page and it's subpages.

Step 1. Get the source code. I got it just like it says below so I don't have to do ""hg update unified" later.
hg clone -r unified https://bitbucket.org/hudson/magic-lantern

Step 2. Setup up the compiler. Here I did things a little differently
- I skipped downloading summon-arm because it's in the ML source code toolchain folder.
- I downloaded and executed prepare.ubuntu.sh (but this is also in the ML source code toolchain folder )
- In ~/magic-lantern/toolchain I edited summon-arm and added the --no-passive-ftp parameter to the wget line per the instructions.
- I ran summon-arm as follows: ./summon-arm SUDO=sudo (when it needed root privileges I gave it the root password)
- I tested the toolchain by building the hello.c per the instructions.
- I added ~/arm-toolchain462/bin to my PATH
- I tried running make in the ~/magic-lantern folder as follows: make, make clean, make (but make encountered errors and failed each time)
- I also tried running make 600D as follows: make 600D, make clean, make 600D (but again make encountered errors and failed each time)

At this point I'm not sure my ML toolchain build is valid because it should just build ML with no problem right?

But... I did only glance through the summon-arm README without making any changes because I thought all that would be covered by downloading and running prepare.ubuntu.sh ... I have little idea what or where to set all those things to in the README

Here's the entire output with errors that I get with running make:
vtrandal@vtrandal-android:~/magic-lantern$ make
make -C /home/vtrandal/magic-lantern/platform/60D.111
make[1]: Entering directory `/home/vtrandal/magic-lantern/platform/60D.111'
[ CPP      ]   magiclantern.lds
[ AS       ]   ../../src/entry.o
[ CC       ]   boot-hack.o
[ AS       ]   stubs.o
[ VERSION  ]   ../../platform/60D.111/version.c
[ CC       ]   version.o
[ CC       ]   bmp.o
[ CC       ]   font-dyn.o
[ CC       ]   config.o
[ CC       ]   menu.o
[ CC       ]   debug.o
[ CC       ]   stdio.o
[ CC       ]   audio.o
[ CC       ]   bitrate.o
[ CC       ]   tweaks.o
../../src/tweaks.c: In function 'handle_arrow_keys':
../../src/tweaks.c:1566:17: warning: passing argument 1 of 'aperture_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:228:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1580:17: warning: passing argument 1 of 'aperture_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:228:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1593:17: warning: passing argument 1 of 'iso_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:226:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1594:17: warning: passing argument 1 of 'shutter_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:227:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1607:17: warning: passing argument 1 of 'iso_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:226:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1608:17: warning: passing argument 1 of 'shutter_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:227:6: note: expected 'void *' but argument is of type 'int'
[ CC       ]   lens.o
[ CC       ]   property.o
[ CC       ]   propvalues.o
[ CC       ]   gui.o
[ CC       ]   gui-common.o
[ CC       ]   misc.o
[ CC       ]   picstyle.o
[ CC       ]   cfn.o
[ CC       ]   zebra.o
[ CC       ]   shoot.o
[ CC       ]   chdk-gui_draw.o
[ CC       ]   movtweaks.o
[ CC       ]   my_memset.o
[ CC       ]   menuhelp.o
cd ../../doc; python menuindex.py
Could not open menuindex.txt
mkdir: cannot create directory `cam': File exists
[ CC       ]   menuindex.o
[ CC       ]   af_patterns.o
[ CC       ]   focus.o
[ CC       ]   notify_box.o
[ CC       ]   bootflags.o
[ CC       ]   dialog_test.o
[ CC       ]   vram.o
[ CC       ]   morse.o
[ CC       ]   liveview.o
[ CC       ]   reloc.o
[ CC       ]   aj_port.o
[ CC       ]   fps-engio.o
[ CC       ]   cartridge.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_init_task':
boot-hack.c:(.text+0x14): relocation truncated to fit: R_ARM_PC24 against symbol `get_current_task' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x4c): relocation truncated to fit: R_ARM_PC24 against symbol `init_task' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x100): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x128): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x138): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x154): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x16c): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x1e8): relocation truncated to fit: R_ARM_PC24 against symbol `task_create' defined in *ABS* section in magiclantern
boot-hack.o: In function `my_assert_handler':
boot-hack.c:(.text+0x234): relocation truncated to fit: R_ARM_PC24 against symbol `get_current_task' defined in *ABS* section in magiclantern
boot-hack.o: In function `my_big_init_task':
boot-hack.c:(.text+0x2b8): relocation truncated to fit: R_ARM_PC24 against symbol `call' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x2e8): additional relocation overflows omitted from the output
collect2: ld returned 1 exit status
make[1]: *** [magiclantern] Error 1
make[1]: Leaving directory `/home/vtrandal/magic-lantern/platform/60D.111'
make: *** [60D] Error 2
vtrandal@vtrandal-android:~/magic-lantern$

Here's the entire output with errors that I get with running make 600D:
vtrandal@vtrandal-android:~/magic-lantern$ make 600D
make -C /home/vtrandal/magic-lantern/platform/600D.102
make[1]: Entering directory `/home/vtrandal/magic-lantern/platform/600D.102'
[ CPP      ]   magiclantern.lds
[ AS       ]   ../../src/entry.o
[ CC       ]   boot-hack.o
[ AS       ]   stubs.o
[ VERSION  ]   ../../platform/600D.102/version.c
[ CC       ]   version.o
[ CC       ]   bmp.o
[ CC       ]   font-dyn.o
[ CC       ]   config.o
[ CC       ]   menu.o
[ CC       ]   debug.o
[ CC       ]   stdio.o
[ CC       ]   audio.o
[ CC       ]   bitrate.o
[ CC       ]   tweaks.o
../../src/tweaks.c: In function 'handle_arrow_keys':
../../src/tweaks.c:1566:17: warning: passing argument 1 of 'aperture_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:228:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1580:17: warning: passing argument 1 of 'aperture_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:228:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1593:17: warning: passing argument 1 of 'iso_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:226:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1594:17: warning: passing argument 1 of 'shutter_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:227:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1607:17: warning: passing argument 1 of 'iso_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:226:6: note: expected 'void *' but argument is of type 'int'
../../src/tweaks.c:1608:17: warning: passing argument 1 of 'shutter_toggle' makes pointer from integer without a cast [enabled by default]
../../src/lens.h:227:6: note: expected 'void *' but argument is of type 'int'
[ CC       ]   lens.o
[ CC       ]   property.o
[ CC       ]   propvalues.o
[ CC       ]   gui.o
[ CC       ]   gui-common.o
[ CC       ]   misc.o
[ CC       ]   picstyle.o
[ CC       ]   cfn.o
[ CC       ]   zebra.o
[ CC       ]   shoot.o
[ CC       ]   chdk-gui_draw.o
[ CC       ]   movtweaks.o
[ CC       ]   my_memset.o
[ CC       ]   menuhelp.o
cd ../../doc; python menuindex.py
Could not open menuindex.txt
mkdir: cannot create directory `cam': File exists
[ CC       ]   menuindex.o
[ CC       ]   af_patterns.o
[ CC       ]   focus.o
[ CC       ]   notify_box.o
[ CC       ]   bootflags.o
[ CC       ]   dialog_test.o
[ CC       ]   vram.o
[ CC       ]   morse.o
[ CC       ]   liveview.o
[ CC       ]   reloc.o
[ CC       ]   aj_port.o
[ CC       ]   fps-engio.o
[ CC       ]   cartridge.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_assert_handler':
boot-hack.c:(.text+0x18): relocation truncated to fit: R_ARM_PC24 against symbol `get_current_task' defined in *ABS* section in magiclantern
boot-hack.o: In function `my_big_init_task':
boot-hack.c:(.text+0x9c): relocation truncated to fit: R_ARM_PC24 against symbol `call' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0xcc): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x10c): relocation truncated to fit: R_ARM_PC24 against symbol `task_create' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x120): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.o: In function `my_dump_task':
boot-hack.c:(.text+0x31c): relocation truncated to fit: R_ARM_PC24 against symbol `call' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x324): relocation truncated to fit: R_ARM_PC24 against symbol `msleep' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x32c): relocation truncated to fit: R_ARM_PC24 against symbol `call' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x334): relocation truncated to fit: R_ARM_PC24 against symbol `call' defined in *ABS* section in magiclantern
boot-hack.c:(.text+0x340): relocation truncated to fit: R_ARM_PC24 against symbol `call' defined in *ABS* section in magiclantern
boot-hack.o: In function `hold_your_horses':
boot-hack.c:(.text+0x37c): additional relocation overflows omitted from the output
collect2: ld returned 1 exit status
make[1]: *** [magiclantern] Error 1
make[1]: Leaving directory `/home/vtrandal/magic-lantern/platform/600D.102'
make: *** [600D] Error 2
vtrandal@vtrandal-android:~/magic-lantern$