XeTeX very broken

[Lenore Horner]

I upgraded my OS and was told, correctly, that I hadn't followed the migration steps.  So I went back and did the migration steps again.  That did not fix my problem (can't create a valid pdf when the .tex file includes \includegraphics{file.png}).  So I followed the directions to completely uninstall MacPorts and start from scratch.  Now things are worse.  I can't produce any output whatsoever using xetex.

When I use the following command

/opt/local/libexec/texlive/texbin/xelatex --synctex=1 --interaction=nonstopmode /fullpath/HW06-07_Ch08.tex; SetFile -a V *.log *.aux *.nav *.out *.snm *.toc *.brf *.lof *synctex.gz *.cut *.vrb; open HW06-07_Ch08.pdf
This is XeTeX, Version 3.1415926-2.5-0.9999.3 (TeX Live 2013/MacPorts 2013_2)
 restricted \write18 enabled.
entering extended mode


I get the following error.

(/opt/local/share/texmf-texlive/tex/latex/euenc/eu1lmr.fd)kpathsea:make_tex: Invalid fontname `[lmroman10-regular]', contains '['

! Font EU1/lmr/m/n/10=[lmroman10-regular]:mapping=tex-text at 10.0pt not loadab
le: Metric (TFM) file or installed font not found.
<to be read again> 
                   relax 
l.100 \fontencoding\encodingdefault\selectfont
                                              
) (/opt/local/share/texmf-texlive/tex/xelatex/xunicode/xunicode.sty
! I can't find file `t3enc.def'.
l.852 \input t3enc.def

I can't find t3enc listed in the Macports list of where TexLive stuff is put.  I have installed the following TeX stuff.
texlive-basic @30847_0+doc (active)
  texlive-bin @2013_2+x11 (active)
  texlive-bin-extra @30842_0+doc (active)
  texlive-common @2013_0 (active)
  texlive-fontutils @30842_0+doc (active)
  texlive-generic-recommended @30396_0+doc (active)
  texlive-latex @30738_0+doc (active)
  texlive-latex-extra @30788_0+doc (active)
  texlive-latex-recommended @30811_0+doc (active)
  texlive-pictures @30637_0+doc (active)
  texlive-science @30307_0+doc (active)
  texlive-xetex @30842_0+doc (active)

Some goggling indicates not using fontspec would be a workaround, but those posts are old and mostly from Debian.  Why is this problem showing up here now?

Thanks,
Lenore