[LU-576] Incorrect build dependencies listed for libcfsutil.a

• Type: Bug
• Resolution: Low Priority
• Priority: Minor
• Fix Version/s: Lustre 2.1.0
• Affects Version/s: Lustre 2.0.0
• Labels: llnl
• Environment: Lustre 2.0.66
• Severity: 3
• Assignee: Minh Diep
• Reporter: Prakash Surya (Inactive)

Description

The dependencies listed for the libcfsutil.a target are incorrect. The sources for that library are listed in libcfs/libcfs/autoMakefile.am as:

libcfsutil_a_SOURCES = nidstrings.c util/parser.c util/parser.h util/platform.h \
                       util/l_ioctl.c util/util.c

Expanding out the above relative pathnames for the referenced [parser|platform].h files gives the following files:

libcfs/libcfs/util/parser.h
libcfs/libcfs/util/platform.h

The problem is these files do not exist. My assumption is, the dependencies it is intending to use are the following files:

libcfs/include/libcfs/util/parser.h
libcfs/include/libcfs/util/platform.h

Even worse, the [parser|platform].c files do not reference [parser|platform].h directly. These files are included through the directive:

#include <libcfs/libcfsutil.h>

But a dependency on libcfsutil.h is not in the *_SOURCES variable.

I think the right thing to do in this situation would be to fix these path issues using an "absolute" path to the needed files, using a reference to the top of the source tree. For example:

libcfsutil_a_SOURCES = $(top_srcdir)/libcfs/libcfs/util/nidstrings.c \
                       $(top_srcdir)/libcfs/libcfs/util/parser.c \
                       $(top_srcdir)/libcfs/libcfs/util/l_ioctl.c \
                       $(top_srcdir)/libcfs/libcfs/util/util.c \
                       $(top_srcdir)/libcfs/include/libcfs/util/parser.h \
                       $(top_srcdir)/libcfs/include/libcfs/util/platform.h \
                       $(top_srcdir)/libcfs/include/libcfs/libcfsutil.h

Although, full pathnames are not used throughout the build system for Lustre, thus the inconsistency of using full pathnames here is not ideal.

The patch submitted for LU-455, http://review.whamcloud.com/#change,1092, "fixes" this issue simply by removing the [parser|platform].h dependencies from the list of *_SOURCES.

Comments

[Andreas Dilger]

It isn't clear that this is still a problem for anyone.

[Christopher Morrone (Inactive)]

http://review.whamcloud.com/1092 was for LU-455, not this ticket. I can't remember this being fixed off the top of my head. I don't have time to do a more thorough search at the moment. My assumption is that is has not been addressed until proven otherwise.

[John Fuchs-Chesney (Inactive)]

Chris, Prakash,
Can I mark this as resolved?
Thanks,
~ jfc.

[Andreas Dilger]

The patch http://review.whamcloud.com/1092 was landed in 2011-08-12 for v2_0_66_0-40-g88ae427. Is there anything left to fix, or should this be closed?

[Minh Diep]

Chris, Prakash

Could you let me know what else need to be done for this ticket?

Thanks

[Peter Jones]

Minh is working on this area nowadays

[Christopher Morrone (Inactive)]

Mostly I want to be clear that we think this is likely a common problem in the build system. I don't think there is a point to fixing just these two. If we fix it, we should figure out the correct solution and apply it everywhere that it is needed.

I see no hurry to fix this either. I think that making some of the bigger changes like moving ldiskfs and the lustre kernel patches out of the lustre tree would be excellent first steps to cleaning up the build system. Once those are done, it will be easier to start some of the finer cleanup like this.

I would not suggest using the full path when the files are in the same directory as the makefile, or in subdirectories below the make file. I would perhaps only use the $(top_builddir) form of the path when we need to walk back up the tree. I am not really particularly opposed to using "..", though.

[Peter Jones]

chris,

Adding you for your comments

Thanks

Peter

[Prakash Surya (Inactive)]

My issue with using the full paths is that doesn't look to be the way things are done anywhere else in the build system. Even though I think it's the right fix, without going through and making the change everywhere, it still feels like an ugly hack. I'm sure I could look through the tree to answer this, but do you know how this sort of issue is handled in the other subsystems? I imagine having a separate 'include' directory is a common idiom.

And I haven't tried using '..' but technically I think it would work just fine. That solution just doesn't sit well with me.. Is there a good argument for '..' over full paths?

Isn't the benefit of using relative paths the fact that you can move the top level directories around and things will still work? If '..' is used then you lock yourself into the current directory structure without explicitly spelling out the structure you expect by using the full paths.

I know Chris Morrone also wasn't too keen using '..' to find the header files as well, although I'm not sure what his reasoning on that was. Perhaps it would be a good idea to add him to the watch list and see what he says about this matter.

[Brian Murrell (Inactive)]

I don't particularly have an issue with selective use of the full path, however couldn't a relative path also be used?

i.e.

libcfsutil_a_SOURCES = nidstrings.c util/parser.c ../include/libcfs/util/parser.h ../include/libcfs/util/platform.h \
                       util/l_ioctl.c util/util.c