Opened 17 years ago

Closed 16 years ago

Last modified 16 years ago

#14185 closed defect (invalid)

teTeX 3.0_5 fails to build

Reported by: dershow Owned by: gwright@…
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: teTeX; gnuplot; link Cc: pguyot (Paul Guyot)
Port:

Description (last modified by jmpalacios (Juan Manuel Palacios))

I have teTeX installed 3.0_4 installed and I have tried to upgrade to 3.0_5 but I get the follow error:

/usr/bin/gcc-4.0 -o xdvi-xaw.bin browser.o dvi-draw.o dvi-init.o dvisel.o encodings.o events.o filehist.o font-open.o gf.o hypertex.o image-magick.o mime.o my-snprintf.o my-vsnprintf.o pagehist.o pk.o print-internal.o psdps.o psgs.o psheader.o psnews.o read-mapfile.o search-internal.o special.o string-utils.o tfmload.o util.o vf.o xdvi.o xserver-info.o x_util.o 1/lib  -L/opt/local/lib ./gui/libgui.a ../../libs/t1lib/libt1.a ../../libs/t1lib/../type1/libtype1.a -L/usr/X11R6 -L/usr/X11/lib -lXaw -lXmu -lXt -lSM -lICE -lXp -lXext -liconv -lXpm -lX11 -lXau -lXdmcp ../kpathsea/.libs/libkpathsea.a -lm
i686-apple-darwin9-gcc-4.0.1: 1/lib: No such file or directory
make[2]: *** [xdvi-xaw.bin] Error 1
make[1]: *** [all] Error 1
make: *** [all] Error 1

Error: Unable to upgrade port: 1

Frankly I am a little confused about what is installing teTeX at the moment. If I do:

port dependents teTeX
gnuplot depends on teTeX

but if I do:

port info gnuplot

I see texlive_base but not teTeX. And I don't currently have texlive installed.

For what it is worth, I see this ticket has discussions of changing over from teTeX to texlive: #12913. So could this problem have something to do with the transition? and my error is the same as this: http://www.nabble.com/tetex-won't-build-on-my-mbp-c2d-running-Leopard-td14851060.html but it seems that he didn't file a ticket.

Change History (13)

comment:1 Changed 17 years ago by jmpalacios (Juan Manuel Palacios)

Description: modified (diff)

comment:2 Changed 17 years ago by josh+macports@…

You have a library directory somewhere that ends in " 1", i.e. it has a space in its name, like "/usr/lib/ruby 1" or "/usr/X11R6 1". I suspect it's a backup copy created by the Leopard or XCode 3 installer.

comment:3 Changed 17 years ago by dershow

Yes. I can see that. In fact the prior command in the build includes: -L/usr/X11R6 1/lib

