You can force install them using 
/Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.14.pkg

> On Jun 20, 2020, at 9:54 AM, Peter <[email protected]> wrote:
> 
> Jims Script does not work for me. And it sets a lot of stuff, which I am 
> unsure if they are the same on my System.
> 
> Apple is Awesome. They have switched the way they work with XCode in catalina 
> depending on what Version you use it works differently.
> 
> So header files are no long distributed in /usr/include or 
> /user/local/include.
> 
> you can figure the path with the command xcrun --show-sdk-path
> 
> Now thanks to Jims script I found the way to overwrite the defaults and I 
> have passed ther test.
> 
> Thanks for the pointer.
> 
> 
> 
> Am 20.06.20 um 14:31 schrieb Matthias Seidel:
> 
>> Am 20.06.20 um 14:25 schrieb Peter:
>>> the alloc statement coimes from the guide. 
>> So the guide may be wrong... If so, please update it.
>> But why don't you try the proven config from Jim? [1]
>> Later you can always modify...
>> 
>> Regards,
>> 
>>    Matthias
>> 
>> [1] 
>> https://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.2.0-Dev2/unxmacos/
>> 
>>> 
>>> I try some of the variations 
>>> 
>>> Am 20.06.20 um 14:19 schrieb Matthias Seidel: 
>>>> Hi, 
>>>> 
>>>> See comment inside. Maybe this solves it. 
>>>> 
>>>> Am 20.06.20 um 14:12 schrieb Peter Kovacs: 
>>>>> Right. Sorry. 
>>>>> 
>>>>> My switches: 
>>>>> 
>>>>> ./configure \ 
>>>>>      --with-dmake-path=${HOME}/dmake/bin/bin/dmake \ 
>>>>>       --with-epm=${HOME}/epm/bin/bin/epm \ 
>>>>>      --with-lang="${LANGS}" \ 
>>>>>      --with-jdk-home=${jdkhome} \ 
>>>>>      --with-package-format="installed" \ 
>>>>>      --with-vendor="Petko Testbuild"\ 
>>>>>      --with-build-version="aoo4ever-$(date +"%Y-%m-%d %H:%M") - `uname 
>>>>> -sm`\n ${GitHash}" \ 
>>>>>      --enable-crashdump=yes \ 
>>>>>      --enable-category-b \ 
>>>>>      --enable-beanshell \ 
>>>>>      --enable-wiki-publisher \ 
>>>>>      --enable-bundled-dictionaries \ 
>>>>>      --enable-opengl  \ 
>>>>>      --enable-dbus  \ 
>>>>>      --without-junit \ 
>>>>>      --without-stlport \ 
>>>>>      --disable-odk \ 
>>>>>      --without-fonts \ 
>>>>>      --disable-systray \ 
>>>>>      --with-alloc=internal \ 
>>>> --with-alloc            Define which allocator to build with 
>>>>                            (choices are oo, system, tcmalloc, jemalloc) 
>>>> 
>>>>                            Note that on FreeBSD/NetBSD system==jemalloc 
>>>>>      --enable-verbose \ 
>>>>>      --with-openldap \ 
>>>>> 
>>>>> Am 20.06.20 um 14:01 schrieb Matthias Seidel: 
>>>>>> Hi Peter, 
>>>>>> 
>>>>>> Am 20.06.20 um 13:56 schrieb Peter: 
>>>>>>> Hi, 
>>>>>>> 
>>>>>>> 
>>>>>>> When Running configure ion Mac OS X I get the error Message: 
>>>>>>> 
>>>>>>> checking whether we are cross compiling... configure: error: in 
>>>>>>> `workspace/AOO/gitbox/main': 
>>>>>>> configure: error: cannot run C compiled programs. 
>>>>>> If it is a "configure: error:" you should probably post your used 
>>>>>> configure switches... 
>>>>>> 
>>>>>> Otherwise we have to simply guess... ;-) 
>>>>>> 
>>>>>> Regards, 
>>>>>> 
>>>>>>     Matthias 
>>>>>> 
>>>>>>> 
>>>>>>> I have Xcode installed, and the commandline tools are also 
>>>>>>> installed. Any other Ideas how to solve this? 
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> --------------------------------------------------------------------- 
>>>>>>> To unsubscribe, e-mail:[email protected] 
>>>>>>> For additional commands, e-mail:[email protected] 
>>> 
>>> 
>>> 
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: 
>>> [email protected]
>>> 
>>> For additional commands, e-mail: 
>>> [email protected]
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to