Package Base Details: freetype2-infinality

Git Clone URL: https://aur.archlinux.org/freetype2-infinality.git (read-only)
Submitter: None
Maintainer: SolarAquarion
Last Packager: SolarAquarion
Votes: 470
Popularity: 0.100865
First Submitted: 2010-07-14 15:27
Last Updated: 2019-05-28 15:57

Latest Comments

« First ‹ Previous ... 7 8 9 10 11 12 13 14 15 16 17 ... Next › Last »

Anonymous comment on 2012-10-02 04:38

Hello! Does any one know whether we still need a cairo wich respect-fontconfig patch? It seems the patch hasn't been merged upstream. But only place on aur has this patch is cairo-ubuntu, which relys on freetype-ubuntu...

Anonymous comment on 2012-08-18 20:16

@graysky - My mistake. I had an old .zshrc where I had export GNUMAKE=gnumake set. Once I deleted that line everything compiled ok. Thanks for the help.

graysky commented on 2012-08-18 10:51

@rodyaj - No problems here. Have you tried to compile in a clean chroot? I'm guessing you're missing something on your system or have a bad conf file somewhere along the line.

Anonymous comment on 2012-08-18 03:26

Error trying to install 2.4.10-1:

GNU make (>= 3.80) or makepp (>= 1.19) is required to build FreeType2.
Please try
`GNUMAKE=<GNU make command name> ./configure'.
or >&2
`GNUMAKE="makepp --norc-substitution" ./configure'.

kvasthval commented on 2012-08-12 12:45


Am I the only one getting pagefaults in WINE with this installed? Could be related to the 32-bit libraries though, but there are no problems whatsoever with the vanilla freetype2 packages...

lazx888 commented on 2012-06-19 15:13

Having some trouble with some terminus (terminus-font-ttf) characters being cut off - any ideas on how to fix this?

Anonymous comment on 2012-06-19 14:32

About those newlines in bash array. That's probably from me. To me, they are neither extra nor ugly. Individual elements would be fine in one line, only if they are short, like 'foobar' or 'barfoo'. Longer elements certainly look better on a line of their own. It is also cleaner in a diff.

Huulivoide commented on 2012-06-19 14:11

Usually it is unneeded to copy the source to a secondary -build directory.
This only the case for git/svn/bzr/... packages as building in the same
directory will make the repository unclean possibly preventing further
updates, without making a whole new checkout/clone of the repository all
over again. Cmake based projects also usually have build directory as
usually cmake based projects support building outside the source directory,
unlike automake based ones. This keeps the sourcecode folder itself clean
from the compiled binary files.

Also adding few extra newlines to here and there, would improve the
readability of the PKGBUILD. Another this is also your
(
'foobar' 'barfoo'
)
parts. Why not just simply write ('foobar' 'barfoo') ? Why the extra/ugly
newlines in those? I'm refering to optdepends and source fields.

Anonymous comment on 2012-06-18 23:25

Never mind, got it. Turns out base-devel was uninstalled on my computer, so I just installed it again.

Anonymous comment on 2012-06-18 20:30

I have multilib-devel and fakeroot installed.