List Archive: gentoo-amd64
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
Mark Knecht wrote:
> I'm apparently not able to get the path edit quite right. It's
> asking about /home/32-bit. Please double check me if possible:
> 1) Everything, including the patch file, is copied to
(Pardon my butting in, Billy; I thought my experience might help Mark.)
You need to set up this structure:
# ls -l /usr/local/portage/sys-apps/l32/
drwxr-xr-x 2 root root 4096 Dec 9 10:18 files
-rw-r--r-- 1 prh users 610 Dec 9 09:52 l32-1.1.ebuild
# ls -l /usr/local/portage/sys-apps/l32/files/
-rw-r--r-- 1 prh users 335 Dec 9 10:01 l32_h-gentoo.patch
Note the name you have to give to the patch file you downloaded from the
bugs site. Note also the name of the ebuild file. I don't suppose the
ownership of the files matters, as you'll be operating as root anyway.
Next, create /usr/local/portage/distfiles/ if it doesn't exist already, and
put l32_1.1.tar.gz in there, not in the sys-apps/l32 directory (this seems
to be the step you've missed); the emerge process will construct a temporary
working directory for all that stuff. You don't need to go extracting the
tarball and editing its contents - that's what the patch file is for.
Oh, and don't put the tarball in /usr/portage/distfiles/ or it'll be erased
at the next emerge --sync!
Then, as Billy said, edit line 8 of files/l32_h-gentoo.patch to set the
directory where your chroot lives. In my case this is /mnt/gentoo32/, so my
line 8 reads:
+#define DEFAULT_LOWDIR "/mnt/gentoo32"
After that, run your digest-building command:
# ebuild /usr/local/portage/sys-apps/l32/l32-1.1.ebuild digest
and you can then emerge l32.
HTH. Let me know if I've missed something...
Linux Counter 5290, Aug 93.
email@example.com mailing list