v.2.0 no longer available, author force users to update to 2.1 with critical network fixes.
Reported by: QAT via pav
Approved by: portmgr (pav)
Feature safe: yes
/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.11 required by /usr/local/bin/hugin not found
which I just fixed by using an older GCC is because
hugin-2009.4.0/src/hugin1/hugin/cmake_install.cmake includes this code:
FILE(RPATH_REMOVE
FILE "$ENV{DESTDIR}${CMAKE_INSTALL_PREFIX}/bin/hugin")
which does remove the rpath setting -Wl,rpath=/usr/local/lib/gcc44 which was
injected by /usr/ports/Mk/bsd.gcc.mk and then /usr/lib/libstdc++.so.6 is
picked up instead of /usr/local/lib/gcc44/libstdc++.so.6
If we have to compile with GCC 4.4 some day, then we will have to
remove the above RPATH_REMOVE code from cmake files.
$ strings /usr/lib/libstdc++.so.6 |grep GLIBCXX
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_FORCE_NEW
$ strings /usr/local/lib/gcc44/libstdc++.so.6 |grep GLIBCXX
GLIBCXX_3.4
GLIBCXX_3.4.1
GLIBCXX_3.4.2
GLIBCXX_3.4.3
GLIBCXX_3.4.4
GLIBCXX_3.4.5
GLIBCXX_3.4.6
GLIBCXX_3.4.7
GLIBCXX_3.4.8
GLIBCXX_3.4.9
GLIBCXX_3.4.10
GLIBCXX_3.4.11
GLIBCXX_3.4.12
GLIBCXX_3.4.13
GLIBCXX_FORCE_NEW
GLIBCXX_DEBUG_MESSAGE_LENGTH
$
Feature safe: yes
The compilation is known to fail on 6.x with GCC 3.4, so
use non-standard GCC (4.4+) only on 6.x and older.
On 7.x and above use the base GCC instead of GCC 4.4+ because:
1. GCC 4.4+ is not needed anyway and
2. The hugin executable compiled on 8.0/gcc-4.4.4.20100216 fails to start:
/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.6: version GLIBCXX_3.4.11 required by /usr/local/bin/hugin not found
Reported by: Hannes Hauswedell <h2@fsfe.org>
Feature safe: yes
- Support for registry symbolic links.
- Many MSI fixes.
- Build process improvements.
- MSXML cleanups and fixes.
- A number of MSHTML improvements.
- Various bug fixes.
Feature safe: yes
Version: lbzip2-0.22
Focus: Minor bugfixes
Date: 18-Feb-2010
Changes: Building lbzip2 on Debian unstable discovered that the "lfs.sh" build
script, due to a typo, did not invoke the "getconf" utility in a
SUSv2-conformant way. This bug has been corrected.
Version: lbzip2-0.21
Focus: Minor bugfixes
Date: 17-Feb-2010
Changes: Code examination revealed that lbzip2-0.18 introduced a race between
the following two code paths: (1) the muxer thread displays an error
message when it encounters a write error, (2) the main thread, in
preparation to terminate the process, frees the output file name after
an INT or TERM signal is delivered to it. This bug had negligible
chance to occur, but it was fixed nonetheless.
Feature safe: yes
Takao Fonts are a community developed derivative of IPA
Fonts. The main purpose of this project is to secure the
possibility to maintain the fonts by the community.
Feature safe: yes
Use current GNU binutils from ports (devel/binutils) instead of the
system tools. The latter are half a decade old and fail to properly
support modern CPUs and their standard features such as SSE or AVX in
the case of AMD64/Intel64 which means that they even break when using
a simple -march=native. This helps address repeated user problems here
and there, also by establishing a consistent base if, for example, the
user has different flavors of as and ld in her path.
On the way, sort CONFIGURE_ARGS.
Feature safe: yes
options since they can't be used together. Also, if openal-soft is the
new version it should come first on the -o command line, and should be
the argument for the -r option.
Feature safe: yes
quoting from
http://lists.freebsd.org/pipermail/freebsd-openoffice/2009-December/004440.html
> OpenOffice.org community officially announced that
> "end-of-life" for version 2.x of its productivity suite
> http://www.openoffice.org/servlets/ReadMsg?list=announce&msgNo=407
> .
> For FreeBSD ports tree - my policy is -
> I'll remove ports/editors/openoffice.org-2-RC soon, and mark as IGNORE
> for ports/editors/openoffice.org-2/ in the near future.
>
> Please contact me (maho at FreeBSD.org - I'm a de facto maintainer of this port),
> if you want to maintain "ports/editors/openoffice.org-2" port.
> I expect you to fix build issues, security issues, etc by back porting.
Thanks for all who loves OpenOffice.org. Sayonara, soshite arigatou (good-bye
and thank you)...
Feature safe: yes
Necessary for the up-coming bwn driver. Marked NO_PACKAGE because we
can't redistribute the modified firmware.
Submitted by: Weongyo Jeong
Feature safe: yes
