Freebsd 10 use clang by default about ossec-hids

[cgzones]

Why is ossec trying to set a compiler variable in the first place (https://github.com/ossec/ossec-hids/blob/master/install.sh#L814)? Should we not trust the operating system to give us a appropriate ${CC} environment variable?
I once succeed to compile ossec with clang, look at https://bitbucket.org/cgzones/ossec-hids/commits/1aa1d8b786d0ab730458626754b4666e4b7eb19d

[jrossi]

FreeBSD 10 only has clang. Gcc is not installed and must be added as pkg/port.

Clang can build everything in ossec correctly other then sha1 https://github.com/ossec/ossec-hids/tree/master/src/os_crypto/sha1 this bit of code uses inline asm that is not supported by clang. You can still build the .o with gcc and link it with clang which is what happens when you run "make clang".

What we need to do is fix that inline asm or require gcc. I think we should fix the inline asm myself.

Sent from my iPhone

On Mar 2, 2014, at 5:48 AM, "cgzones" [email protected] wrote:

Why is ossec trying to set a compiler variable in the first place (https://github.com/ossec/ossec-hids/blob/master/install.sh#L814)? Should we not trust the operating system to give us a appropriate ${CC} environment variable?
I once succeed to compile ossec with clang, look at https://bitbucket.org/cgzones/ossec-hids/commits/1aa1d8b786d0ab730458626754b4666e4b7eb19d

—
Reply to this email directly or view it on GitHub.

[cgzones]

can you test my branch https://github.com/cgzones/ossec-hids/tree/clang?

[jrossi]

@cgzones in quick testing it fixed this issue for freebsd. We are gonna need larger testing to make this work. Could you create a pull request for this?

[jrossi]

Thanks #132 this works and compiles on freebsd without issue.

Thank you @cgzones