Skip to content
This repository has been archived by the owner on Feb 28, 2024. It is now read-only.

tacc not found #89

Closed
lucevers opened this issue Mar 19, 2017 · 11 comments
Closed

tacc not found #89

lucevers opened this issue Mar 19, 2017 · 11 comments

Comments

@lucevers
Copy link

Seems that tacc is not compiled.
Could not found the program after installing pam_tacplus.

@pprindeville
Copy link
Collaborator

Can you attach the output of your make? Not giving a lot of useful information to go by here.

@rx13
Copy link

rx13 commented Mar 30, 2017

The issue is not announced in the make process, but it is if you attempt to compile the tacc.c manually:

# gcc tacc.c -o tacc
tacc.c:30:26: fatal error: openssl/rand.h: No such file or directory
 #include <openssl/rand.h>
                          ^
compilation terminated.

This issue can be fixed by either installing libssl-dev in Debian or openssl-devel in RHEL base.

@pprindeville
Copy link
Collaborator

pprindeville commented Mar 30, 2017

This issue can be fixed by either installing libssl-dev in Debian or openssl-devel in RHEL base.

Of course the package containing the headers needs to be present to compile. Also, when you compile manually you're not passing in all the flags that a make-based compile would, so of course it's not going to work properly.

Neither of these is really a bug. That's normal usage.

If you look here:

https://github.com/jeroennijhof/pam_tacplus/blob/master/configure.ac#L39
https://github.com/jeroennijhof/pam_tacplus/blob/master/configure.ac#L54

you'll see that TACC only gets defined if a library (called libcrypto.a or libcrypto.so) containing the function RAND_pseudo_bytes is found. And you'll see here:

https://github.com/jeroennijhof/pam_tacplus/blob/master/Makefile.am#L13

that tacc only gets built if TACC was defined above (i.e. a libcrypto.a containing RAND_pseudo_bytes) was found.

If those conditions aren't met, then only the minimal components which can be built are built.

@rx13
Copy link

rx13 commented Mar 30, 2017

when you compile manually you're not passing in all the flags that a make-based compile would

Correct, I should've included the extended piece instead of the short one where I was replicating the make flags.

@pprindeville
Copy link
Collaborator

That's not really the point. If you want to (re-)compile tacc, then you do so as:

make tacc

@rx13
Copy link

rx13 commented Mar 30, 2017

Worth noting, in Debian 8.7* (kernel 4.7.5), you also need to replace -Werror with -Wno-deprecated to compile successfully with all dependencies. tacc is working for me at this time. Thanks. (adjusted per follow-up comment -- need more coffee)

@pprindeville
Copy link
Collaborator

I don't think you need to replace -Werror so much as supplement it as -Werror -Wno-error=deprecated. Can you post the errors that you're seeing when you build? And why are you using such an old version of Debian? I don't think anyone expects a current project to build under such an old release. Etch is now 10 years old.

@rx13
Copy link

rx13 commented Mar 30, 2017

In short, make was running with no issue (reported), but it was never spitting out the tacc client.
So I replicated as many of the flags from make as I could, and realized it was missing libssl.
Once that was fixed, it was failing to compile due to deprecation errors.
That's when I pulled -Werror (in place of the more sensible -Wno-error=deprecated)

So, had I not needed tacc, it likely would have never been noticed.

@pprindeville
Copy link
Collaborator

Once that was fixed, it was failing to compile due to deprecation errors.

Without seeing the previously requested errors, I can't tell if that's definitively true or not, but I strongly suspect that the errors have to do with your using a very old version of Debian (and hence a very old version of OpenSSL, probably pre 1.0.0).

@pprindeville
Copy link
Collaborator

Can you post your compilation messages from an unmodified cloning?

@pprindeville
Copy link
Collaborator

Can't fix it without more information so closing the issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants