A resend of this message of yesterday, so that it should now appear in the list 
archives.


> On Fri, 1 January 2016, at 4:59 p.m., gevisz <gev...@gmail.com> wrote:
> 
> Below is the additional details of the second answer:
> 
>> Since you build from source on gentoo:
>> Can you check whether this appears when running ./configure?
>> checking for nl_langinfo and CODESET… yes

You should see this by re-emerging the package and watching the screen - there 
should be lots of "checking for" lines during the emerge output. You should be 
able to scroll back through it all when the package has finished emerging.

>> Also, which arguments are used for ./configure?

Look in the ebuild. [1]

It looks like it's configured with --with-lispdir=/$path/$to/$directory if you 
have the USE=emacs.

It looks like it applies an xemacs compatibility patch [2], but I doubt that 
makes a difference.

Otherwise, as far as I can see, it uses the makefile's defaults.

I'm not sure what's going on with "$(use_enable nls)" in the ebuild - perhaps 
someone else on this list could explain what USE=nls does for this package.


>> /* printf("encoding is %s, UTF8=%d\n", locale_encoding, isUTF8Locale); */
>> 
>> If that doesn't help, can you enable to printf above and post the
>> output?

If you run `sudo ebuild /usr/portage/app-misc/gtypist/gtypist-2.9.5.ebuild 
unpack` you should be able to find the file with that line. 

The "/*" and "*/" make that line into a comment, so "uncomment" it [3] by 
removing them. Save the file.

Now you should be able to run `sudo ebuild 
/usr/portage/app-misc/gtypist/gtypist-2.9.5.ebuild install` to install gtypist 
with the modified code. 

I haven't done this in a while, so hopefully someone will correct me if I've 
got anything wrong. My first instinct was to epatch, but I don't think that's 
necessary.

HTH,

Stroller.




[1] 
https://gitweb.gentoo.org/repo/gentoo.git/plain/app-misc/gtypist/gtypist-2.9.5.ebuild

[2] 
https://gitweb.gentoo.org/repo/gentoo.git/plain/app-misc/gtypist/files/gtypist-2.8.3-xemacs-compat.patch

[3] http://english.stackexchange.com/questions/33483/



Reply via email to