compiling rpm gives error poptQV.c 226

R03L · 04-17-2009, 05:24 AM

afther compiling all the packages for redhat's rpm i get this error running MAKE

Code:

C -DPIC -o .libs/poptQV.o
poptQV.c: In function 'queryArgCallback':
poptQV.c:226: error: 'POPT_READFILE_TRIMNEWLINES' undeclared (first use in this function)
poptQV.c:226: error: (Each undeclared identifier is reported only once
poptQV.c:226: error: for each function it appears in.)
make[3]: *** [poptQV.lo] Error 1
make[3]: Leaving directory `/home/admin/packages/rpm-5.1.8/lib'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/admin/packages/rpm-5.1.8/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/admin/packages/rpm-5.1.8'
make: *** [all] Error 2

can anybody help me please or explain this error?

or where do i find a packages containging poptQV?

already thnks

weibullguy · 04-17-2009, 07:15 AM

The package containing poptQV is RPM. But, that's not the error. This is the error message

Code:

error: 'POPT_READFILE_TRIMNEWLINES' undeclared (first use in this function)

However, you don't provide enough output to determine which header RPM is looking for POPT_READFILE_TRIMNEWLINES. I could presume it is looking in popt.h, but my popt.h doesn't define this variable. So maybe RPM is looking for this variable in an internal header or your version of popt is too old/new.

Edit: OK, I was bored enough to troubleshoot this a little. POPT_READFILE_TRIMNEWLINES is defined in popt version 1.15 or greater. Try updating your popt and see if that works. It did on my machine.

R03L · 04-17-2009, 08:34 AM

ok i dit install an older version of rpm and its compiling fine now.
rpm version 5.1.6

but now im getting this message from rpm.

Code:

#:RPM
rpm: error while loading shared libraries: librpmbuild-5.0.so: cannot open shared object file: No such file or directory

so were do i find librpmbuild or rpmlibs tar.gz tarball?

weibullguy · 04-17-2009, 12:12 PM

librpmbuild is provided by the rpm package. It should be installed in /usr/lib, /usr/local/lib, /usr/lib64, /usr/local/lib64, etc. depending on the prefix you used and the ABI you built. If it's not there, something went wrong with your install. If it is, you shouldn't have to, but you can try to execute ldconfig as root.

R03L · 04-18-2009, 05:15 AM

ok it's working now,, thank you