Hello Gautam,

Thank you very much for reporting those issues.
I am working on fixing them (at least some of them).
A fix for pthread_* functions is proposed in pull request
https://github.com/OpenSCAP/openscap/pull/337

Regarding your question, the header files are dependent on versions
of libraries in your system and should not be changed manually.
I think it would be very hard to backport the newer versions from newer systems.
The way for you is to fix the OpenSCAP code.

Best regards

Jan Černý
Security Technologies | Red Hat, Inc.

----- Original Message -----
> From: "S, Gautam" <[email protected]>
> To: [email protected]
> Sent: Friday, March 4, 2016 9:44:23 AM
> Subject: [Open-scap] Further compilation issues on SLES11.
> 
> 
> 
> Hello folks,
> 
> 
> 
> I have been following the mail chain “Compile issues on RHEL5+SLES11” and I
> see a few more issues further down the compile and install process.
> 
> 
> 
> 1) Added “linux/limits.h” to src/OVAL/oval_session.c as suggested by Andreas
> Krause.
> 
> 
> 
> 2) The missing pthread API “pthread_setname_np” is used in a few other places
> apart from debug.c. Modules in src/OVAL/probes/SEAP/seap.c,
> src/OVAL/probes/probe/icache.c, input_handler.c, signal_handler.c and
> worker.c also use this API.
> 
> 
> 
> 3) The module src/OVAL/probes/unix/linux/rpmverifypackage.c uses
> ARGV_const_t. There is no definition for this in any of the header files
> present in SLES 11 SP3. On RHEL6, I see a definition in argv.h:
> 
> 
> 
> $grep ARGV_const_t /usr/include/rpm/argv.h
> 
> typedef char * const *ARGV_const_t;
> 
> 
> 
> 4) The module src/OVAL/probes/unix/linux/rpmverifyfile uses symbols
> RPMVERIFY_FILEDIGEST, VERIFY_FILEDIGEST and VERIFY_CAPS which are not
> present SLES 11 SP3. On RHEL6, the definitions are provided by
> /usr/include/rpm/rpmvf.h. I updated the /usr/include/rpm/rpmcli.h file since
> it seemed to be the right place to add these definitions.
> 
> 
> 
> I am new to Linux and building on Linux. I apologize upfront is what I am
> asking is trivial. Is there a way from me to update my system’s
> “/usr/include…” directories with the expected versions of the code?
> 
> 
> 
> Thank you.
> 
> 
> 
> Regards,
> 
> Gautam.
> 
> _______________________________________________
> Open-scap-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/open-scap-list

_______________________________________________
Open-scap-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/open-scap-list

Reply via email to