Re: [Openhpi-devel] Recompiling issue in the openhpid code

[Anton P. <av...@ng...>]

Hello Banani!

Not sure if the directory with build files can be safely relocated.
You can try out of source build if you need several build configurations.

I.e.:

mkdir /some/dir/build1
cd /some/dir/build1
/openhpi/src/dir/configure
make
make install

then mkdir /some/dir/build2... for another configuration

Another benefit is that you can remove build directory completely then.

Anton Pak

On Wed, 24 Dec 2014 16:30:13 +0300, Banani Ghosh  
<ban...@ar...> wrote:

> Hi,
>
> We are facing a problem in recompiling the OpenHPI code in the following  
> scenario:
>
>
> 1.       Copied the source code in a directory.
>
> 2.       Executed the command "./configure"
>
> 3.       Executed "make"
>
> 4.       Executed "make install"    [NOTE: Succesfully compiled and  
> binaries created]
>
> 5.       Copied the code into another directory
>
> 6.       Executed "make clean"
>
> 7.       Executed "make"
>
> And came across the following errors :
>
> mv -f .deps/sahpi_enum_utils.Tpo .deps/sahpi_enum_utils.Plo
> mv: cannot stat `.deps/sahpi_enum_utils.Tpo': No such file or directory
>
>
> Then also tried with executing ./configure in the new directory but the  
> issue did not resolve.
>
> NOTE: The code is getting compiled in the path in which it was first  
> configured and compiled.
>
> Kindly guide us to solve this issue as soon as possible.
>
>
> Regards
> Banani Ghosh
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended  
> solely for the use of the individual to whom it is addressed. It may  
> contain privileged or confidential information and should not be  
> circulated or used for any purpose other than for what it is intended.  
> If you have received this message in error, please notify the originator  
> immediately. If you are not the intended recipient, you are notified  
> that you are strictly prohibited from using, copying, altering, or  
> disclosing the contents of this message. Aricent accepts no  
> responsibility for loss or damage arising from the use of the  
> information transmitted by this email including damage from virus."