@Oliver I did `source` every time I make a build, without `source`, there
will be compile error complaining that build command not found.


On Fri, Feb 21, 2014 at 4:10 PM, Oliver-Rainer Wittmann <
[email protected]> wrote:

> Hi,
>
>
> On 20.02.2014 14:39, LOH KOK HOE wrote:
>
>> During the build, there was an error happen in instsetoo_native module
>> where a function call determine_new_packagename causing the build stop. As
>> I trace back the bug, I have this
>> link<https://issues.apache.org/ooo/show_bug.cgi?id=121469> and
>>
>> they mention this was cause by the epm module. The module I have now is
>> version 4.2, and I must have the version 3.7. Thus I am require to issue
>> this command
>>
>> './configure
>> --with-epm-url=/home/xxx/workspace/aoo-trunk/main/epm-3.7-source.tar.gz`
>>
>> After that I issue the ./bootstrap command to update the build
>> configuration. After this command I see the following output:
>>
>> all external libraries present
>> epm-3.7.tar.gz exists
>>
>> When I continue my build using this command:
>>
>>
> Just a simple question:
> Your 'configure' created a new 'build environment script' (Linux[...].sh).
> Did you 'source' it before you start the next build?
>
> Note: I also recommend to run the 'configure' in a new shell as the
> configure script might be influenced by an existing 'AOO build environment'.
>
>
> Best regards, Oliver.
>
>
>  build --all:instsetoo_native
>>
>> The problem still exists. As I check in the <aoo_source_root>/main/epm, I
>> see there is a `epm-3.7.patch` file sitting there silently, I wasn't sure
>> whether this file will actually fix this problem or not, but in fact, it
>> doesn't. Thus I would like to know is there any alternate solution in
>> order
>> to rectified this problem?
>>
>> FYI, I made the build on Ubuntu 13.04, do I need to disable something
>> during the configuration before the build?
>>
>> THanks@!
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to