> | I meant something like /usr/include/openmpi/
>
> You lost me. Please make up your mind as to whether you think it is a problem
> because we do or do not use /usr/include, or /usr/include/openmpi ?
>
> We use /usr/include/openmpi now, and we think that's the right way:

I agree that is the right way, but you don't use /usr/include/openmpi,
but /usr/lib/openmpi/include, as you have just shown:

>
> [EMAIL PROTECTED]:~$ dpkg -L libopenmpi-dev | grep mpi.h
> /usr/lib/openmpi/include/mpi.h
> /usr/lib/openmpi/include/openmpi/ompi/mpi/f77/prototypes_mpi.h
> [EMAIL PROTECTED]:~$ dpkg -l libopenmpi-dev
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: 
> uppercase=bad)
> ||/ Name                                   Version                            
>     Description
> +++-======================================-======================================-============================================================================================
> ii  libopenmpi-dev                         1.2.4-5                            
>     high performance message passing library -- header files
> [EMAIL PROTECTED]:~$
>
> No bug here, and if you could excuse me now, I got real work to do.

I am sorry for taking your time. And I appreciate your work on
openmpi. Unfortunately I still don't understand how it works. I admit
it can be my fault.

Let me repeat my question:

Why does openmpi use /usr/lib instead of /usr/include? Other libraries
use /usr/include, like petsc (/usr/include/petsc), libmesh
(/usr/include/libmesh), gtk
(/usr/include/gtk-2.0) etc. etc. Usually, as I understand it, they
also use /usr/lib/something/include, but they always link from
/usr/include.

Also, I, as a user, was used to using /usr/include (/something) for
everything, that's why I thought it'd the de facto standard, isn't it?
And if not,
is there some policy for that? I only found links I posted above,
suggesting to use /usr/include.

Thanks a lot,
Ondrej



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to