texlive-bin @2013_3 - upgrade failure

[dan@…]

Got an error on textlive-bin when running "upgrade outdated". Cleaned the port, and tried again:

Dan:~ dan$ sudo port clean texlive-bin
--->  Cleaning texlive-bin
Dan:~ dan$ sudo port upgrade !$
sudo port upgrade texlive-bin
--->  Computing dependencies for texlive-bin
--->  Fetching archive for texlive-bin
Warning: Your DNS servers incorrectly claim to know the address of nonexistent hosts. This may cause checksum mismatches for some ports.
--->  Attempting to fetch texlive-bin-2013_3+motif+x11.darwin_13.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/texlive-bin
--->  Attempting to fetch texlive-bin-2013_3+motif+x11.darwin_13.x86_64.tbz2 from http://packages.macports.org/texlive-bin
--->  Attempting to fetch texlive-bin-2013_3+motif+x11.darwin_13.x86_64.tbz2 from http://lil.fr.packages.macports.org/texlive-bin
--->  Fetching distfiles for texlive-bin
--->  Verifying checksums for texlive-bin
--->  Extracting texlive-bin
--->  Applying patches to texlive-bin
--->  Configuring texlive-bin
--->  Building texlive-bin
Error: org.macports.build for port texlive-bin returned: command execution failed
Please see the log file for port texlive-bin for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_tex_texlive-bin/texlive-bin/main.log
Error: Unable to upgrade port: 1
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

[dan@…]

Build log

[ryandesign (Ryan Carsten Schmidt)]

The log says:

cannot find the library `/opt/local/lib/libX11.la' or unhandled argument `/opt/local/lib/libX11.la'

On Mavericks, MacPorts handles .la files differently than on previous systems, so this suggests you did not follow the migration instructions.

[dan@…]

Replying to ryandesign@…:

On Mavericks, MacPorts handles .la files differently than on previous systems, so this suggests you did not follow the migration instructions.

You're right. I did install the new command line tools, but I didn't do a full un-install / re-install of everything. That seems to have fixed it.

Thanks.

[drkp (Dan Ports)]

Glad it's working now!