After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.
Now texinfo is not in base on any of the supported version of FreeBSD
it is possible to proceed to this move and it is easier to do than
the manpage change.
Other benefit than consistency are less patching: all build tools but
cmake are expecting info files to be under share/info and cmake (patched here)
was having an exception for BSD so the patch makes FreeBSD case less
specific for them
Bump revision of all impacted ports
PR: 232907
exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D17816
- Use the version tag instead of commit hash when they're the same.
- Remove unnneeded variables.
- Simplify go- ports when possible.
- Various fixes.
Sponsored by: Absolight
- Update MAINTAINER to my @FreeBSD.org address
- Fix tcc-doc.html generation
- Remove CONFLICTS because TenDRA port was deprecated some time ago
- Use post-install-DOCS-on target
- Use post-install-EXAMPLES-on target
- Bump PORTREVISION
Reviewed by: amdmi3, junovitch (mentors)
Approved by: amdmi3, junovitch (mentors)
Differential Revision: D6314
- Add INFO macro and USES=makeinfo to make it also work on revent head
- Clean up Makefile
PR: 192137
Submitted by: Carlos Jacobo Puga Medina <cjpugmed@gmail.com> (maintainer)
fixes i made recently.
Add files/patch-z1-preproc which implements -include, -M and some
related preprocessing macros to improve portability
Bump portrevision accordingly
Should close PR/141185
Features:
* SMALL! You can compile and execute C code everywhere, for example on rescue
disks (about 100KB for x86 TCC executable, including C preprocessor,
C compiler, assembler and linker).
* FAST! tcc generates x86 code. No byte code overhead. Compile, assemble and
link several times faster than GCC.
* UNLIMITED! Any C dynamic library can be used directly. TCC is heading torward
full ISOC99 compliance. TCC can of course compile itself.
* SAFE! tcc includes an optional memory and bound checker. Bound checked code
can be mixed freely with standard code.
* Compile and execute C source directly. No linking or assembly necessary.
Full C preprocessor and GNU-like assembler included.
* C script supported : just add '#!/usr/local/bin/tcc -run' at the first line
of your C source, and execute it directly from the command line.
* With libtcc, you can use TCC as a backend for dynamic code generation.
WWW: http://bellard.org/tcc/
Tcc's features include:
* Small: You can compile and execute C code everywhere, for
example on rescue disks (about 100KB for x86 TCC executable,
including C preprocessor, C compiler, assembler and linker).
* Fast: tcc generates optimized x86 code. No byte code overhead.
Compile, assemble and link several times faster than GCC.
* Unlimited: Any C dynamic library can be used directly. TCC is
heading torward full ISOC99 compliance. TCC can of course compile
itself.
* Safe: tcc includes an optional memory and bound checker. Bound
checked code can be mixed freely with standard code.
* Compile and execute C source directly. No linking or assembly
necessary. Full C preprocessor and GNU-like assembler included.
* C script supported : just add '#!/usr/local/bin/tcc -run' at
the first line of your C source, and execute it directly from the
command line.
* With libtcc, you can use TCC as a backend for dynamic code
generation.
