Originally noticed the lack of /usr/local/avr/include/ after an upgrade, no matter that /var/db/pkg/avr-binutils-2.15_1/+CONTENTS said there should be one. Seems to be two problems: 1) pdflatex is missing causing the make to fail. 2) when portinstall/portupgrade is used the above error is not noticed. Fix: Creating a bogus pdflatex in my path didn't help. How-To-Repeat: portinstall avr-libc Seems we are lacking pdflatex: # cd /usr/ports/devel/avr-libc # make .. cd latex_pdf_src && \ sed -e '/{demo.eps}/s/demo.eps/demo.pdf/' \ group__demo__project.tex > tmp.$ && \ mv -f tmp.$ group__demo__project.tex cd latex_pdf_src && gmake refman.pdf gmake[2]: Entering directory `/usr/ports/devel/avr-libc/work/avr-libc-1.2.1/build/doc/api/latex_pdf_src' pdflatex refman.tex gmake[2]: pdflatex: Command not found gmake[2]: *** [refman.pdf] Error 127 gmake[2]: Leaving directory `/usr/ports/devel/avr-libc/work/avr-libc-1.2.1/build/doc/api/latex_pdf_src' gmake[1]: *** [avr-libc-user-manual.pdf] Error 2 gmake[1]: Leaving directory `/usr/ports/devel/avr-libc/work/avr-libc-1.2.1/build/doc/api' gmake: *** [all-recursive] Error 1 *** Error code 1 Stop in /usr/ports/devel/avr-libc/work/avr-libc-1.2.1/build. dkelly@Opus {1052}
Responsible Changed From-To: freebsd-ports-bugs->joerg Over to maintainer.
How could you possibly get away with starting the build at all? pdflatex is part of teTeX, and teTeX is properly listed as a prerequisite for the port (BUILD_DEPENDS). Perhaps I should change the check for teTeX from "latex" to "pdflatex"? Is there any other package that would possibly install a "latex" command these days? Hmm, teTeX conflicts with latex2e-*, so maybe you've got one of those installed? As for the portupgrade not noticing the build failure, we might pass the PR on to the portupgrade maintainer once the above has been clarified. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
On Feb 15, 2005, at 3:46 AM, Joerg Wunsch wrote: > How could you possibly get away with starting the build at all? Surprised me too. Ran portupgrade on one machine and saw success along with a new avr-libc but didn't try to use that avr-libc for a while until after running portupgrade on another machine and found avr-libc was broken. > pdflatex is part of teTeX, and teTeX is properly listed as a > prerequisite for the port (BUILD_DEPENDS). I think latex and family are in a state of disarray on FreeBSD at the moment. Removed doxygen and now rebuild of doxygen breaks on latex. > Perhaps I should change the check for teTeX from "latex" to > "pdflatex"? Is there any other package that would possibly install a > "latex" command these days? Hmm, teTeX conflicts with latex2e-*, so > maybe you've got one of those installed? > > As for the portupgrade not noticing the build failure, we might pass > the PR on to the portupgrade maintainer once the above has been > clarified. I think that is a key component of my initial problem which prompted opening this PR. Having run cvsupdate a time or two since I can no longer reproduce the portupgrade no-error where there really was an error situation. So it seems to have cleared up. Using "-DNOPORTDOCS" gets my avr-libc binaries and include files back into operational condition. -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad.
Responsible Changed From-To: joerg->knu I've made the avr-libc port depend on pdflatex as well as on latex now, to make absolutely sure both are installed. Over to the maintainer of portupgrade, so he can analyze why portupgrade didn't detect the build failure.
Responsible Changed From-To: knu->daichi Over to new maintainer of sysutils/portupgrade.
State Changed From-To: open->feedback Over to new maintainer.
Lets close this as whatever was happening before is no longer a problem with current versions.
State Changed From-To: feedback->closed Submitter request. Thanks!