Bug 87127 – resolution to bug 27548 will still give ewarnings and will not create bytecode freetype

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Bernard Edlington 2005-03-29 08:53:38 UTC]

unfortunately even when I apply the resolution to this bug "USE=bindist emerge freetype" there is still a ewarning saying bytecode has NOT been sucessfull.
 the problem lies in the freetype 2.1.9 ebuild flag -DTT_CONFIG_OPTION_BYTECODE_INTERPRETER which seems to have no effect.
only by paching ftoption.h can bytecode be enabled

Reproducible: Always
Steps to Reproduce:
1.USE=bindist emerge freetype
2.
3.

Actual Results:  
no bytecode freetype and ewarning saying bytecode has NOT been sucessfull.

Expected Results:  
bytecode freetype and no ewarning

[Comment 1 Bernard Edlington 2005-03-29 08:54:11 UTC]

Created attachment 54769 [details, diff]
ebuild fix

[Comment 2 Carsten Lohrke (RETIRED) 2005-03-29 10:43:58 UTC]

Um, are we picky today? ;)

[Comment 3 foser (RETIRED) 2005-03-29 13:25:57 UTC]

the warning is correct.

let me get this straight, you compile with USE=bindist & get the message that the bytecode interpreter is disabled ? And if you compile with USE=-bindist you get no such message ?

btw, i must say while looking into this once again to be sure *bareuh* I had a hard time seeing the difference between the BI & AH.

[Comment 4 Bernard Edlington 2005-03-29 18:40:58 UTC]

both USE=" -bindist" and USE="bindist" give the same ftoption.h file. I am sure that with the bindist flag enabled TT_CONFIG_OPTION_BYTECODE_INTERPRETER should be uncommented. I know its really nitpickin, and is barely noticeable.  Except with some apps (ie some emulation stuff).
- bernie

[Comment 5 foser (RETIRED) 2005-03-30 02:04:50 UTC]

You didn't answer my question.

[Comment 6 Bernard Edlington 2005-03-30 09:20:04 UTC]

No with USE=bindist I get the message that the bytecode interpreter is disabled.  And if I compile with USE=-bindist I also get the message.  in other words the bindist flag has no effect. 

[Comment 7 Bernard Edlington 2005-03-30 09:24:33 UTC]

The file the r1 ebuild checks ftoption.h is the same with USE=bindist and USE=-bindist.  So either ditch the bindist flag or as I patched - change the file it checks.  Whatdo you think? 

[Comment 8 foser (RETIRED) 2005-03-30 13:32:26 UTC]

it works fine here, but i have some clue why it may not work correctly in some cases. What shell are you using ?

[Comment 9 Bernard Edlington 2005-04-01 05:38:06 UTC]

bash. wierd hey?  Once the ebuild is completed the file /usr/include/freetype2/freetype/config/ftoption.h has the line 439 TT_CONFIG_OPTION_BYTECODE_INTERPRETER commented out.  If I am not mistaken this should be uncommented when bindist is in the use flag right?

[Comment 10 foser (RETIRED) 2005-04-01 07:12:53 UTC]

keep the attitude to yourself please. Don't get so hung up on your config patch, we do exactly the same thing in another way.

[Comment 11 Bernard Edlington 2005-04-01 10:00:16 UTC]

no probs. btw no attitude intended

[Comment 12 foser (RETIRED) 2005-04-01 10:10:12 UTC]

i made some minor changes to the 2.1.9-r1 ebuild which will hopefully remedy your problem. Please sync and see (got to have cvs revision 1.17 at least in the ebuild header).

[Comment 13 foser (RETIRED) 2006-06-20 05:37:13 UTC]

for 2.2.1 we now patch the config option in the header, b/c some apps rely on that.