So that leads to the next questions of why that is there, and what to do about it? Is "X11R6 1" not a typical X11 path? Can Macports not deal with a space in the path name? The contents of /usr/X11R6 1/lib are all static libraries (.a) while /usr/X11/lib and /usr/X11R6/lib are all dynamic libraries (.dylib and .la). What could be related is that I upgraded from the standard Apple X11 to version 2.1.3 (from http://trac.macosforge.org/projects/xquartz) because otherwise the Gimp port would crash.

comment:4 Changed 17 years ago by danielluke (Daniel J. Luke)

On the two machines where I've upgraded from 10.4 to 10.5 the installer moved the 10.4 X11 stuff to /usr/X11R6 1/ while installing the new stuff into /usr/X11/

comment:5 Changed 17 years ago by dershow

In your case did it put any static libraries into the /usr/X11? The only static libraries at all (I did a search for .a) in /usr/X11* are the ones that are in "/usr/X11R6 1/lib/" Meanwhile "/usr/X11R6 1/" just contains: "include","lib" and "man," directories. So it is not just the stuff left over from 10.4. And, it seems like it might be useful, if anything needs to link static?

comment:6 Changed 17 years ago by danielluke (Daniel J. Luke)

Linking with static libraries is discouraged on Mac OS X (and in fact, it's totally unsupported to completely statically link an application).

comment:7 in reply to:  3 ; Changed 17 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: gwright@… removed
Owner: changed from macports-tickets@… to gwright@…

Replying to dersh@alum.mit.edu:

Yes. I can see that. In fact the prior command in the build includes:
-L/usr/X11R6 1/lib

So that leads to the next questions of why that is there, and what to do about it? Is "X11R6 1" not a typical X11 path? Can Macports not deal with a space in the path name? [snip]

"X11R6 1" is not a typical X11 location. MacPorts and probably lots of the software you can install using MacPorts cannot deal with paths with spaces in the path name. It's just not usual for unix software to support this, so this will probably never change. I don't know why "X11R6 1" is on your system but others' guesses in this ticket seem plausible. Probably you should remove it.

Replying to your questions in the issue description: gnuplot depends on a TeX program. It probably used to depend on teTeX but since teTeX is dead it was changed to texlive, but in such a way that if you already have teTeX it'll use that instead. This is intentional, so that you can select the TeX program that you prefer.

Assigning ticket to maintainer of teTeX.

comment:8 in reply to:  7 Changed 17 years ago by cleonello@…

Replying to ryandesign@macports.org:

"X11R6 1" is not a typical X11 location. MacPorts and probably lots of the software you can install using MacPorts cannot deal with paths with spaces in the path name. It's just not usual for unix software to support this, so this will probably never change. I don't know why "X11R6 1" is on your system but others' guesses in this ticket seem plausible. Probably you should remove it.

Replying to your questions in the issue description: gnuplot depends on a TeX program. It probably used to depend on teTeX but since teTeX is dead it was changed to texlive, but in such a way that if you already have teTeX it'll use that instead. This is intentional, so that you can select the TeX program that you prefer.

Assigning ticket to maintainer of teTeX.

I have the same issue. Is there any workaround for this? Can the portfile or makefile or cofigure script be hacked to igonore this directory and not add it to the library search path?

Or, as suggested in the nabble post mentioned above, can I manual link? How would that be done? Would I then rerun port install after linking?

comment:9 Changed 17 years ago by dershow

The work around that did the job for me was to rename, or move, those directories. For example just:

sudo mv "/usr/X11R6 1" /usr/X11R61 sudo mv "/usr/lib/ruby 1" /usr/lib/ruby1 did the job for me.

comment:10 in reply to:  9 Changed 17 years ago by cleonello@…

Replying to dersh@alum.mit.edu:

The work around that did the job for me was to rename, or move, those directories. For example just:

sudo mv "/usr/X11R6 1" /usr/X11R61 sudo mv "/usr/lib/ruby 1" /usr/lib/ruby1 did the job for me.

Thanks. Did that followed by a "port clean teTex" and "port install teTex" and it fixed the spurious search path entry. Found another problem with the link command, however. Notice the extra library "1" just before the first -L entry in the command:

/usr/bin/gcc-4.0 -o xdvi-xaw.bin browser.o dvi-draw.o dvi-init.o dvisel.o encodings.o events.o filehist.o font-open.o gf.o hypertex.o image-magick.o mime.o my-snprintf.o my-vsnprintf.o pagehist.o pk.o print-internal.o psdps.o psgs.o psheader.o psnews.o read-mapfile.o search-internal.o special.o string-utils.o tfmload.o util.o vf.o xdvi.o xserver-info.o x_util.o 1 -L/opt/local/lib ./gui/libgui.a ../../libs/t1lib/libt1.a ../../libs/t1lib/../type1/libtype1.a -L/usr/lib/ruby -L/usr/X11/lib -lXaw -lXmu -lXt -lSM -lICE -lXp -lXext -liconv -lXpm -lX11 -lXau -lXdmcp ../kpathsea/.libs/libkpathsea.a -lm

This was actually the problem reported in the mailing list post. I got around this by running the above command (w/o the "1" libraray entry) in the "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_print_teTeX/work/tetex-src-3.0/texk/xdvik" directory. Then ran "port install teTex" and it finished the install.

comment:11 Changed 17 years ago by dershow

Yes, that was the same problem that I was seeing. If you take a look at the command that printed just before the /usr/bin/gcc-4.0 .... above then you can probably find a library path that has a space then a 1 in it (of the form "/usr/X11R6 1"). And if you rename that directory to get rid of the space, then:

sudo clean --work teTeX

Then I would guess that it will install correctly (at least it did for me).

comment:12 Changed 16 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Resolution: invalid
Status: newclosed

The solution has been documented in the ProblemHotlist.

comment:13 Changed 16 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

Note: See TracTickets for help on using tickets.