Ian Young wrote:
> From what you're saying, maybe the -I../../src/include option (either of
> them!) ought to be making the right thing happen, as that directory does
> include an opensc directory containing (soft links to) the appropriate
> files. Apparently not, though, and I don't know how to
Ville Skyttä wrote:
> Wouldn't that be the rough equivalent of adding "." to $PATH and/or
> $LD_LIBRARY_PATH, ie. what stuff gets actually used would depend on in which
> dir a command pulling it in would be run? Doesn't sound too good to me when
> thinking about these same headers being insta
On Monday 19 February 2007, Ian Young wrote:
> The problem is that many of the opensc source files, but particularly
> opensc.h, include files like this:
>
> #include
> #include
> #include
>
> Unfortunately, the <...> means to pick these files up from the globally
> installed
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 th
