To build from source RPM you will have to modify the SPEC file of the package or create your own SPEC file and make it relocateable I believe. For that there is a variable called "Prefix" that should be assigned some value. Ken Failbus ----- Original Message ----- From: "Robert P. J. Day" <rpjday@xxxxxxxxxxxxxx> To: <rpm-list@xxxxxxxxxx> Sent: Friday, December 12, 2003 12:29 PM Subject: Re: installing a PPC RPM in a local NFS-mounted root filesystem | | | -----Original Message----- | From: Ken Failbus <ken.failbus@xxxxxxxxxxx> | | > Robert, | | > This package might not be relocated to any other filesystem. Even though | > you try to install it in exported root filesystem looks like it's overriding | > that option and trying to install locally. | | well, dang, you're right, i just did an "rpm -qpi" on the file and it did say that | it was not relocatable. bummer. | | now, does this mean i can rebuild from the source rpm and *specify* that | i want a relocatable PPC binary rpm? i have the source rpm in front of | me, and i also have a PPC-target toolchain on this system. | | not clear from the man page, but how would i rebuild that source rpm | while being able to specify not only the target architecture, but also the | CROSS_COMPILE= tool prefix and that i want the end result to be | relocatable? | | am i pushing my luck? | | rday | | | | | _______________________________________________ | 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
