| non port: devel/simulavr/files/patch-doc::Makefile.in |
|
CVSWeb
|
Number of commits found: 2 | |
Mon, 1 Aug 2005
|
[ 07:28 joerg ]
1.15 devel/simulavr/Makefile
1.3 devel/simulavr/files/patch-configure
1.1 devel/simulavr/files/patch-doc-texinfo.tex
1.2 devel/simulavr/files/patch-doc::Makefile.in
1.5 devel/simulavr/pkg-plist
Many thanks to hrs who kept track of my emergency call, and to
Benjamin Lutz whom he got to solve my latex PDF vs. DVI generation
problem, and who supplied a fix that makes simulavr's documentation
build again. That way, I could reenable the doc generation for the
port I just turned off about a day ago in order to unbreak the port.
Submitted by: Benjamin Lutz <benlutz@datacomm.ch>
|
|
Sat, 30 Jul 2005
|
[ 23:03 joerg ]
1.14 devel/simulavr/Makefile
1.3 devel/simulavr/distinfo
1.2 devel/simulavr/files/patch-configure
1.1 devel/simulavr/files/patch-doc::Makefile.in
1.2 devel/simulavr/files/patch-sim-no-vcd-inline
1.2 devel/simulavr/files/patch-src::avrcore.c
1.2 devel/simulavr/files/patch-test_asm
1.4 devel/simulavr/pkg-plist
Upgrade to a new source tarball that has all of our functional private
patches integrated.
I give up on trying to convince the doxygen setup of simulavr to
peacefully collaborate with LaTeX 3.x, it always ends up in producing
a PDF file where it is supposed to produce a DVI file (which the build
system then tries to process further). Instead, I hacked the
configure and build system to not try building or installing any of
its private documentation at all (the man and info pages are still
around as they are already present in the source tarball).
After all, the original simulavr is no longer being developed but has
a successor named simulavrxx, so in future, I'll rather concentrate on
making a FreeBSD port out of that one.
|
Number of commits found: 2 |
|
| Latest Vulnerabilities |
|
12 vulnerabilities affecting 16 ports have been reported in the past 14 days
|
* - modified, not new All vulnerabilities
|
|