[Open-scap] getting started with source

[Jan Ruzicka]

Vladimir

The open scap is using the rpm-devel for verifying versions of packages.
To work for Gentoo ... seems like quite a lot of work ahead.
All test need to be redefined according to your system ... 

Jan

On Oct 19, 2011, at 11:42 AM, Vladimir Giszpenc wrote:

> 1. I am using Gentoo.
> No version of rpm-devel is installed I imagine since Gentoo does not use
> rpm.  I figured that since I was installing from source, it would not be an
> issue.
> 
> 2. 
> # ldd `which oscap` | grep openscap
> /usr/bin/ldd: line 163: /lib/ld-linux.so.2: cannot execute binary file
>        libopenscap.so.1 => not found
> # ls -laF /usr/local/lib64/libopenscap.so.1
> lrwxrwxrwx 1 root root 20 Oct 19 11:05 /usr/local/lib64/libopenscap.so.1 ->
> libopenscap.so.1.0.0*
> 
> 
> Vladimir Giszpenc
> Armadillo Technical Lead
> DSCI Contractor Supporting
> U.S. Army CERDEC S&TCD CSIAD
> Tactical Network Protection Branch
> (732) 542-3113 x1328
> 
> 
>> -----Original Message-----
>> From: Peter Vrabec [mailto:pvrabec at redhat.com]
>> Sent: Wednesday, October 19, 2011 11:33 AM
>> To: open-scap-list at redhat.com
>> Cc: Vladimir Giszpenc
>> Subject: Re: [Open-scap] getting started with source
>> 
>> Hi Vladimir,
>> 
>> I can't reproduce any of you issues, so I have more questions than
> answers.
>> 
>> 1.
>> * What distribution do you use?
>> * What version of rpm-devel package is installed?
>> 
>> 2.
>> * $ ldd `which oscap`
>> * $ find / -name libopenscap.so.1
>> 
>> thnx.
>> Peter.
>> 
>> 
>> 
>> On Wednesday, October 19, 2011 03:44:59 PM Vladimir Giszpenc wrote:
>>> Hi all,
>>> 
>>> I got the oscap source using
>>> $git clone git://git.fedorahosted.org/git/openscap.git
>>> 
>>> Then, I ran
>>> $./autogen.sh
>>> 
>>> Then, I ran
>>> $./configure
>>> 
>>> Finally, I ran make.  Here is where it exited out.
>>> 
>>> unix/linux/rpmverify.c:333: error: âVERIFY_MD5â undeclared here (not
>>> in a
>>> function) unix/linux/rpmverify.c:333: warning: missing initializer
>>> unix/linux/rpmverify.c:333: warning: (near initialization for
>>> ârpmverify_bhmap[6].a_flagâ) make[3]: ***
>>> [probe_rpmverify-rpmverify.o] Error 1
>>> make[3]: Leaving directory
>> `/public/vlad/openscap/openscap/src/OVAL/probes'
>>> make[2]: *** [all-recursive] Error 1
>>> make[2]: Leaving directory
>> `/public/vlad/openscap/openscap/src/OVAL/probes'
>>> make[1]: *** [all-recursive] Error 1
>>> make[1]: Leaving directory `/public/vlad/openscap/openscap'
>>> make: *** [all] Error 2
>>> 
>>> 
>>> I sort of fixed this by prepending RPM in front of VERIFY_MD5, but I
>>> really don't know what I am doing so I don't want to submit any patch
>>> to that effect. Also, I am a proponent of reporting errors early.  I
>>> did not install swig at first and I think that configure should give
>>> an error since make gives an error when it is not installed.
>>> 
>>> I installed swig.  Reran configure.
>>> Make
>>> Make install (as root)
>>> 
>>> Now given
>>> oscap xccdf generate guide --profile allrules output/rhel6-xccdf.xml >
>>> output/rhel6-guide.html
>>> 
>>> I get
>>> 
>>> oscap: error while loading shared libraries: libopenscap.so.1: cannot
>>> open shared object file: No such file or directory
>>> 
>>> Can you offer any advice.
>>> 
>>> Thanks,
>>> 
>>> Vladimir Giszpenc
>>> Armadillo Technical Lead
>>> DSCI Contractor Supporting
>>> U.S. Army CERDEC S&TCD CSIAD
>>> Tactical Network Protection Branch
>>> (732) 542-3113 x1328
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Open-scap-list mailing list
>>> Open-scap-list at redhat.com
>>> https://www.redhat.com/mailman/listinfo/open-scap-list
> <smime.p7s><ATT00001..txt>

Jan Ruzicka
Senior Software Engineer
Comtech Mobile Datacom Corporation
20430 Century Blvd, Germantown, MD 20874
Office: 240-686-3300
Fax: 240-686-3301
 
The information contained in this message may be privileged and/or confidential. If you are not the intended recipient, or responsible for delivering this message to the intended recipient, any review, forwarding, dissemination, distribution or copying of this communication or any attachment(s) is strictly prohibited. If you have received this message in error, please so notify the sender immediately, and delete it and all attachments from your computer and network.