globus-core: strange header install location

[petrrr]

I am using Macports to install the globus toolkit. As most of the ports are not yet committed here, I use the version from ​https://github.com/dvandok/globus-macports. However, the issue I am reporting here relates to my understanding to the already committed port globus-core.

This port installs the header file into /opt/local/lib/globus/include. Am I wrong, if I would think it should be simply /opt/local/include?

Note: The other ports install header files into the correct location. So this seems an exception.

radegast:include petr$ pwd
/opt/local/lib/globus/include
radegast:include petr$ ls -la
total 16
drwxr-xr-x  3 root  admin   102 Jun 21 21:25 .
drwxr-xr-x  3 root  admin   102 Jun 21 21:25 ..
-rw-r--r--  1 root  admin  5609 Jun 14 14:28 globus_config.h
radegast:include petr$ port provides globus_config.h 
/opt/local/lib/globus/include/globus_config.h is provided by: globus-core
radegast:include petr$ port installed globus-core
The following ports are currently installed:
  globus-core @8.9_0 (active)
radegast:include petr$ port installed globus-core
The following ports are currently installed:
  globus-core @8.9_0 (active)

I would assume this issue is related to this entry in the configure.post_args:

[...]
                        --with-flavorincludedir='\${libdir}/globus/include' \
[...]

Any good reason for this?

[cooljeanius (Eric Gallager)]

I'm guessing it's probably because there are some headers that would either mask or conflict with other headers if they were put in the default include directory... idk for sure though.

[petrrr]

Replying to egall@…:

I'm guessing it's probably because there are some headers that would either mask or conflict with other headers if they were put in the default include directory... idk for sure though.

Sorry, I was not precise enough in my last post.

The other (future) ports for the Globus suite install into /opt/local/include/globus not in the generic /opt/local/include which seems perfectly fine. None of the ports from the suite seems to install this same header file and I would be surprised if any port not from the suite would do so. So I do not see any conflict.

Actually, I use these ports as a dependency to compile software with GSI support, when I point to the /opt/local/include/globus directory, I am missing exactly that file.

[dennisvd@…]

The file globus_config.h is generated by configure and contains all kinds of system- and architecture-dependent value such as sizes of types. It contains no public interface definitions or function prototypes. I believe it is commonplace to put architecture specific files under ${prefix}/lib.

About the future ports I can not make any claim at the moment; I'm seeing that myproxy also installs headers in that location but that may be in error. I will have to look into it.

For now I'm holding the claim that the installation directory for globus_config.h is actually ok until proven wrong.

[petrrr]

I see the your point. Probably you are correct, so I am fine if you close this ticket.

If I get you right, the globus_config.h shouldn't be included at all to access the APIs? I will recheck this, and would eventually contact you directly (if you don't mind).

[dennisvd@…]

Peter,

no problem, and thanks for trying out!