Author Topic: General compiling problem  (Read 195 times)

waelti_de

  • New to the forum
  • *
  • Posts: 6
General compiling problem
« on: September 03, 2017, 07:21:21 PM »
After the VM with 1.3 GB from 2013 has the same problem and the other VM doesn´t start, I tried to build mine with Debian 9. I think I found all packages I need to install after the minimal installation. The compiler is gcc-arm-none-eabi-4_8-2013q4
Now my problems:
If I do a "make", all cameras will be compiled with the exeption of the 7D:

[ SYMBOLS  ]   magiclantern.sym
[ CP       ]   7D_203.sym
make[1]: Leaving directory '/home/ml/magic-lantern/platform/7D.203'
make -C  /home/ml/magic-lantern/platform/7D_MASTER.203
make[1]: Entering directory '/home/ml/magic-lantern/platform/7D_MASTER.203'
[ VERSION  ]   ../../platform/7D_MASTER.203/version.bin
[ LD       ]   magiclantern
../../src/Makefile.src:196: recipe for target 'magiclantern' failed
make[1]: Leaving directory '/home/ml/magic-lantern/platform/7D_MASTER.203'
Makefile:18: recipe for target '7D_MASTER' failed

After disabling the 7D all is fine, but this can not be the solution.

When I do a "make zip", at first "make docs" is executed. It seems, that there is only executed the first line:
cd $(DOC_DIR) && RST2LATEX=$(RST2LATEX) $(PYTHON) mkdoc.py

then I get an error:

../../Makefile.inc:49: recipe for target 'docs' failed
make[1]: Leaving directory '/home/ml/magic-lantern/platform/all'
Makefile:105: recipe for target 'docs' failed

If I execute both lines in the console, all works fine with no error:
   cd doc && python2 mkdoc.py
   cd doc && python2 mkdoc-cam.py

Where can I raise the debuglevel to find the errors? Can anyone give me a hint, where these errors came from?


a1ex

  • Administrator
  • Hero Member
  • *****
  • Posts: 10183
  • 5D Mark Free
Re: General compiling problem
« Reply #1 on: September 03, 2017, 07:49:25 PM »
It's not a problem with your system - that's the current state.

For 7D, we currently use only the slave processor; there is some experimental code for the master CPU, but requires some non-public signing tools.

We usually compile from the platform directory (e.g. platform/7D.203). You can check the build logs from the download page, for reference.

The docs system should be updated (both the text and the backend); back then, we only had a fixed-width font, so the help system used to display pre-rendered bitmaps; however, we've now got proportional fonts, so the help pages can now be stored as plain (or some sort of rich) text.

Some useful topics:
http://www.magiclantern.fm/forum/index.php?topic=11269
http://www.magiclantern.fm/forum/index.php?topic=3545
http://www.magiclantern.fm/forum/index.php?topic=7850
http://www.magiclantern.fm/forum/index.php?topic=8539.msg81214#msg81214

(basically, it only needs some manpower, and ideally a solution that doesn't require a lot of maintenance)