In regard to: rpm 4.4.9 missing neon support in Solaris 9 - build issue?,...:
Now that I have it built there is an issue. After succesfully building 4.4.9
against neon 0.26.2 (it didn't seem to like 0.27, so I used a 0.26 I already
had) we've noticed that even though the build looked good, neon support (I
guess that's the issue) seems to be mysteriously missing when we actually go
to use it.
I just tested the fetch-and-install functionality, and I'm seeing the exact
same issue you're seeing, on x86_64-sun-solaris2.10.
My libneon was built statically so it won't show up via ldd, but if I
nm -p /local/lib/64/librpmio-4.4.so | egrep 'ne_'
there are lots of neon-related matches, so librpmio definitely has the
necessary neon functions.
Retrieving
ftp://rpm.rutgers.edu/solaris/solaris9-sparc64/helium/RPMS.main/wget-1.10.2-3.solaris2.9-sparc64.rpm
write(1, " R e t r i e v i n g f".., 112) = 112
getpid() = 2426 [2425]
sysconfig(_CONFIG_MAXPID) = 30000
lstat64("rpm-xfer.ubaqVe", 0xFFBFF880) Err#2 ENOENT
open64("ftp://rpm.rutgers.edu/solaris/solaris9-sparc64/helium/RPMS.main/wget-1.10.2-3.solaris2.9-sparc64.rpm";,
O_RDONLY) Err#2 ENOENT
fstat64(2, 0xFFBFF578) = 0
error: write(2, " e r r o r : ", 7) = 7
skipping
ftp://rpm.rutgers.edu/solaris/solaris9-sparc64/helium/RPMS.main/wget-1.10.2-3.solaris2.9-sparc64.rpm
- transfer failed - Unknown or unexpected error
I get pretty much the same truss output, but it's probably more useful to
do library-level tracing too, something like
truss -rall -wall -u a.out -u 'libneon::' -u 'librpm-4.4::' -u
'librpmio-4.4::' rpm -Uvh ftp://foo/bar/file.rpm
When I do that, I can see that urlGetFile() is being called, the urlPath()
call is returning 3, but Fopen is returning 0 and that basically ends our
fun.
$> strings -a /usr/local/bin/rpm | grep ftp
ftpStrerror
ftpStrerror
ftpFileDoneNeeded
ftpFileDoneNeeded
ftpFileDoneNeeded
ftpFileDoneNeeded
ftpFileDoneNeeded
ftpFileDoneNeeded
&ftpStrerror
$> strings -a /usr/local/bin/rpm | grep http
httpVersion
$>
That may not necessarily prove anything, as rpm might be invoking a
different program like $prefix/lib/rpm/rpmi.
In any case, I'm seeing the same issue as you. I don't know when I would
have much time to help track down what's going on, especially since
it's functionality I just don't use much.
Tim
--
Tim Mooney mooney@xxxxxxxxxxxxxxxxxxxxxxxxx
Information Technology Services (701) 231-1076 (Voice)
Room 242-J6, IACC Building (701) 231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
