On 30 Sep, Dr. Michael Stehmann wrote:
> Hello Don,
>
> in configure.sh I had this line :
>
> --with-build-version="aoo42x-$(date +"%Y-%m-%d %H:%M") - `uname -sm`\n
> ${GitHash}"
>
> Because I want to have the corresponding git hash I built, I need the
> output in two lines.
Instead of \n, try \\\\n. That forces the environment variable to
contain a literal \n, which should get passed as a compiler preprocessor
symbol definition, and the compiler will turn the \n into a newline. I
don't know how that interacts with the About dialog, though.
This is one more level of escaping than I think should be necessary, but
\\n didn't seem to help.
> Thanks for your help
>
> Kind regards
>
> Mechtilde
>
> Am 30.09.20 um 08:38 schrieb Don Lewis:
>> On 30 Sep, Mechtilde wrote:
>>> Hello,
>>>
>>> I set up a recent build environment with Debian 9.
>>>
>>> I have got the same error message again:
>>>
>>> ~/openoffice/main/instsetoo_native$ build --from cui
>>> build -- version: -
>>>
>>>
>>> =============
>>> Building module cui
>>> =============
>>>
>>> Entering /home/mechtilde/openoffice/main/cui/prj
>>>
>>> cd .. && make -s -r -j1 && make -s -r deliverlog
>>> /home/mechtilde/openoffice/main/cui/Library_cui.mk:37: *** missing
>>> separator. Stop.
>>> dmake: Error code 2, while making 'all'
>>>
>>> 1 module(s):
>>> cui
>>> need(s) to be rebuilt
>>>
>>> Reason(s):
>>>
>>> ERROR: error 65280 occurred while making
>>> /home/mechtilde/openoffice/main/cui/prj
>>>
>>> When you have fixed the errors in that module you can resume the build
>>> by running:
>>>
>>> I also attach my file LinuxX86-64Env.Set.sh.
>>>
>>> Can someone help me to get a proper build environment.
>>>
>>> Kind regards
>>>
>>> Mechtilde
>>>
>>> Am 10.11.19 um 22:02 schrieb Ariel Constenla-Haile:
>>>> Hi Mechtilde,
>>>>
>>>> On Sun, Nov 10, 2019 at 5:23 AM Mechtilde <[email protected]> wrote:
>>>>>
>>>>> Hello again,
>>>>>
>>>>> I did a recent git pull AOO42X and try to build it under Debian 9.
>>>>>
>>>>> It didn't build. it fails with error in main/cui/Library_cui.mk:37
>>>>>
>>>>> If I patched it as before then it builds succesfully.
>>>>>
>>>>> Either we need a switch for Debian 9 and may be newer
>>>>> distribution/versions or we need another fix.
>>>>
>>>> The contents of BUILD_VER_STRING might be the problem, attach your
>>>> LinuxX86-64Env.Set.sh and someone may reproduce the error.
>>
>> I'm building on Debian 9 and not having any problems. I just did a
>> trunk build and in my LinuxX86-64Env.Set.sh I see:
>>
>> $ grep BUILD_VER_STRING LinuxX86-64Env.Set.sh | head -1
>> BUILD_VER_STRING="2020-09-29 22:09:35 (Tue, 29 Sep 2020) - Linux x86_64"
>>
>> If I look at your LinuxX86-64Env.Set.sh:
>>
>> %grep BUILD_VER_STRING /tmp/LinuxX86-64Env.Set.sh | head -1
>> BUILD_VER_STRING="aoo42x-2020-09-29 19:11 - Linux x86_64
>>
>> I see a critical difference. Mine has " characters around the value,
>> but yours has the leading quote, but no trailing quote. Looking more
>> closely at the file:
>>
>> BUILD_VER_STRING="aoo42x-2020-09-29 19:11 - Linux x86_64
>> "
>>
>> It looks like a newline is getting embeded into the value somehow. The
>> rest of the info in the string has other differences as well.
>>
>> If I check out AOO42X and run autoconf and configure, I see:
>> BUILD_VER_STRING="2020-09-29 23:34:46 (Tue, 29 Sep 2020) - Linux x86_64"
>>
>> Ah, I'm running configure with this option:
>> --with-build-version="$(date +"%Y-%m-%d %H:%M:%S (%a, %d %b
>> %Y)") - `uname -sm`${AOO_BUILD_VERSION}"
>> What are you doing here?
>>
>>
>> ---------------------------------------------------------------------
>> 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]
