Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 102055 Details for
Bug 154946
sci-visualization/epix fails in sample directory
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
sample.log
sample.log (text/plain), 28.51 KB, created by
Juergen Rose
on 2006-11-16 04:51:29 UTC
(
hide
)
Description:
sample.log
Filename:
MIME Type:
Creator:
Juergen Rose
Created:
2006-11-16 04:51:29 UTC
Size:
28.51 KB
patch
obsolete
>This is pdfeTeX, Version 3.141592-1.30.5-2.2 (Web2C 7.5.5) (format=latex 2006.7.17) 15 NOV 2006 23:12 >entering extended mode >**sample >(./sample.tex >LaTeX2e <2003/12/01> >Babel <v3.8d> and hyphenation patterns for american, french, german, ngerman, b >ahasa, basque, bulgarian, catalan, croatian, czech, danish, dutch, esperanto, e >stonian, finnish, greek, icelandic, irish, italian, latin, magyar, norsk, polis >h, portuges, romanian, russian, serbian, slovak, slovene, spanish, swedish, tur >kish, ukrainian, nohyphenation, loaded. >(/usr/share/texmf/tex/latex/base/article.cls >Document Class: article 2004/02/16 v1.4f Standard LaTeX document class >(/usr/share/texmf/tex/latex/base/size11.clo >File: size11.clo 2004/02/16 v1.4f Standard LaTeX file (size option) >) >\c@part=\count79 >\c@section=\count80 >\c@subsection=\count81 >\c@subsubsection=\count82 >\c@paragraph=\count83 >\c@subparagraph=\count84 >\c@figure=\count85 >\c@table=\count86 >\abovecaptionskip=\skip41 >\belowcaptionskip=\skip42 >\bibindent=\dimen102 >) (/usr/share/texmf/tex/latex/amsmath/amsmath.sty >Package: amsmath 2000/07/18 v2.13 AMS math features >\@mathmargin=\skip43 >For additional information on amsmath, use the `?' option. >(/usr/share/texmf/tex/latex/amsmath/amstext.sty >Package: amstext 2000/06/29 v2.01 >(/usr/share/texmf/tex/latex/amsmath/amsgen.sty >File: amsgen.sty 1999/11/30 v2.0 >\@emptytoks=\toks14 >\ex@=\dimen103 >)) (/usr/share/texmf/tex/latex/amsmath/amsbsy.sty >Package: amsbsy 1999/11/29 v1.2d >\pmbraise@=\dimen104 >) (/usr/share/texmf/tex/latex/amsmath/amsopn.sty >Package: amsopn 1999/12/14 v2.01 operator names >) >\inf@bad=\count87 >LaTeX Info: Redefining \frac on input line 211. >\uproot@=\count88 >\leftroot@=\count89 >LaTeX Info: Redefining \overline on input line 307. >\classnum@=\count90 >\DOTSCASE@=\count91 >LaTeX Info: Redefining \ldots on input line 379. >LaTeX Info: Redefining \dots on input line 382. >LaTeX Info: Redefining \cdots on input line 467. >\Mathstrutbox@=\box26 >\strutbox@=\box27 >\big@size=\dimen105 >LaTeX Font Info: Redeclaring font encoding OML on input line 567. >LaTeX Font Info: Redeclaring font encoding OMS on input line 568. >\macc@depth=\count92 >\c@MaxMatrixCols=\count93 >\dotsspace@=\muskip10 >\c@parentequation=\count94 >\dspbrk@lvl=\count95 >\tag@help=\toks15 >\row@=\count96 >\column@=\count97 >\maxfields@=\count98 >\andhelp@=\toks16 >\eqnshift@=\dimen106 >\alignsep@=\dimen107 >\tagshift@=\dimen108 >\tagwidth@=\dimen109 >\totwidth@=\dimen110 >\lineht@=\dimen111 >\@envbody=\toks17 >\multlinegap=\skip44 >\multlinetaggap=\skip45 >\mathdisplay@stack=\toks18 >LaTeX Info: Redefining \[ on input line 2666. >LaTeX Info: Redefining \] on input line 2667. >) (/usr/share/texmf/tex/latex/base/latexsym.sty >Package: latexsym 1998/08/17 v2.2e Standard LaTeX package (lasy symbols) >\symlasy=\mathgroup4 >LaTeX Font Info: Overwriting symbol font `lasy' in version `bold' >(Font) U/lasy/m/n --> U/lasy/b/n on input line 47. >) (/usr/share/texmf/tex/latex/graphics/pstcol.sty >Package: pstcol 2001/06/20 v1.1 PSTricks color colompatibility (DPC) >(/usr/share/texmf/tex/latex/pstricks/pstricks.sty >Package: pstricks 2005/12/19 v0.31 LaTeX wrapper for `PSTricks' (RN,HV) >(/usr/share/texmf/tex/generic/pstricks/pstricks.tex >`PSTricks' v1.14a <2006/02/06> (tvz) >\pst@dima=\dimen112 >\pst@dimb=\dimen113 >\pst@dimc=\dimen114 >\pst@dimd=\dimen115 >\pst@dimg=\dimen116 >\pst@dimh=\dimen117 >\pst@hbox=\box28 >\pst@boxg=\box29 >\pst@cnta=\count99 >\pst@cntb=\count100 >\pst@cntc=\count101 >\pst@cntd=\count102 >\pst@cntg=\count103 >\pst@cnth=\count104 >\pst@toks=\toks19 >(/usr/share/texmf/tex/generic/pstricks/pstricks.con) >\psunit=\dimen118 >\psxunit=\dimen119 >\psyunit=\dimen120 >\pslinewidth=\dimen121 >\pst@customdefs=\toks20 >\pslinearc=\dimen122 >\everypsbox=\toks21 >\psframesep=\dimen123 >\pslabelsep=\dimen124 >\psk@shift=\dimen125 >\pst@shift=\dimen126 >\theoverlaybox=\box30 >) >File: pstricks.tex 2006/02/06 v1.14a `PSTricks' (tvz) >(/usr/share/texmf/tex/latex/xcolor/xcolor.sty >Package: xcolor 2005/12/21 v2.09 LaTeX color extensions (UK) >(/usr/share/texmf/tex/latex/graphics/color.cfg >File: color.cfg 2005/02/03 v1.3 color configuration of teTeX/TeXLive >) >Package xcolor Info: Package option `override' ignored on input line 211. >Package xcolor Info: Driver file: dvips.def on input line 220. >(/usr/share/texmf/tex/latex/graphics/dvips.def >File: dvips.def 1999/02/16 v3.0i Driver-dependant file (DPC,SPQR) >) >Package xcolor Info: Model `cmy' substituted by `cmy0' on input line 1328. >Package xcolor Info: Model `RGB' extended on input line 1344. >Package xcolor Info: Model `HTML' substituted by `rgb' on input line 1346. >Package xcolor Info: Model `Hsb' substituted by `hsb' on input line 1347. >Package xcolor Info: Model `tHsb' substituted by `hsb' on input line 1348. >Package xcolor Info: Model `HSB' substituted by `hsb' on input line 1349. >Package xcolor Info: Model `Gray' substituted by `gray' on input line 1350. >Package xcolor Info: Model `wave' substituted by `hsb' on input line 1351. >)) >! Undefined control sequence. ><recently read> \@@drv > >l.35 \definecolor{darkgray}{gray}{.25} > >The control sequence at the end of the top line >of your error message was never \def'ed. If you have >misspelled it (e.g., `\hobx'), type `I' and the correct >spelling (e.g., `I\hbox'). Otherwise just continue, >and I'll forget about whatever was undefined. > > >! LaTeX Error: Missing \begin{document}. > >See the LaTeX manual or LaTeX Companion for explanation. >Type H <return> for immediate help. > ... > >l.35 \definecolor{darkgray}{gray}{.25} > >You're in trouble here. Try typing <return> to proceed. >If that doesn't work, type X <return> to quit. > >! Undefined control sequence. ><argument> ...\fi \fi \toks@ \expandafter {\@@drv > }\edef \@@tmp {\ifglobalco... >l.35 \definecolor{darkgray}{gray}{.25} > >The control sequence at the end of the top line >of your error message was never \def'ed. If you have >misspelled it (e.g., `\hobx'), type `I' and the correct >spelling (e.g., `I\hbox'). Otherwise just continue, >and I'll forget about whatever was undefined. > >! Undefined control sequence. ><recently read> \@@drv > >l.36 \definecolor{gray}{gray}{.5} > >The control sequence at the end of the top line >of your error message was never \def'ed. If you have >misspelled it (e.g., `\hobx'), type `I' and the correct >spelling (e.g., `I\hbox'). Otherwise just continue, >and I'll forget about whatever was undefined. > >! Undefined control sequence. ><argument> ...\fi \fi \toks@ \expandafter {\@@drv > }\edef \@@tmp {\ifglobalco... >l.36 \definecolor{gray}{gray}{.5} > >The control sequence at the end of the top line >of your error message was never \def'ed. If you have >misspelled it (e.g., `\hobx'), type `I' and the correct >spelling (e.g., `I\hbox'). Otherwise just continue, >and I'll forget about whatever was undefined. > >! Undefined control sequence. ><recently read> \@@drv > >l.37 \definecolor{lightgray}{gray}{.75} > >The control sequence at the end of the top line >of your error message was never \def'ed. If you have >misspelled it (e.g., `\hobx'), type `I' and the correct >spelling (e.g., `I\hbox'). Otherwise just continue, >and I'll forget about whatever was undefined. > >! Undefined control sequence. ><argument> ...\fi \fi \toks@ \expandafter {\@@drv > }\edef \@@tmp {\ifglobalco... >l.37 \definecolor{lightgray}{gray}{.75} > >The control sequence at the end of the top line >of your error message was never \def'ed. If you have >misspelled it (e.g., `\hobx'), type `I' and the correct >spelling (e.g., `I\hbox'). Otherwise just continue, >and I'll forget about whatever was undefined. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.41 \psset@bordercolor{white} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{gray 1}{gray}{1}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.41 \psset@bordercolor{white} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.42 \psset@doublecolor{white} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{gray 1}{gray}{1}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.42 \psset@doublecolor{white} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.43 \psset@linecolor{black} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{gray 0}{gray}{0}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.43 \psset@linecolor{black} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.44 \psset@fillcolor{white} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{gray 1}{gray}{1}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.44 \psset@fillcolor{white} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.45 \psset@hatchcolor{black} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{gray 0}{gray}{0}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.45 \psset@hatchcolor{black} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.46 \psset@gridcolor{black} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{gray 0}{gray}{0}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.46 \psset@gridcolor{black} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.47 \psset@gridlabelcolor{black} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{gray 0}{gray}{0}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.47 \psset@gridlabelcolor{black} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.48 \psset@shadowcolor{darkgray} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{}{gray}{0.25}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.48 \psset@shadowcolor{darkgray} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.49 \psset@subgridcolor{gray} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{}{gray}{0.5}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.49 \psset@subgridcolor{gray} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >) (/usr/share/texmf/tex/latex/eepic/epic.sty >Enhancements to Picture Environment. Version 1.2 - Released June 1, 1986 >\@@multicnt=\count105 >\d@lta=\count106 >\@delta=\dimen127 >\@@delta=\dimen128 >\@gridcnt=\count107 >\@joinkind=\count108 >\@dotgap=\dimen129 >\@ddotgap=\dimen130 >\@x@diff=\count109 >\@y@diff=\count110 >\x@diff=\dimen131 >\y@diff=\dimen132 >\@dotbox=\box31 >\num@segments=\count111 >\num@segmentsi=\count112 >\@datafile=\read1 >) (/usr/share/texmf/tex/latex/eepic/eepic.sty >Extension to Epic and LaTeX. Version 1.1e - Released Dec 21, 1999 >\@gphlinewidth=\count113 >\@eepictcnt=\count114 >\@tempdimc=\dimen133 >\maxovaldiam=\dimen134 >\@filltype=\box32 >) (/usr/share/texmf/tex/latex/rotating/rotating.sty >Package: rotating 1997/09/26 v2.13 Rotation package >(/usr/share/texmf/tex/latex/graphics/graphicx.sty >Package: graphicx 1999/02/16 v1.0f Enhanced LaTeX Graphics (DPC,SPQR) >(/usr/share/texmf/tex/latex/graphics/keyval.sty >Package: keyval 1999/03/16 v1.13 key=value parser (DPC) >\KV@toks@=\toks22 >) (/usr/share/texmf/tex/latex/graphics/graphics.sty >Package: graphics 2001/07/07 v1.0n Standard LaTeX Graphics (DPC,SPQR) >(/usr/share/texmf/tex/latex/graphics/trig.sty >Package: trig 1999/03/16 v1.09 sin cos tan (DPC) >) (/usr/share/texmf/tex/latex/graphics/graphics.cfg >File: graphics.cfg 2005/02/03 v1.3 graphics configuration of teTeX/TeXLive >) >Package graphics Info: Driver file: dvips.def on input line 80. >) >\Gin@req@height=\dimen135 >\Gin@req@width=\dimen136 >) (/usr/share/texmf/tex/latex/base/ifthen.sty >Package: ifthen 2001/05/26 v1.1c Standard LaTeX ifthen package (DPC) >) >\c@r@tfl@t=\count115 >\rot@float@box=\box33 >) >No file sample.aux. >\openout1 = `sample.aux'. > >LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 28. >LaTeX Font Info: ... okay on input line 28. >LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 28. >LaTeX Font Info: ... okay on input line 28. >LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 28. >LaTeX Font Info: ... okay on input line 28. >LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 28. >LaTeX Font Info: ... okay on input line 28. >LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 28. >LaTeX Font Info: ... okay on input line 28. >LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 28. >LaTeX Font Info: ... okay on input line 28. >[1 > >] >LaTeX Font Info: Try loading font information for U+lasy on input line 30. >(/usr/share/texmf/tex/latex/base/ulasy.fd >File: ulasy.fd 1998/08/17 v2.2e LaTeX symbol font definitions >) >LaTeX Font Info: Try loading font information for OMS+cmr on input line 48. >(/usr/share/texmf/tex/latex/base/omscmr.fd >File: omscmr.fd 1999/05/25 v2.5h Standard LaTeX font definitions >) >LaTeX Font Info: Font shape `OMS/cmr/m/n' in size <10.95> not available >(Font) Font shape `OMS/cmsy/m/n' tried instead on input line 48. >[2] (./parabola.eepic) [3 > >] (./cropplot.eepic) [4 > >] (./polar.eepic) [5 > >] (./shadeplot.eepic) [6 > >] (./newton.eepic) [7 > >] (./calculus.eepic) [8 > >] (./slopefield.eepic) [9 > >] (./denom.eepic) [10 > >] (./weierstrass.eepic) [11 > >] (./uppersum.eepic) [12 > >] (./wheel.eepic) [13 > >] [14] > >LaTeX Warning: Reference `fig:sphere' on page 15 undefined on input line 688. > >(./sphere.eepic) [15 > >] (./geomsum.eepic >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.13 \psset{fillcolor=lightgray, linecolor=white} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{}{gray}{0.75}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.13 \psset{fillcolor=lightgray, linecolor=white} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.13 \psset{fillcolor=lightgray, linecolor=white} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{gray 1}{gray}{1}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.13 \psset{fillcolor=lightgray, linecolor=white} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.18 \psset{fillcolor=blue} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{rgb 0 0 1}{rgb}{0,0,1}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.18 \psset{fillcolor=blue} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >) [16 > >] (./pascal.eepic) [17 > >] (./contour.eepic >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.14 ...olor=orange,linecolor=red,linewidth=1.5pt} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{rgb 1 0.7 0.2}{rgb}{1,0.7,0.2}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.14 ...olor=orange,linecolor=red,linewidth=1.5pt} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.14 ...olor=orange,linecolor=red,linewidth=1.5pt} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{rgb 1 0 0}{rgb}{1,0,0}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.14 ...olor=orange,linecolor=red,linewidth=1.5pt} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >) [18 > >] (./pole.eepic) >Overfull \hbox (3.28027pt too wide) in paragraph at lines 967--967 >[] \OT1/cmtt/m/n/10.95 label(P(x_min, y_max), P(2,-2), "$z=\\mathrm{Re}\\,\\fr >ac{1}{x+iy}$", br);[] > [] > > >Overfull \hbox (55.01846pt too wide) in paragraph at lines 967--967 >[] \OT1/cmtt/m/n/10.95 clip(); clip_box(P(-Bd,-Bd,-Bd), P(Bd,Bd,0)); fill(); s >urface(F, R); // bottom half[] > [] > > >Overfull \hbox (26.27502pt too wide) in paragraph at lines 967--967 >[] \OT1/cmtt/m/n/10.95 pen(0.15); rgb(0.75,0.75,0.75); plot(F, R); plain(); / >/ simulate transparency[] > [] > > >Overfull \hbox (32.02371pt too wide) in paragraph at lines 967--967 >[] \OT1/cmtt/m/n/10.95 clip(); clip_box(P(-Bd,-Bd,0), P(Bd,Bd,Bd)); fill(); su >rface(F, R); // top half[] > [] > >[19 > >] (./sqrt.eepic) [20] (./lissajous.eepic) (./koch.eepic) (./oscillator.eepic) ( >./torus.eepic) (./levelset.eepic) (./clipping.eepic >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.915 ...inecolor=axis_color,fillcolor=axis_color} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{rgb 0.8 0.2 0.9}{rgb}{0.8,0.2,0.9}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.915 ...inecolor=axis_color,fillcolor=axis_color} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.915 ...inecolor=axis_color,fillcolor=axis_color} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{rgb 0.8 0.2 0.9}{rgb}{0.8,0.2,0.9}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.915 ...inecolor=axis_color,fillcolor=axis_color} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.1743 ...ecolor=axis_color, fillcolor=axis_color} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{rgb 0.8 0.2 0.9}{rgb}{0.8,0.2,0.9}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.1743 ...ecolor=axis_color, fillcolor=axis_color} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >! Argument of \c@lor@to@ps has an extra }. ><inserted text> > \par >l.1743 ...ecolor=axis_color, fillcolor=axis_color} > >I've run across a `}' that doesn't seem to match anything. >For example, `\def\a#1{...}' and `\a}' would produce >this error. If you simply proceed now, the `\par' that >I've just inserted will cause me to report a runaway >argument that might be the root of the problem. But if >your `}' was spurious, just type `2' and it will go away. > >Runaway argument? >\xcolor@ {}{rgb 0.8 0.2 0.9}{rgb}{0.8,0.2,0.9}\@@ >! Paragraph ended before \c@lor@to@ps was complete. ><to be read again> > \par >l.1743 ...ecolor=axis_color, fillcolor=axis_color} > >I suspect you've forgotten a `}', causing me to apply this >control sequence to too much text. How can we recover? >My plan is to forget the whole thing and hope for the best. > >) [21 > > >] (./sample.aux) > >LaTeX Warning: There were undefined references. > > >LaTeX Warning: Label(s) may have changed. Rerun to get cross-references right. > > ) >Here is how much of TeX's memory you used: > 2853 strings out of 49433 > 32390 string characters out of 425589 > 300021 words of memory out of 1100000 > 5976 multiletter control sequences out of 10000+15000 > 13479 words of font info for 54 fonts, out of 400000 for 2000 > 580 hyphenation exceptions out of 1000 > 37i,12n,39p,246b,319s stack positions out of 1500i,500n,1500p,200000b,5000s > >Output written on sample.dvi (21 pages, 546520 bytes).
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 154946
:
101917
| 102055