Author Topic: Getting started with development (Read 185339 times)

pompeiisneaks · « **Reply #50 on:** November 07, 2013, 05:40:24 AM »

Not sure I follow. I tried both the arm-elf-gcc and the arm-none-eabi-gcc and neither builds, both fail with similar errors. Is it my os that's causing this? Too old of libs or something?

1% · « **Reply #51 on:** November 07, 2013, 06:54:48 AM »

Maybe, look at requirements for TCC or try to compile without it and see if there are errors.

pompeiisneaks · « **Reply #52 on:** November 07, 2013, 07:30:55 PM »

Sorry, everything I find on this forum about the Tiny C Compiler is not helpful, I tried disabling it and it still fails to build with this error:

Code: [Select]

[ CC       ]   menuindex.o
[ CC       ]   focus.o
[ CC       ]   notify_box.o
[ CC       ]   dialog_test.o
[ CC       ]   vram.o
[ CC       ]   aj_port.o
[ CC       ]   fps-engio.o
[ CC       ]   shoot.o
../../src/shoot.c:519:60: warning: initialization makes pointer from integer without a cast [enabled by default]
../../src/shoot.c:519:1: error: initializer element is not constant
../../src/shoot.c:521:53: warning: initialization makes pointer from integer without a cast [enabled by default]
../../src/shoot.c:521:1: error: initializer element is not constant
make[1]: *** [shoot.o] Error 1
make[1]: Leaving directory `/home/pdavis/src/magiclantern/magic-lantern/platform/5D3.113'
make: *** [5D3] Error 2

Why would the arm linker complaining about eabi mismatches have anything to do with the tiny c compiler?

pompeiisneaks · « **Reply #53 on:** November 07, 2013, 11:31:41 PM »

Okay I'm pretty sure its just due to how old this machine's Fedora is. I'll figure something else out. Right now its failing to compile the docq target due to missing pandoc which isn't available in fedora until 18. I'm on like 11 or 13, sorry its an old host I had sitting around as my router I figured I could dual purpose. I'll give it a go on a more modern OS.

~Phil

pompeiisneaks · « **Reply #54 on:** November 08, 2013, 02:36:20 AM »

Well look at that, I can build 5D3 now on my fedora 19 laptop. It fails with the 60D when I just try and build all, but success with my camera at any rate. Oddly trying to build the arm toolkit from source fails due to texinfo 5.0 on fedora not being happy with the docs. I did some reading on how to fix it on a linux from scratch thread but gave up after an hour of mucking about and not getting the right lines fixed. (I have no idea how to fix texinfo files.) At any rate, I'm down that road now, thanks!

~Phil

1% · « **Reply #55 on:** November 08, 2013, 03:28:07 AM »

Quote

Why would the arm linker complaining about eabi mismatches have anything to do with the tiny c compiler?

Why? Because its a lot of PI code going into the binary and thats where it failed. Either way probably like you said, old libs, old gcc.

pompeiisneaks · « **Reply #56 on:** November 08, 2013, 05:57:02 PM »

Yup, thanks, I appreciate your help.

~Phil

Scoutman · « **Reply #57 on:** February 02, 2014, 06:48:44 PM »

Hi!

I always get this error:

Code: [Select]

username@ubuntu:~/daten/ml/magic-lantern/platform/50D.109$ make clean && make
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  50D_109.sym magiclantern.sym
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
[ VERSION  ]   ../../platform/50D.109/version.bin
[ CPP      ]   magiclantern.lds
/bin/sh: 1: /home/username/gcc-arm-none-eabi-4_7-2012q4/bin/arm-none-eabi-gcc-4.7.3: Permission denied
make: *** [magiclantern.lds] Error 1

I use Ubutuntu 12.04 and gcc 4.7.3. I have tried to use sudo but it didn't helped. All files have the same owner/group. I didn't understand the "Permission denied"!?

Any idea?

Marsu42 · « **Reply #58 on:** February 02, 2014, 07:25:41 PM »

Quote from: Scoutman on February 02, 2014, 06:48:44 PM

/bin/sh: 1: /home/username/gcc-arm-none-eabi-4_7-2012q4/bin/arm-none-eabi-gcc-4.7.3: Permission denied

Your gcc file doesn't seem to be executable, try "chmod 755 /home/username/gcc-arm-none-eabi-4_7-2012q4/bin/arm-none-eabi-gcc-4.7.3"

Scoutman · « **Reply #59 on:** February 02, 2014, 07:39:46 PM »

Thanks.

Now I get this error??

Code: [Select]

username@ubuntu:~/daten/ml/magic-lantern/platform/50D.109$ make clean && make
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  50D_109.sym magiclantern.sym
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o  dietlibc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
[ VERSION  ]   ../../platform/50D.109/version.bin
[ CPP      ]   magiclantern.lds
/bin/sh: 1: /home/username/gcc-arm-none-eabi-4_7-2012q4/bin/arm-none-eabi-gcc-4.7.3: not found
make: *** [magiclantern.lds] Error 1

Marsu42 · « **Reply #60 on:** February 02, 2014, 08:48:24 PM »

Quote from: Scoutman on February 02, 2014, 07:39:46 PM

Now I get this error??

Omg, you're 100% sure "/home/username/gcc-arm-none-eabi-4_7-2012q4/bin/arm-none-eabi-gcc-4.7.3" exists, has the correct usership and permissions? Try to view it in less to be sure, you should be getting a binary elf file.

Pelican · « **Reply #61 on:** March 20, 2014, 10:44:10 PM »

Is there an easy way to make minimalist autoexec.bin and put more and more stuff into it if everything is OK?
I mean I've made an autoexec.bin for 7D 2.0.5 but it's freezing so how can I start to check what's wrong with it?
(https://bitbucket.org/Pelican/7d.205/commits/all)

nanomad · « **Reply #62 on:** March 20, 2014, 11:04:44 PM »

Well, most of ML features are defined inside all-features.h. I'd start by undefining them all then working my way up

a1ex · « **Reply #63 on:** March 20, 2014, 11:19:26 PM »

You can go even earlier in the boot process, boot-hack.c, simply do nothing from my_big_init_task. If you do that, you'll only have the GUI task overriden.

If you still have problems, comment out the GUI task too; if not, start enabling stuff from my_big_init_task.

Pelican · « **Reply #64 on:** March 21, 2014, 12:04:21 AM »

Thanks for the hints guys!

CraigularB · « **Reply #65 on:** April 26, 2014, 05:38:59 AM »

Quote from: Marsu42 on February 02, 2014, 08:48:24 PM

Omg, you're 100% sure "/home/username/gcc-arm-none-eabi-4_7-2012q4/bin/arm-none-eabi-gcc-4.7.3" exists, has the correct usership and permissions? Try to view it in less to be sure, you should be getting a binary elf file.

Quote from: Scoutman on February 02, 2014, 07:39:46 PM

Thanks.

Now I get this error??

Code: [Select]
username@ubuntu:~/daten/ml/magic-lantern/platform/50D.109$ make clean && make [ RM ] *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin [ RM ] 50D_109.sym magiclantern.sym [ RM ] magiclantern.bin autoexec autoexec.map location.map [ RM ] autoexec-fir autoexec-fir.bin [ RM ] magiclantern.lds [ RM ] newlib-libc.a lib_a-setjmp.o lib_a-memcpy.o lib_a-memcpy-stub.o lib_a-memccpy.o lib_a-memset.o dietlibc.a [ RM ] version.c version.bin [ RM dir ] zip [ RM ] *.zip [ VERSION ] ../../platform/50D.109/version.bin [ CPP ] magiclantern.lds /bin/sh: 1: /home/username/gcc-arm-none-eabi-4_7-2012q4/bin/arm-none-eabi-gcc-4.7.3: not found make: *** [magiclantern.lds] Error 1

I know these are old, but I hit the same issue tonight on a clean install of Ubuntu 14.04 64-bit LTS. It has to do with running a 32-bit app on a 64-bit machine. I could see the files in the folder, I could run 'ls' and have it return the files, but trying to run any of them would result in bash saying it didn't exist. If you reinstall the 32-bit libs it fixes it:

Code: [Select]

sudo apt-get install --reinstall libc6-i386
This comes from an old bug that was supposedly fixed: Launchpad bug report

On an older version of Ubuntu you may also be able to do

Code: [Select]

sudo apt-get install ia32-libs
per this Superuser question but I can't verify that.

Hope this helps anybody who may be stumped.

Rewind · « **Reply #66 on:** June 12, 2014, 04:03:02 PM »

Guys, what am I doing wrong?

dslrrookie2 · « **Reply #67 on:** June 12, 2014, 04:10:06 PM »

Quote from: Rewind on June 12, 2014, 04:03:02 PM

Guys, what am I doing wrong?

I had the same issue ... resolved by installing docutils

Also, I had to run Make for the platform builds prior to building modules.

http://pkgs.org/ubuntu-12.04/ubuntu-main-i386/python-docutils_0.8.1-4ubuntu1_all.deb.html

Rewind · « **Reply #68 on:** June 12, 2014, 05:36:12 PM »

Quote from: dslrrookie2 on June 12, 2014, 04:10:06 PM

... resolved by installing docutils

Thanks a lot! It works now.

stoopkid · « **Reply #69 on:** August 03, 2014, 01:22:35 AM »

I get this error...

Code: [Select]

nick@nick-mint ~/magic-lantern/platform/550D.109 $ make clean && make
[ RM ]  *.o *.d autoexec autoexec.bin magiclantern magiclantern.bin
[ RM ]  550D_109.sym magiclantern.sym
[ RM ]  magiclantern.bin autoexec autoexec.map location.map
[ RM ]  autoexec-fir autoexec-fir.bin
[ RM ]  magiclantern.lds
[ RM ]  dietlibc.a newlib-libc.a newlib-libm.a gcc-libgcc.a
[ RM ]  version.c version.bin
[ RM dir ]  zip
[ RM ]  *.zip
[ VERSION  ]   ../../platform/550D.109/version.bin
[ CPP      ]   magiclantern.lds
/bin/sh: /home/nick/gcc-arm-none-eabi-4_8-2014q2/bin/arm-none-eabi-gcc-4.8.4: No such file or directory
make: *** [magiclantern.lds] Error 1

However the file is there and executable...

Code: [Select]

nick@nick-mint ~/magic-lantern/platform/550D.109 $  ls -l /home/nick/gcc-arm-none-eabi-4_8-2014q2/bin/arm-none-eabi-gcc-4.8.4
-rwxr-xr-x 2 nick nick 676756 Jun  8 12:12 /home/nick/gcc-arm-none-eabi-4_8-2014q2/bin/arm-none-eabi-gcc-4.8.4

I don't really know how to troubleshoot this any further.

ayshih · « **Reply #70 on:** August 03, 2014, 05:08:18 AM »

It sounds like you may be having the same 32-bit/64-bit issue discussed earlier in this thread. See the solution a few posts above yours: http://www.magiclantern.fm/forum/index.php?topic=991.msg112954#msg112954

stoopkid · « **Reply #71 on:** August 04, 2014, 12:25:20 AM »

Thanks it works now.

dpjpandone · « **Reply #72 on:** August 11, 2014, 05:40:48 PM »

I'm trying to use the prebuilt at work and when I try to launch the Magic Lantern machine, I keep getting this:

Failed to open a session for the virtual machine MagicLantern.

The virtual machine 'MagicLantern' has terminated unexpectedly during startup with exit code 1.

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

philmoz · « **Reply #73 on:** August 11, 2014, 09:49:37 PM »

Quote from: dpjpandone on August 11, 2014, 05:40:48 PM

I'm trying to use the prebuilt at work and when I try to launch the Magic Lantern machine, I keep getting this:

Failed to open a session for the virtual machine MagicLantern.

The virtual machine 'MagicLantern' has terminated unexpectedly during startup with exit code 1.

Result Code: E_FAIL (0x80004005)
Component: Machine
Interface: IMachine {480cf695-2d8d-4256-9c7c-cce4184fa048}

On Windows, any error code ending in 005, is usually a permission problem (access denied).

The machine may be locked down preventing VirtualBox (or whatever hypervisor you are using) from gaining enough access to the hardware.

Have you tried running it as administrator?

Phil.

dpjpandone · « **Reply #74 on:** August 12, 2014, 07:12:48 PM »

yes phil, I right click on virtual box and select "run as administrator" any other hints?

News:

Author Topic: Getting started with development (Read 185339 times)