| 1 |
I really appreciate the help. |
| 2 |
|
| 3 |
I am looking at several 32 bit binary packages that are only downloadable as |
| 4 |
32 bit rpms or debs. For example: fledermaus and a related 3D viewer for |
| 5 |
bathymetry files, and two different video editors. They are not available as |
| 6 |
source, and they certainly are not available as ebuilds, or prepackaged in |
| 7 |
any way. |
| 8 |
|
| 9 |
So, I can copy the binaries etc by hand into the chroot environment? Or |
| 10 |
perhaps even unpack using "rpm" or apt? WOuld I need to produce an ebuild of |
| 11 |
some kind? (Something akin to climbing Mt. Everest, I guess). |
| 12 |
|
| 13 |
Thanks again, |
| 14 |
|
| 15 |
Alan |
| 16 |
|
| 17 |
On 11/14/05, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 18 |
> |
| 19 |
> On Mon, 14 Nov 2005 11:21:00 +1000, Alan E. Davis wrote: |
| 20 |
> |
| 21 |
> > I think this is a step in the right direction. However, does this apply |
| 22 |
> > to 32 bit binaries one might wish to install from an RPM, for example, |
| 23 |
> > or a DEB file, from a 32 bit dist? |
| 24 |
> |
| 25 |
> Normally you just install those as normal. 32 bit binaries usually run |
| 26 |
> on AMD64 without modification. For example, I have openoffice-bin, |
| 27 |
> firefox-bin and vmware-workstation, all 32 bit packages, running on this |
| 28 |
> amd64 box. |
| 29 |
> |
| 30 |
> The chroot is only needed if you want to build 32 bit binaries. |
| 31 |
> |
| 32 |
> |
| 33 |
> -- |
| 34 |
> Neil Bothwick |
| 35 |
> |
| 36 |
> Why is there an expiration date on sour cream? |
| 37 |
> |
| 38 |
> |
| 39 |
> |
Archives