On 9/16/07, David Halik <dhalik@xxxxxxxxxxxxxxx> wrote:
Hello all,
Let me first say that archived list mail from all of you was extremely
helpful in enabling me to build rpm 4.4.9 for Solaris 9 sparc as we move
off of 4.1. Almost every issue I ran into had already been address by
Tim Mooney or Jeff Johnson at some point. Thank you very much!
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.
First of all, neon is _NOT_ used for ftp transport.
Second, adding --ftpdebug will display the FTP protocol on
the wire. There is also --rpmiodebug which will display args
to almost every rpmio operation if needed.
From 6+ year old memory, there are ftp server differences on solaris that
cause pain. Likely easy fixing if there is need.
73 de Jeff
For example:
$> rpm -Uvh
ftp://rpm.rutgers.edu/solaris /solaris9-sparc64/helium/RPMS.main/wget-1.10.2-3.solaris2.9-sparc64.rpm
Retrieving
ftp://rpm.rutgers.edu/solaris/solaris9-sparc64/helium/RPMS.main/wget-1.10.2-3.solaris2.9 -sparc64.rpm
error: 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
Since I'm sucking off our own server we know the files exist and can
download them any other way I try, so I began investigating and noticed
this after a quick truss of the process:
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
Hmm, that looks like it doesn't understand it's not a local file. So I
looked a little bit farther:
$> 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 didn't seem right either. Way too little in the way of http/ftp,
especially when you compare it against our rpm 4.1 binary that is
currently working. The build definitely thought it was making neon
support, and an ldd of rpm shows libneon.so.26 =>
/usr/local/lib/libneon.so.26, so it wants and finds it... yet it doesn't
look like it was actually built in. Maybe I'm going in the wrong
direction, but I'm stumped.
Any advice here? I'd greatly appreciate it.
Thank you,
-Dave
//////
--
============================== ===
David Halik
Systems Programmer
OSS/NBCS - OIT Rutgers University
dhalik@xxxxxxxxxxxxxxx
=================================
______________________________ _________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/rpm-list
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
