First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 6856
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Seemant Kulleen (RETIRED) <seemant@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Julien Herfurth <jherfurth@arafox.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 6856 depends on: Show dependency tree
Bug 6856 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2002-08-21 14:15 0000 
Hi,

It seems that giving the option --enable-freetype to the configure script does
excatly the opposite of what it is supposed to do : it disables the freetype
support ! If you read the output of ./configure --enable-freetype, I can see :

checking if --disable-freetype option specified... yes

obviously not what we want :-).

I replaced :

use truetype \
    && myconf=${myconf} --enable-freetype \
    || myconf=${myconf} --disable-freetype

by :

use truetype \
    || myconf=${myconf} --disable-freetype

and it works all right now.

Julien

------- Comment #1 From Seemant Kulleen (RETIRED) 2002-08-23 06:32:06 0000 ------- 
thanks for catching that.  fixed in portage.
First Last Prev Next    No search results available      Search page      Enter new bug