| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
2018-07-13 lang/gcc47: Unsupported by upstream. Use GCC 6 or newer instead.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
"ldconfig -m <path>" so the order of ldconfig search directories after
package installation is the same as after a reboot. The original command
simply appends the path to the list of directories while the ldconfig rc.d
script uses "sort -u".
Bump lang/gcc* which are known to install libraries with exactly the same
name so the library loaded at runtime depends on the order of the search
directories.
PR: 228046
Approved by: portmgr (antoine)
|
|
|
|
|
| |
have been maintained upstream for more than three years by then. It also
is not used anywhere in the FreeBSD Ports tree.
|
|
|
|
|
|
|
| |
(gcc47, gcc48, gcc49, and gcc5), taking advantage of the default for GCC
releases provided by MASTER_SITES_ABBREVS.
Reported by: portlint
|
| |
|
|
|
|
| |
version 1.1.0 (via revision 464079).
|
|
|
|
|
|
|
|
|
|
| |
info is removed) from lang/gcc7 to lang/gcc47, lang/gcc48 and lang/gcc49.
(For more background see revisions 454177 and 454422.)
Reported by: Ports QA Framework, miwi, sobomax
Discussed with: tijl, miwi
Differential Revision: https://reviews.freebsd.org/D10357
|
|
|
|
|
| |
instead of GCC 5 or later in the deprecation messages for lang/gcc46
to lang/gcc49.
|
|
|
|
|
|
|
|
| |
but no expiration date at this point (since at least the latter two
still have users in the ports tree and sparc64 relies on the latter).
PR: 222373
Submitted by: Yasuhiro KIMURA <yasu@utahime.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Move ONLY_FOR_ARCHS into the right position of the Makefile.
- Omit a comment describing GCC_VERSION and SUFFIX.
- Do not quote constant strings compared with ${ARCH}. [1]
- Last, but not least the only functional change (and an important one
at that): Remove headers being created by GCC's fixincludes machinery
from the installation / packaging to avoid breakage when FreeBSD's
headers are changing afterwards.
- On the way, add a TIMESTAMP to distinfo.
PR: 221905 [1]
Submitted by: linimon [1]
|
|
|
|
|
|
| |
from the end-of-life lang/gcc4* ports.
PR: 219274
|
|
|
|
| |
for all lang/gcc4* ports.
|
|
|
|
|
|
|
|
| |
This is an old version of GCC (a couple of generations end-of-lifed)
that is not going to be fixed realistically, and we have newer ports
that work.
Discussed with: linimon, andreast
|
|
|
|
|
|
|
|
|
| |
was a stub, provide a real one.
While here, pet portlint.
Approved by: portmgr (tier-2 blanket)
Reported by: swills
|
|
|
|
|
|
|
| |
Changes: http://savannah.gnu.org/forum/forum.php?forum_id=8679
Differential Revision: https://reviews.freebsd.org/D
PR: 218972
Exp-run by: antoine
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
it as well as java from CATEGORIES) from this port.
After GCC 4.7 went end-of-life upstream in June 2014 there isn't much
use of that not better served by newer lang/gcc* ports and it speeds up
the build and simplifies this port significantly.
In addition to the expected changes to Makefile, pkg-plist, and pkg-descr,
this also removes files/java-patch-hier.
|
|
|
|
| |
Approved by: gerald (maintainer via mail)
|
|
|
|
|
|
|
| |
438272 to avoid DISTVERSION in this port .
On the way also drop the definition of DISTNAME and simplify the
definition of GCC_VERSION since GCC 4.7 is EOL.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are two cases:
- The upstream versionning is compatible with our versionning, or using
DISTVERSION's magic leads to a compatible PORTVERSION, use
DISTVERSION. If it is possible to use DISTVERSIONPREFIX and
DISTVERSIONSUFFIX to make it compatible, use them.
- The upstream versionning is not compatible with our versionning, and
DISTVERSION's magic does not lead to a correct PORTVERSION, then set
PORTVERSION to the equivalent of our versionning, and set DISTNAME.
It is possible to use a third variable where you store upstream's
version and use it to compute PORTVERSION and/or DISTNAME, like the
dns/bind9* ports do.
Sponsored by: Absolight
|
|
|
|
|
|
|
| |
PR: 213570
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
|
|
|
|
|
|
|
|
| |
of GCC including lang/gcc:
Only override CONFIGURE_TARGET for amd64 which is x86-64/x86_64 for the
rest of the world including GNU and GCC. For all other architectures
it already defaults to the value we were setting.
|
|
|
|
| |
some 20 months ago).
|
|
|
|
|
|
|
| |
PR: 208294, 208309
Exp-run by: antoine
Approved by: gerald (maintainer)
Differential Revision: https://reviews.freebsd.org/D4157
|
|
|
|
|
| |
With hat: portmgr
Sponsored by: Absolight
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
UNIQUENAME was never unique, it was only used by USE_LDCONFIG and now,
we won't have conflicts there.
Use PKGBASE instead of LATEST_LINK in PKGLATESTFILE, the *only* consumer
is pkg-devel, and it works just fine without LATEST_LINK as pkg-devel
has the correct PKGNAME anyway.
Now that UNIQUENAME is gone, OPTIONSFILE is too. (it's been called
OPTIONS_FILE now.)
Reviewed by: antoine, bapt
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D3336
|
|
|
|
| |
Suggested by: mat
|
|
|
|
|
|
|
|
|
|
|
|
| |
The JAVA frontend doesn't build on DragonFly on any release. The new
OPTIONS_EXCLUDE_${OPSYS} feature is a nice way to avoid the use of
Makefile.DragonFly (most are in dports, but one is in lang/gcc5).
The recent addition of CXXFLAGS to lang/gcc5 prevents Makefile.DragonFly
on lang/gcc5 from being removed outright. There are a couple of options
available to allow its removal, but I'll need to discuss with Gerald.
Approved by: DragonFly blanket
|
|
|
|
|
|
|
|
|
| |
This was causing the gcc packages to be generated with a
/usr/local/libdata/ldconfig/gcc file. All were conflicting. Bump
PORTREVISION to fix packages built during this time.
With hat: portmgr
Reported by: sunpoet
|
|
|
|
|
|
|
|
|
| |
Use PKGNAMESUFFIX so that PORTNAME falls back to plain gcc and we
can avoid setting DISTNAME and CPE_PRODUCT. [2]
PR: 198256 [1]
Submitted by: shun.fbsd.pr@dropcut.net [1]
Suggested by: mat [2]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
script to assume the BUILD_CONFIG is set to bootstrap-debug, instead of
letting it auto-detect.
With clang 3.5.0 this auto-detection can fail, due to a discrepancy [1]
[2] in its debug information, when objects are produced with and without
-g. When the auto-detection fails, gcc will compare objects with full
debug information during the stage comparisons, and this sometimes
causes those stage comparisons to fail unexpectedly.
[1] http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20141222/250134.html
[2] http://llvm.org/PR22046
Approved by: gerald (maintainer)
|
|
|
|
| |
generated parts via the Makefile.
|
|
|
|
|
|
| |
indexinfo is taking care of generating it at package installation time
Reported by: peter
|
| |
|
|
|
|
| |
TARGLIB.
|
|
|
|
| |
With hat: portmgr
|
|
|
|
|
|
|
| |
Please note that lots of invocation of MAKE_CMD here are wrong as they do not
properly respect MAKE_ENV and friends
With hat: portmgr
|
|
|
|
|
|
|
| |
Due to the way we have been handling PORTREVISION before lang/gcc48 this
requires PORTEPOCH.
Also, since this is now final and stable, no longer bootstrap this port.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since FreeBSD 8.4 and FreeBSD 9.1 make(1) do support :tu and :tl as a
replacement for :U and :L (which has been marked as deprecated)
bmake which is the default on FreeBSD 10+ only support by default
:tu/:tl a hack has been added at the time to support :U and :L to ease
migration. This hack is now not necessary anymore
Note that this makes the ports tree incompatible with make(1) from
FreeBSD 8.3 or earlier
With hat: portmgr
|
|
|
|
|
|
| |
Add pkg-message that references the need to use -Wl,-rpath=... . [1]
PR: 185902 [1]
|
|
|
|
| |
Extend full-regression-test by running contrib/test_summary.
|
|
|
|
|
|
| |
uncompressed version since post-install runs before compress-man.
Submitted by: mat
|
|
|
|
|
| |
No longer install rebuild-gcj-db47 (which requires bash among others)
and its man page.
|
|
|
|
| |
Replace USE_BZIP2 by USES=tar:bzip2.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GCC 4.6.4 to GCC 4.7.3. This entails updating the lang/gcc port as
well as changing the default in Mk/bsd.default-versions.mk.
This adds powerpc64 as a supported architecture (and removes ia64,
though it can be supported by manually installing lang/gcc48).
New binaries %%GNU_HOST%%-gcc-ar47, %%GNU_HOST%%-gcc-nm47, and
%%GNU_HOST%%-gcc-ranlib47 are provided to support link-time
optimization (LTO) which scales significantly better.
And it adds support for indirect functions (IFUNCS), experimental
support for transactional memory in the compiler as well as a supporting
run-time library called libitm, a new string length optimization pass,
and support for atomic operations specifying the C++11/C11 memory model.
Version 3.1 of the OpenMP specification is now supported for the C,
C++, and Fortran compilers.
GCC accepts the options -std=c11 and -std=gnu11 for the C11 revision
of the ISO C standard which inlcude support for unicode strings,
nonreturning functions (_Noreturn and <stdnoreturn.h>), alignment
support (_Alignas, _Alignof, max_align_t, <stdalign.h>), and a
__builtin_complex built-in function.
The C++ frontend now accepts the -std=c++11, -std=gnu++11, and
-Wc++11-compat options and implements many C++11 features of the
language including extended friends syntax, explicit override
control, non-static data member initializers, user-defined literals,
alias declarations, delegating constructors, atomic classes, and more.
The C++ standard library and Fortran frontend have received many
improvements. See http://gcc.gnu.org/gcc-4.7/changes.html for an
extense list of changes; http://gcc.gnu.org/gcc-4.7/porting_to.html
for information on how to port to that new version.
PR: 182136
Supported by: Christoph Moench-Tegeder <cmt@burggraben.net> (fixing many ports)
Tested by: bdrewery (two -exp runs)
|
| |
|
|
|
|
|
| |
Set the license to a combination of GPLv3 (for the compiler itself) and
GPLv3 with GCC Runtime Library Exception (for the runtime).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Configure with --enable-gnu-indirect-function to enable the "ifunc"
attribute, a GCC extension. [1]
Remove the man7 pages, which we are not packaging, from the staging
area to silence some warnings some are concerned about. [2]
No longer run ccache-update-links as part of post-install which, in
the world of staging, no longer is what it used to be. Rely on the
existing @exec and @unexec in pkg-plist instead. [3]
Submitted by: jmg [1], miwi [2]
Discussed with: kib [1], antoine [2][3]
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
No longer add -I${LOCALBASE}/include to CFLAGS.
Since we now configure with --with-gmp=${LOCALBASE} this is no longer
necessary, and due to bugs in binutils (which should not install ansidecl.h
into ${PREFIX}/include) and GCC (which should search its own include
directories with higher priority) can lead to build failures.
|
|
|
|
|
|
|
| |
port and avoid a package name collision with other GCC ports. This
also allows us to remove LATEST_LINK.
On the way update to the 20131123 snapshot of GCC 4.7.4.
|
|
|
|
| |
Reported by: portscout
|
|
|
|
|
|
|
|
|
|
| |
Remove a (long) obsolete dependency on bison. [1]
Migrate to the new LIB_DEPENDS standard.
STAGEify.
Reported by: marino [1]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Switched to automake 1.11.6, see CVE-2012-3386.
- #14669: Fixed extraction of CC from gmp.h.
- Fixed case of intermediate zero real or imaginary part in mpc_fma,
found by hydra with GMP_CHECK_RANDOMIZE=1346362345.
This is on top of the following changes from version 1.0
- Licence change towards LGPLv3+ for the code and GFDLv1.3+ (with no
invariant sections) for the documentation.
- 100% of all lines are covered by tests
- Renamed functions
. mpc_mul_2exp to mpc_mul_2ui
. mpc_div_2exp to mpc_div_2ui
- 0^0, which returned (NaN,NaN) previously, now returns (1,+0).
- Removed compatibility with K&R compilers, which was untestable due
to lack of such compilers.
- New functions
. mpc_log10
. mpc_mul_2si, mpc_div_2si
- Speed-ups
. mpc_fma
- Bug fixes
. mpc_div and mpc_norm now return a value indicating the effective
rounding direction, as the other functions.
. mpc_mul, mpc_sqr and mpc_norm now return correct results even if
there are over- or underflows during the computation.
. mpc_asin, mpc_proj, mpc_sqr: Wrong result when input variable has
infinite part and equals output variable is corrected.
. mpc_fr_sub: Wrong return value for imaginary part is corrected.
Convert to the new LIB_DEPENDS standard and remove hard-coded
.so versions from a couple of dependent ports.
Bump PORTREVISIONS of all dependent ports.
PR: 183141
Approved by: portmgr (bdrewery)
|
|
|
|
| |
lang)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on FreeBSD 10, and amd64 on earlier versions.
SSP_UNSAFE is added to disable in a port if it fails to build, but
this should only be used in rare circumstances such as kernel modules.
Otherwise, the port may just be failing due to lack of respecting
LDFLAGS.
On FreeBSD 10, this uses an ldscript in /usr/lib/libc.so to pull in
libssp_nonshared.a to address issues linking on i386 [1].
On earlier FreeBSD versions the WITH_SSP knob will add -lssp_nonshared
to LDFLAGS on i386. This is not needed on amd64. However, several hundred
ports do not currently respect LDFLAGS, so this support is disabled currently
as it causes build failures if a dependency is looking for the stack_chk
symbols.
Many thanks to jlh@ for this as he had many years of patience in getting
all of the necessary pieces [1][2] in.
[1] http://svnweb.freebsd.org/base/head/lib/libc/libc.ldscript?revision=251668&view=markup
PR: ports/138228 [2]
Submitted by: jlh (bsd.ssp.mk based on)
Reviewed by: bapt
With hat: portmgr
exp-runs done: 37 over a month on 91i386,91amd64,10i386,10amd64
|
|
|
|
| |
Convert from USE_GMAKE to USES=gmake
|
|
|
|
|
|
|
|
| |
Instead of hardcoding the compiler target as FreeBSD, use the OPSYS
variable to it. This makes no practical difference for FreeBSD, but
it helps DragonFly get properly configured.
Approved by: gerald
|
|
|
|
|
|
|
|
| |
It's value is "--with-libiconv-prefix=/usr/local" for systems
before 100043 with ports libiconv and to use at systems post
100043 with base iconv it's value is "" (NULL).
Co-authors: bapt, madpilot and bsam (me)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Work around a bug in libcpp that pulls in the optional system iconv
if present instead of relying on the port we actually depend on. [1]
The issue is that /usr/include/iconv.h has #include <stdbool.h> which
in turn, since both are included very late in the game, conflicts with
similar definintions by libcpp itself.
Interestingly enough, lang/gcc46 and lang/gcc48 did not fail under the
same test scenarios and libstdc++ does not seem to require adjustments,
so PR 161417 may not be relevant in full.
PR: 161417 [1]
|
|
|
|
| |
Update to the 20130817 snapshot of GCC 4.7.4.
|
|
|
|
| |
Approved by: portmgr (bdrewery)
|
|
|
|
|
|
|
|
|
| |
Rename VERSIONSTRING to the standard DISTVERSION. [1]
Add more notes on the various variables carrying version information.
Suggested by: crees [1]
~
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Introduce a new option BOOTSTRAP that allows switching between a
full bootstrap of GCC and just running a simple build.
Bootstrapping is the default upstream, and for very stable and old
flavors of GCC we disable this by default since that is a huge win
in terms of build time of the port. No change in default behavior
for this port, for the time being we continue to bootstrap.
|
|
|
|
|
|
| |
- Change USE_GNOME=pkgconfig|gnomehack to USES=pathfix|pkgconfig while here
Reviewed by: zeising
|
|
|
|
|
|
| |
those fixes in the GCC 4.7.3 release.
Feature safe: yes
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It brings bison as a build dependency in case it is set the following way:
USES= bison or USES= bison:build
it brings bison as a run dependency in case it is set the following way:
USES= bison:run
it brings bison both as a run and build dependency in case it the set the following way:
USES= bison:both
While here trim some headers
Convert some USE_GNOME= gnomehack to USES= pathfix
|
|
|
|
| |
build with texinfo 5.0 more or less.
|
|
|
|
|
|
| |
one in all cases.
On the way, update to the 20130216 snapshot of GCC 4.7.3.
|
| |
|
|
|
|
| |
Reported by: Paul Reynold <preynold@redcom.com>
|
|
|
|
|
|
|
|
|
| |
instead of including a pre-built version of the Eclipse Java Compiler
(ECJ) ourselves. [1]
On the way, update to the 20130119 snapshot of GCC 4.7.3.
PR: 175072 [1]
|
| |
|
|
|
|
|
|
|
|
| |
Without this, the libiberty build fails locating ar.
Also update to the 20121124 snapshot of 4.7.3.
Feature safe: yes
|
|
|
|
| |
Feature safe: yes
|
|
|
|
| |
Feature safe: yes
|
|
|
|
|
|
|
| |
Update to the 20121013 snapshot of GCC 4.7.3.
Submitted by: jkim [1]
Feature safe: yes
|
|
|
|
|
|
|
|
|
|
| |
On the way rename %%GCC_VER%% in pkg-plist to %%GCC_VERSION%% and
make the Makefile machinery a bit more generic to minimize differences
between lang/gcc ports based on releases and those based on snapshots.
On the way, update to the 20120929 snapshot of GCC 4.7.3.
Submitted by: jkim [1]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to the GCC 4.7.2 release. It also fixes an ABI problem introduced
with earlier GCC 4.7 releases.
Cut down the comments at the top of Makefile per recent guidance.
Revamp the handling of different languages (frontends, run-times)
by GCC to allow for orthogonal setting them in the future. [1]
Print the list of languages being built as part of pre-everything
and shorten the output of operating system and version there.
Inspired by: jkim [1]
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
On the way update to the 20120728 snapshot of GCC 4.7.2.
|
|
|
|
| |
Remove ABI version numbers for all library dependencies.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
release.
Fix a portlint warning (tab vs space).
|
|
|
|
| |
Approved by: gerald
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Feature safe: yes
|
|
|
|
| |
Feature safe: yes
|
| |
|
| |
|
|
|
|
| |
-fstack-protector-all on FreeBSD (thanks to tijl).
|
|
|
|
|
| |
This fixes a bootstrap comparison failure rearing its ugly head in
some cases, plus GNU/kFreeBSD.
|
|
|
|
| |
front end and accordingly also the run-time.
|
| |
|
| |
|
| |
|
|
|
|
| |
Feature safe: yes
|
|
|
|
|
|
|
| |
incorrectly named library (libjavamath.so.0.0) introduced by the
fixes for FreeBSD 10 support.
Feature safe: yes
|
|
|
|
|
|
| |
FreeBSD 10 without problems and any additional tweaks.
Feature safe: yes
|
|
|
|
|
|
|
|
|
|
| |
for transactional memory on i386, amd64 and alpha.
We handle the corresponding info file inclusively by listing all
supported architecture and move the libquadmath info file to the
same schema.
Feature safe: yes
|
|
|
|
|
|
| |
now developer, only a sole user, ever cared for the last many years.
Feature safe: yes
|
|
|
|
|
|
| |
a hack of mine for libgcc on ia64.
Feature safe: yes
|
|
|
|
| |
This adds new programs gcc-ar47, gcc-nm47, and gcc-ranlib47.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
On the way update ccache links (when appropriate) when installing
and deinstalling this port/package. [1]
PR: 155568 [1]
Submitted by: ehaupt [1]
|
|
|
|
|
|
|
| |
the newer version of binutils that we are using).
Remove a patch for ia64 that was not accepted upstream and where the are
in question was restructured recently.
|
| |
|
|
|
|
| |
issues on ia64.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
a single tarball and this update brings a number of changes around that.
Enable c, c++, and fortran (and only these) explicitly by default, and
Java when/where available. [1]
Reported by: Scott Allendorf <scott-allendorf@uiowa.edu> [1]
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Replace the, now dysfunctional, post-patch target with a configure
option that marks this build of GCC as "FreeBSD Ports Collection". [1]
Reported by: Bjoern Koenig <bkoenig@alpha-tierchen.de> [1]
|
| |
|
| |
|
|
|
|
|
|
| |
On SPARC the target CPU type may now be set via -mcpu instead of being
limited to the hardcoded equivalent of -mcpu=ultrasparc and TLS support
is enabled if available.
|
|
|
|
| |
Submitted by: andreast
|
|
|
|
|
|
|
| |
the GCC 4.6 branch has been carved, thus quite similar to that. Over
the next months this will see a lot of active and partially invasive
development. Accordingly this port is for early exposure and not yet
production use.
|
|
|
|
|
|
| |
Make the full-regression-test target conditional on MAINTAINER_MODE. [1]
Reported by: andreast, marius [1]
|
|
|
|
|
| |
LTO option. This is now the default, without any drawbacks or extra
dependencies.
|
|
|
|
|
| |
on libelf when building with link-time optimization (LTO) support which
is not needed any more.
|
|
|
|
|
| |
generation on i386 to default to i486 on FreeBSD 6 and above is now
upstream, too, so we can shed our specific patch.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This addresses the pollution of common namespace by
share/python/aotcompile.py and share/python/classfile.py which are
now saved in version-specific directories.
By means of an extra patch default code generation on i386 now
defaults to i486 on FreeBSD 6 and above. [1]
Submitted by: tijl [1]
Reported by: Yuri Karaban <tech@askold.net> [1]
PR: 154364 [1]
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This addresses the pollution of common namespace by
share/python/aotcompile.py and share/python/classfile.py which now
go into version-specific directories.
By means of an extra patch default code generation on i386 defaults
to i486 on FreeBSD 6 and above. [1]
Submitted by: tijl [1]
Reported by: Yuri Karaban <tech@askold.net> [1]
PR: 154364 [1]
|
| |
|
|
|
|
| |
Reported by: Anton Shterenlikht <mexas@bristol.ac.uk>
|
|
|
|
|
|
|
|
| |
a long standing issue around libgcj that's been hitting us and allows
me to remove the stop gap I had put in place years ago. [1]
PR: 81788 [1]
Feature safe: yes
|
|
|
|
| |
Feature safe: yes
|
|
|
|
|
|
|
| |
improves GOMP support on FreeBSD with a patch of mine to resolve
linking issues.
Feature safe: yes
|
|
|
|
|
|
| |
Provide more background on the need to use --disable-rpath as a workaround.
Feature safe: yes
|
|
|
|
| |
Feature safe: yes
|
| |
|
|
|
|
|
| |
original pollution of include file namespace around libquadmath and
adds a GNU info file for libquadmath.
|
| |
|
|
|
|
|
|
| |
(better support for 128 bit floating point types, which for now poisons
global include file namespace though this won't be an issue before GCC
4.7 and I have reported it upstream).
|
| |
|
| |
|
|
|
|
| |
Look ma', no more MD5 distinfo.
|
|
|
|
| |
script which had allowed submitting bugs like send-pr in FreeBSD.
|
| |
|
| |
|
|
|
|
| |
Submitted by: bf
|
| |
|
| |
|
|
|
|
| |
architecture support on i386 thanks to a patch by tijl.
|
|
|
|
|
| |
FreeBSD/ia64 that I made upstream and together with another, which is a
local patch for now, ia64 can become part of ONLY_FOR_ARCHS.
|
|
|
|
| |
for _float128 on i386 and proper symbol versioning for libgcc.
|
|
|
|
|
|
|
|
|
|
|
|
| |
link-time optimization framework and optimizations. GCC 4.6 has been
seeing a lot of work since GCC 4.5, but we are still keeping this
disable by default for now
Using LTO adds libelf as a new dependency and in either case the
environment does not have an influence any more. Bumping PORTREVISION
since someone who had libelf on his system previously to this change
would get LTO enabled automatically and then run into problems if libelf
was removed.
|
| |
|
|
|
|
|
|
|
|
| |
work with the ancient version of GNU as that is part of FreeBSD 8.1 and
earlier (and likely later), so where the dependency this port has on
devel/binutils was a strong recommendation until now and necessary to
leverage new processor features and the -mtune=native option when running
on those newer processors, it is now strictly needed on x86-64 at least.
|
|
|
|
|
|
| |
Replace NOT_FOR_ARCHS by ONLY_FOR_ARCHS. [1]
Suggested by: linimon
|
| |
|
| |
|
|
|
|
| |
Feature safe: yes
|
|
|
|
| |
Feature safe: yes
|
|
|
|
| |
Feature safe: yes
|
|
|
|
|
|
|
| |
Make Java support an OPTION (JAVA) so it is easier to deselect. [1]
Suggested by: doubg [1]
Feature safe: yes
|
|
|
|
| |
Feature safe: yes
|
|
|
|
| |
Feature safe: yes
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Reported by: Eitan Adler <eitanadlerlist@gmail.com>
|
| |
|
|
|
|
|
| |
20100424 snapshot of GCC 4.6.0, which is a very, very early version of
said release which likely won't happen before 2011.
|
| |
|
|
|
|
|
|
| |
PR: ports/144487
Submitted by: ale
Approved by: portmgr (-exp run by erwin)
|
|
|
|
|
| |
official release of GCC 4.5.0, thought that one may still have some
kinks and I recommend staying with GCC 4.4 for production use.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Feature safe: yes
|
|
|
|
| |
Feature safe: yes
|
| |
|
| |
|
| |
|
|
|
|
| |
Submitted by: Andreas Tobler <andreast@fgznet.ch>
|
|
|
|
|
| |
Since we already require devel/binutils for the assembler, also enforce
use of the linker from there.
|
| |
|
|
|
|
|
|
|
| |
improvements to libffi (Java), especially on amd64.
Remove the WITH_JAVA_AWT knob which really has not been used a lot,
if at all.
|
|
|
|
| |
a bit differently.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
On the way, sort CONFIGURE_ARGS.
PR: 140995, 136607
|
|
|
|
|
| |
to build emulators/wine due to problems with debuginfo, but then this
is more of an experimental port than anything, so always use with care.
|
|
|
|
|
| |
now remove the check for a gcc295 binary that might cause build failure in
libgcj.
|
| |
|
|
|
|
|
|
|
|
| |
Minor style changes.
Adjust the ports description to the new style I am using for the various
gcc ports and remove an obsolete note on memory consumption when building
libgcj (the Java library).
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
dependency going forward; it will become mandatory in the next weeks
and for the final GCC 4.5.0 release.
|
| |
|
|
|
|
|
|
|
| |
more than half a GB of memory. Accordingly, we can now remove the build-
time test for that from pre-everything.
Feature safe: yes
|
|
|
|
| |
Feature safe: yes
|
|
|
|
| |
Feature safe: yes
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Reported by: QAT
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add hack for non-default LOCALBASE until the ports infrastructure has
been fixed. [1]
The new share/libstdc++/python/libstdcxx has now moved to a version
specific location based on an upstream report of mine.
And there are now three new ffi related man pages.
Dedicated to:
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Move the snapshot date from PORTREVISION to being a part of PORTVERSION
to allow for PORTREVISION bumps.
Simplify pre-everything and adjust PLIST_SUB accordingly.
Move VERSIONSTRING down to pacify portlint after all those years and
extract it from PORTVERSION, too.
|
| |
|
|
|
|
| |
CONFIGURE_SCRIPT more robust.
|
|
|
|
|
|
|
|
|
| |
Extract SUFFIX from PORTVERSION. Use SUFFIX for TARGLIB (and thus for
the library path used by this port). Also use SUFFIX for the libexec
directory instead of the full port version and flatten the directory
structure and simplify the logic along the way.
Tinder-tested by: itetcu@
|
|
|
|
|
| |
Reported by: pointyhat
Pointy hat to: ale
|
| |
|