I ran into a problem recently when rebuilding opensc in an environment
where a version of the package was already installed (Fedora Core 6, gcc
4.1.1, with both opensc and opensc-devel installed).
The problem is that many of the opensc source files, but particularly
opensc.h, include files like this:
#include <opensc/scconf.h>
#include <opensc/errors.h>
#include <opensc/types.h>
Unfortunately, the <...> means to pick these files up from the globally
installed version of opensc, not the version I'm trying to build. This
caused a problem in my case because the value of SC_MAX_ACL_OPS has
changed since the FC6 packages were created.
I solved this problem in opensc.h by changing these #includes to:
#include "opensc/scconf.h"
#include "opensc/errors.h"
#include "opensc/types.h"
This means search for these files locally, falling back to <...> if the
local versions can't be located, which seems right for a development
environment.
Can anyone think of any disadvantage to making this change throughout
the opensc sources?
If not, I'm guessing I should put it into the ticket system?
-- Ian
_______________________________________________
opensc-devel mailing list
[email protected]
http://www.opensc-project.org/mailman/listinfo/opensc-devel
