Hi Paul Thanks for your commits. I'm still not entirely clear on the cause of the FTBFS. Your patch to components/build.sh looks the same as the one I attached to this bug report earlier, but that on its own didn't work for me.
What do you think of modifying debian/patches/fix_build.sh_for_lazarus-1.2.patch as below: --- a/components/build.sh +++ b/components/build.sh @@ -10,7 +10,12 @@ then $lazbuild /usr/lib/lazarus/default/components/lazcontrols/lazcontrols.lpk $DC_ARCH -B $lazbuild /usr/lib/lazarus/default/components/synedit/synedit.lpk $DC_ARCH -B - $lazbuild /usr/lib/lazarus/default/ideintf/ideintf.lpk $DC_ARCH -B + if [ -d /usr/lib/lazarus/default/components/ideintf ] + then + $lazbuild /usr/lib/lazarus/default/components/ideintf/ideintf.lpk $DC_ARCH -B + else + $lazbuild /usr/lib/lazarus/default/ideintf/ideintf.lpk $DC_ARCH -B + fi fi # Build components This should make backporting easier and allow doublecmd to continue to build on lazarus >= 1.0.1, and we won't have to change the versions of the lazarus and lcl* build-depends in debian/control to >= 1.2~. That being said, right now I'm not able to build doublecmd with debian/add_set-e_to_build_scripts.patch and lazarus 1.0.10 (Ubuntu Trusty). I'll be able to test on lazarus 1.2 this coming week. Regards Graham -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
