Re: [expert] Can you believe it?

2001-07-31 Thread Paul Cox

On Friday, Jul 20, 2001, Craig Woods wrote:

 Still hacking away at rebuilding the bind 9 src file, I have added 
 openssl-devel, libxml, libxml-devel, numerous updates, and a parser named 
 byacc, and now I am closer than ever. This is what I now get at the end of a 
 very long compile session
 
 + cd /var/tmp/bind-root/usr/share/man
 + tar xjf /usr/src/RPM/SOURCES/bind-manpages.tar.bz2
 tar: invalid option -- j
 Try `tar --help' for more information.
 Bad exit status from /var/tmp/rpm-tmp.47472 (%install)  
 
 It is hard to believe but somehow, during the install phase of the rpm 
 --rebuild process, the process is issuing a tar command with an j option. 
 Hell, I have never seen a j switch, and neither has man tar. Is there 
 someway to alter this command? I think it might be the last piece in what has 
 been a veritable jigsaw puzzle..

It's been a long time since you wrote your original message, but here's
a reply anyway :)

The option -j is to uncompress bzip2 archives and then untar them.  It's
correct for the version of tar that comes with Mandrake 8.0.  However on
older versions, it's option -I, not -j.  Why it was changed, I don't
know.  Of course, this is assumming you're using the GNU version of tar.

-- 
Paul Cox paul at coxcentral dot com
Kernel: 2.4.3-20mdk-win4lin-pcox  -  Uptime: 19 days 19 hours 35 minutes.




[expert] Can you believe it?

2001-07-20 Thread Craig Woods


I can

Still hacking away at rebuilding the bind 9 src file, I have added 
openssl-devel, libxml, libxml-devel, numerous updates, and a parser named 
byacc, and now I am closer than ever. This is what I now get at the end of a 
very long compile session

+ cd /var/tmp/bind-root/usr/share/man
+ tar xjf /usr/src/RPM/SOURCES/bind-manpages.tar.bz2
tar: invalid option -- j
Try `tar --help' for more information.
Bad exit status from /var/tmp/rpm-tmp.47472 (%install)  

It is hard to believe but somehow, during the install phase of the rpm 
--rebuild process, the process is issuing a tar command with an j option. 
Hell, I have never seen a j switch, and neither has man tar. Is there 
someway to alter this command? I think it might be the last piece in what has 
been a veritable jigsaw puzzle..

Again thanks to all,
Craig Woods
UNIX SA




RE: [expert] Can you believe it?

2001-07-20 Thread Jose M. Sanchez


Hah! An undocumented update to TAR that was available on the
developers machine(s).

Look at the spec file in /usr/src/RPM/SPECS for the bind program.

You can change it there and then use rebuild by using the modified spec
file as well.

The RPM book explains it. I don't remember the command to do this.

You can update the source RPM with your modified spec.

-JMS

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Craig Woods
Sent: Friday, July 20, 2001 3:29 AM
To: [EMAIL PROTECTED]
Subject: [expert] Can you believe it?



I can

Still hacking away at rebuilding the bind 9 src file, I have added 
openssl-devel, libxml, libxml-devel, numerous updates, and a parser
named 
byacc, and now I am closer than ever. This is what I now get at the end
of a 
very long compile session

+ cd /var/tmp/bind-root/usr/share/man
+ tar xjf /usr/src/RPM/SOURCES/bind-manpages.tar.bz2
tar: invalid option -- j
Try `tar --help' for more information.
Bad exit status from /var/tmp/rpm-tmp.47472 (%install)  

It is hard to believe but somehow, during the install phase of the rpm 
--rebuild process, the process is issuing a tar command with an j
option. 
Hell, I have never seen a j switch, and neither has man tar. Is there 
someway to alter this command? I think it might be the last piece in
what has 
been a veritable jigsaw puzzle..

Again thanks to all,
Craig Woods
UNIX SA





RE: [expert] Can you believe it?

2001-07-20 Thread Jose M. Sanchez

One thing I forgot to mention before.

If you grab the tarball and use the ./configure script, it may learn how
to deal with the items missing from your computer and go ahead and
compile.

You should grab the i586.rpm file and see where it would have placed the
destination folders, then use the --target-dir= command for ./configure
to tell it where to put the installation tree.

This way later when you finally have a working RPM, you can install it
without loosing compatibility with your existing files.

-JMS


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Craig Woods
Sent: Friday, July 20, 2001 3:29 AM
To: [EMAIL PROTECTED]
Subject: [expert] Can you believe it?






Re: [expert] Can you believe it?

2001-07-20 Thread Julia A. Case

Quoting Craig Woods ([EMAIL PROTECTED]):
 + cd /var/tmp/bind-root/usr/share/man
 + tar xjf /usr/src/RPM/SOURCES/bind-manpages.tar.bz2
 tar: invalid option -- j
 Try `tar --help' for more information.
 Bad exit status from /var/tmp/rpm-tmp.47472 (%install)  
 
The j option is so that it can unzip the .bz2 file...  you might want to 
upgrade your tar install

Julia

-- 
[  Julia Anne Case  ] [Ships are safe inside the harbor,   ]
[Programmer at large] [  but is that what ships are really for.]
[   Admining Linux  ] [   To thine own self be true.   ]
[ Windows/WindowsNT ] [ Fair is where you take your cows to be judged. ]

 PGP signature