From owner-freebsd-ports@FreeBSD.ORG Mon May 9 21:58:17 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C66B016A4EA; Mon, 9 May 2005 21:58:17 +0000 (GMT) Received: from uriah.heep.sax.de (uriah.heep.sax.de [213.240.137.9]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41DFC43D88; Mon, 9 May 2005 21:58:17 +0000 (GMT) (envelope-from j@uriah.heep.sax.de) Received: from localhost (localhost [127.0.0.1]) by uriah.heep.sax.de (Postfix) with ESMTP id E1E924C0; Mon, 9 May 2005 23:58:14 +0200 (MET DST) Received: from uriah.heep.sax.de (localhost [127.0.0.1]) by localhost (AvMailGate-2.0.2-10) id 37916-43B386D9; Mon, 09 May 2005 23:58:14 +0200 Received: by uriah.heep.sax.de (Postfix, from userid 107) id A597F1AF; Mon, 9 May 2005 23:58:14 +0200 (MET DST) Date: Mon, 9 May 2005 23:58:14 +0200 From: Joerg Wunsch To: ports@freebsd.org Message-ID: <20050509215814.GM60161@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-GPG-Fingerprint: 5E84 F980 C3CA FD4B B584 1070 F48C A81B 69A8 5873 X-AntiVirus: checked by AntiVir MailGate (version: 2.0.2-10; AVE: 6.30.0.12; VDF: 6.30.0.162; host: uriah.heep.sax.de) cc: hrs@FreeBSD.org cc: bsd@freebsd.org Subject: teTeX 3.0 woes X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Joerg Wunsch List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 May 2005 21:58:17 -0000 I've come across a number of occasions where the new pdflatex-based LaTeX produces PDF files where it's normally supposed to generate a DVI file instead. My devel/simulavr port is currently broken for that; while one could blame doxygen (which produces the LaTeX source in question) for that, I haven't even found a way at all to tweak the LaTeX file so it would cause a PDF file to be generated. (I could find a fix for devel/avr-libc's documentation that is also doxygen- generated. The very same fix doesn't work for simulavr though.) Now, with running texi2dvi (which comes from teTeX itself) on devel/avrdude's texinfo documentation, I run into the same issue. There appears to be no chance to convince the new LaTeX command to actually generate DVI in some situations. Does anyone know of a remedy for this? [Please keep me Cc'ed, I'm not subscribed on ports@freebsd.org] -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)