7

I am getting the abovementioned error when compiling a moderncv file in Texmaker. I recently switched to Windows 10.

I have tried the solutions mentioned here and here but nothing worked. I am completely clueless what else I could try.

Do I need to install FontAwesome seperately as a font on my system?

C.Carl
  • 728

3 Answers3

4

I have the same problem here.

I think, the problem is, that the 'casual' of modernvc uses the fontawesome package, which only works with lualatex or xelatex.

When using

\moderncvstyle{classic} 

instead of

\moderncvstyle{casual} 

it works for me.

See also this answer: How to use fontawesome-package in moderncv?

Since I like the 'casual' more than 'classic' I am still looking for a way to use it without fontawesome.

Stiefel
  • 156
2

A manual activation using \usepackage{fontawesome} in the line just below \documentclass fixed the error for me.

Previously I tried reinstalling moderncv and fontawesome via Miktex-Console (Admin). I use pdfLaTeX.

Franz
  • 31
0

I had the same problem with the font-awesome package. I needed to tell my TEX engine where to find the Map file for the font-awesome font. Running

updmap-sys --enable Map fontawesome.map   

(inside /usr/share/texmf-dist/tex/fontawesome/map)

fixed it for me.

j3la
  • 11