On Sat, 26 Nov 2011 22:19:59 -0600, DJ Lucas <d...@linuxfromscratch.org> wrote:
> On 11/26/2011 10:02 PM, DJ Lucas wrote:
>> On 11/26/2011 09:27 PM, DJ Lucas wrote:
>>> Latest gettext configure can hang in chapter 5 on "checking where .elc
>>> files should go..." if emacs is installed on the host. Should probably
>>> add "--without-emacs" and probably "--without-git" to the chapter 5
>>> gettext configure flags. Though I did not have any trouble with git, it
>>> will not be available in the chroot environment, but is picked up by
>>> default.
>>>
>>> -- DJ Lucas
>>>
>>>
>> Scratch that...bad troubleshooting, forgot to put the symlink back.
>> Something is broken in gettext-tools/configure. Looking into it now.
>>
> This is related to having /usr/bin/emacs -> zile symlink on x86_64 (does
> not affect 32bit builds). Bug has aparently been there for a very long
> time. Workaround is 'EMACS="no" ./configure ...' Not sure how gentoo
> handles this internally. Suitable for the book, or just blacklist x86_64
> Gentoo as a suitable host? I've been using the Gentoo Live DVD for x86
> builds for a while now (and I used to use System Rescue CD, which I've
> seen mentioned a few times), but this was first build on x86_64. Anybody
> have GNU Zile on some other x86_64 host that can double check this?

Thanks for the report, DJ.  I can't double-check myself as I build on x86
still.  However, your analysis looks fine, and the simple workaround of setting
EMACS=no is certainly suitable for the book (far more suitable than blacklisting
an entire distribution).

I'll add it to the book during the next round of updates.

Thanks,

Matt. 
> 
> -- DJ Lucas
> 
> 
> --
> This message has been scanned for viruses and
> dangerous content, and is believed to be clean.
> 
> --
> http://linuxfromscratch.org/mailman/listinfo/lfs-dev
> FAQ: http://www.linuxfromscratch.org/faq/
> Unsubscribe: See the above information page

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to