sdk 10.9 lacks Python. No idea why. Install sdk 10.11 and configure should find and use that one.
All this is fixed in trunk. > On Oct 26, 2017, at 7:29 PM, Dave Fisher <dave2w...@comcast.net> wrote: > > Hi - > > Well this is a royal pain to setup. > > I’ve done the xcodelegacy and have installed the 10.7 and 10.9 SDKs. > > I have a fresh copy of the branch AOO414. I run and now it cannot find python > headers. > > checking which python to use... compiling against system python > (/usr/bin/python) > compiling against system python (version 2.7) > checking Python.h usability... no > checking Python.h presence... no > checking for Python.h... no > configure: error: Python headers not found > > I need help. What the heck happened to my Python setup? > > Thanks, > Dave > >> On Oct 26, 2017, at 1:00 PM, Dave Fisher <dave2w...@comcast.net >> <mailto:dave2w...@comcast.net>> wrote: >> >> Hi Jim, >> >> I’m building AOO 4.1.4 using macOS12 library and made it all the way to VCL >> where I get: >> >> /Users/davewave/Development/aoo-4.1.4/main/vcl/aqua/source/dtrans/PictToBmpFlt.cxx:34:10: >> fatal error: 'QuickTime/QuickTime.h' file not found >> #include <QuickTime/QuickTime.h> >> >> Do I need to use XCodeLegacy and point to 10.7? >> >> Regards, >> Dave >> >>> On Oct 25, 2017, at 12:24 PM, Dave Fisher <dave2w...@comcast.net >>> <mailto:dave2w...@comcast.net>> wrote: >>> >>> Hi - >>> >>> I am now on Xcode 8.3.3. Cleaned up and reset. >>> >>> I now I’m on an issues with Redland: >>> >>> configure: error: Raptor is too old - see http://librdf.org/raptor/ >>> <http://librdf.org/raptor/> to get a 2.0.7 or newer >>> dmake: Error code 1, while making >>> '../unxmaccx.pro/misc/build/so_configured_so_rasqal' >>> >>> 1 module(s): >>> redland >>> need(s) to be rebuilt >>> >>> Reason(s): >>> >>> ERROR: error 65280 occurred while making >>> /Users/davewave/Development/aoo/main/redland/rasqal >>> >>> When you have fixed the errors in that module you can resume the build by >>> running: >>> >>> build --all:redland >>> >>> Looking into this it looks bogus and I went past the check and now: >>> >>> configure: error: Rasqal is not installed or too old - see >>> http://librdf.org/rasqal/ <http://librdf.org/rasqal/> to get a version in >>> range 0.9.25 to 0.9.99 >>> dmake: Error code 1, while making >>> '../unxmaccx.pro/misc/build/so_configured_so_redland' >>> >>> 1 module(s): >>> redland >>> need(s) to be rebuilt >>> >>> Reason(s): >>> >>> ERROR: error 65280 occurred while making >>> /Users/davewave/Development/aoo/main/redland/redland >>> >>> When you have fixed the errors in that module you can resume the build by >>> running: >>> >>> build --all:redland >>> >>> Looks like I have something off in my environment. >>> >>> Regards, >>> Dave >>> >>> >>>> On Oct 25, 2017, at 8:19 AM, Dave Fisher <dave2w...@comcast.net >>>> <mailto:dave2w...@comcast.net>> wrote: >>>> >>>> Hi Jim, >>>> >>>> Thanks. I have Xcode 9 which has the following: >>>> >>>> $ xcodebuild -showsdks >>>> iOS SDKs: >>>> iOS 11.0 -sdk iphoneos11.0 >>>> >>>> iOS Simulator SDKs: >>>> Simulator - iOS 11.0 -sdk iphonesimulator11.0 >>>> >>>> macOS SDKs: >>>> macOS 10.13 -sdk macosx10.13 >>>> >>>> tvOS SDKs: >>>> tvOS 11.0 -sdk appletvos11.0 >>>> >>>> tvOS Simulator SDKs: >>>> Simulator - tvOS 11.0 -sdk appletvsimulator11.0 >>>> >>>> watchOS SDKs: >>>> watchOS 4.0 -sdk watchos4.0 >>>> >>>> watchOS Simulator SDKs: >>>> Simulator - watchOS 4.0 -sdk watchsimulator4.0 >>>> >>>> I modified configure to target 10.13 and adjusted the egrep: >>>> >>>> sdk_found=`xcodebuild -showsdks | $EGREP "sdk macosx10.(10|11|12|13)" | >>>> sed -e "s/.*sdk //" | head -n1` >>>> >>>> Also - >>>> # sdk_target=10.9 >>>> >>>> >>>> sdk_target=10.13 >>>> >>>> The last means the environment variable MACOSX_DEPLOYMENT_TARGET in the >>>> release script is not used. >>>> >>>> On to the next issue with the category B downloads. Certificate store >>>> issues giving 500 errors. >>>> >>>> Also, I noticed a version 5.5 of Tomcat …. >>>> >>>> Regards, >>>> Dave >>>> >>>>> On Oct 25, 2017, at 5:32 AM, Jim Jagielski <j...@jagunet.com >>>>> <mailto:j...@jagunet.com>> wrote: >>>>> >>>>> Actually, if you have Xcode7 or Xcode8, there is no need for >>>>> Xcodelegacy at all. >>>>> >>>>> All Xcodelegacy does is obtain older macOS SDKs and installs them >>>>> in Xcode. But we use the latest SDK available (via configure). So >>>>> Xcodelegacy is not a requirement/dependency per se. It's just >>>>> useful in case we get into a situation where we need to >>>>> use an older SDK rather than the latest. >>>>> >>>>>> On Oct 24, 2017, at 6:00 PM, Dave Fisher <dave2w...@comcast.net >>>>>> <mailto:dave2w...@comcast.net>> wrote: >>>>>> >>>>>> Hi Jim, >>>>>> >>>>>> I’m hung up on what I should do with >>>>>> https://github.com/devernay/xcodelegacy >>>>>> <https://github.com/devernay/xcodelegacy> >>>>>> <https://github.com/devernay/xcodelegacy >>>>>> <https://github.com/devernay/xcodelegacy>> >>>>>> >>>>>> What should I download before I run the scripts? Which form of the >>>>>> command should I use? >>>>>> >>>>>> BTW - this requirement is only mentioned in the build release script. >>>>>> >>>>>> Regards, >>>>>> Dave >>>>>> >>>>>>> On Oct 23, 2017, at 5:38 PM, Dave Fisher <dave2w...@comcast.net >>>>>>> <mailto:dave2w...@comcast.net> <mailto:dave2w...@comcast.net >>>>>>> <mailto:dave2w...@comcast.net>>> wrote: >>>>>>> >>>>>>> Hi Jim, >>>>>>> >>>>>>> I wanted to validate build instructions. Should I take these two from >>>>>>> your github for my MacOS Sierra environment? >>>>>>> >>>>>>> Regards, >>>>>>> Dave >>>>>>> >>>>>>> Sent from my iPhone >>>>>>> >>>>>>>> On Oct 20, 2017, at 7:31 AM, Jim Jagielski <j...@jagunet.com >>>>>>>> <mailto:j...@jagunet.com> <mailto:j...@jagunet.com >>>>>>>> <mailto:j...@jagunet.com>>> wrote: >>>>>>>> >>>>>>>> Just a FYI that I am tracking dmake and epm on the >>>>>>>> below Github pages: >>>>>>>> >>>>>>>> o https://github.com/jimjag/epm <https://github.com/jimjag/epm> >>>>>>>> <https://github.com/jimjag/epm <https://github.com/jimjag/epm>> >>>>>>>> o https://github.com/jimjag/dmake <https://github.com/jimjag/dmake> >>>>>>>> <https://github.com/jimjag/dmake <https://github.com/jimjag/dmake>> >>>>>>>> >>>>>>>> I know we are moving away from dmake, but IMO it'll take >>>>>>>> some time for that to be complete. Plus, updating to the >>>>>>>> latest version of EPM is useful (it's the ONLY way to build >>>>>>>> the macOS versions now, for example), but we also need >>>>>>>> the AOO-specific patches in there. Which are included >>>>>>>> in my forks. >>>>>>>> >>>>>>>> Just topic for discussion and chewing over >>>>>>>> >>>>>>>> --------------------------------------------------------------------- >>>>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>>>>>> <mailto:dev-unsubscr...@openoffice.apache.org> >>>>>>>> <mailto:dev-unsubscr...@openoffice.apache.org >>>>>>>> <mailto:dev-unsubscr...@openoffice.apache.org>> >>>>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>>>>>> <mailto:dev-h...@openoffice.apache.org> >>>>>>>> <mailto:dev-h...@openoffice.apache.org >>>>>>>> <mailto:dev-h...@openoffice.apache.org>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org >>>>>>> <mailto:dev-unsubscr...@openoffice.apache.org> >>>>>>> <mailto:dev-unsubscr...@openoffice.apache.org >>>>>>> <mailto:dev-unsubscr...@openoffice.apache.org>> >>>>>>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>>>>>> <mailto:dev-h...@openoffice.apache.org> >>>>>>> <mailto:dev-h...@openoffice.apache.org >>>>>>> <mailto:dev-h...@openoffice.apache.org>> >>>>>>> >>>>>> >>>>> >>>> >>> >> >
