| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
|
| |
|
|
| |
PR: 232162
|
| |
|
|
|
|
|
| |
via this meta-port.
PR: 232162
Submitted by: freebsd@mcwest.org
|
| |
|
|
| |
version 1.1.0 (via revision 464079).
|
| |
|
|
|
|
|
| |
this pulls in by default, still provides GCJ/libgcj (as the last GCC-based
port doing so), but unlike C, C++, or Fortran we do not create any symlink
for Java and users may also change the default version of GCC, so really
nothing Java-specific here.
|
| |
|
|
|
|
| |
the older versions, in particular 4.9 which is the last working on SPARC.
Reported by: linimon
|
| |
|
|
|
|
|
| |
the major version (so this does not result in a need for PORTEPOCH).
PR: 219275
Reported by: jbeich
|
| |
|
|
|
|
|
| |
default.
PR: 219275
Reported by: rakuco
|
| | |
|
| |
|
|
| |
Reported by: pkg-fallout, Matthew D. Fuller <fullermd@over-yonder.net>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
or less ended up identical to lang/gcc5 now that we differentiate between
lang/gccX-devel and lang/gccX ports, by (or as) a meta-port that pulls in
the respective lang/gccX port (based on the setting of $GCC_DEFAULT) and
defines gcc, g++, and gfortran as symlinks to the respective versioned
binaries.
This is the end of a long journey establishing this infrastructure
which is now similar to the one of the python ports, for example,
and makes upgrading the default as well as adjusting the default
locally a lot easier.
(PORTVERSION remains at 5.4.0 for now to avoid PORTEPOCH, but
PORTREVISION gets a bump.)
Suggested by: tijl (a while ago)
|
| |
|
|
| |
Approved by: gerald (maintainer via mail)
|
| |
|
|
|
|
|
|
| |
This define is already in upstream.
The gcc*-devel ports will pickup the commit from upstream.
Submitted by: kan@
Approved by: gerald@ (maintainer)
|
| |
|
|
|
|
| |
fix the armv6 bootstrap.
Reported by: andreast, jbeich
|
| |
|
|
|
|
| |
ICE on this architecture.
Reported by: andreast
|
| |
|
|
| |
Submitted by: andreast
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Collection (requested by USE_GCC=yes and various USES=compiler
invocations) from GCC 4.9.4 to GCC 5.4.
files/patch-arm-support and files/patch-gcc_system.h have become
obsolete. New patches files/patch-arm-unwind-cxx-support and
files/patch-libc++ help support arm targets and new libc++ in base.
ONLY_FOR_ARCHS now also includes arm.
A new option GRAPHITE_DESC, off by default for now, adds support for
Graphite loop optimizations.
Finally, conflicts with other lang/gcc* ports are adjusted suitably.
In terms of changes for users, this upgrade brings the following:
The default mode for C is now -std=gnu11 instead of -std=gnu89.
New warning options -Wc90-c99-compat and -Wc99-c11-compat may
prove useful on that front.
The C++ front end now has full C++14 language support including
C++14 variable templates, C++14 aggregates with non-static data
member initializers, C++14 extended constexpr, and more.
The Standard C++ Library (libstdc++) has full C++11 support and
experimental full C++14 support. It uses a new ABI by default.
There have been significant improvements to inter-procedural optimizations
and link-time optimization such as One Definition Rule based merging of C++
types as well as register allocation.
OpenMP 4.0 specification offloading features are now supported by the C,
C++, and Fortran compilers. Cilk Plus, an extension to the C and C++
languages to support data and task parallelism, has been added as well.
New warning options -Wswitch-bool, -Wlogical-not-parentheses,
-Wbool-compare and -Wsizeof-array-argument may prove useful as
may new preprocessor directives __has_include, __has_include_next,
and __has_attribute.
GCC can now be built as a shared library for embedding in other processes
(such as interpreters), suitable for Just-In-Time compilation to machine
code. This provides a C API and a C++ wrapper API.
Many code generation improvements for AArch64, ARM, support for
AVX-512{BW,DQ,VL,IFMA,VBMI} and Intel MPX on x86-64, and generally
improvements on many targets.
The Local Register Allocator (LRA) now contains a rematerialization
subpass and is able to reuse the PIC hard register on x86/x86-64 to
improve performance of position independent code.
https://gcc.gnu.org/gcc-5/changes.html has a more extensive set of
changes and https://gcc.gnu.org/gcc-5/porting_to.html has a solid
overview of issue you may encountering porting to this new version.
PR: 216707, 218125
Tested by: antoine (-exp runs)
Supported by: jbeich, tcberner, and others
|
| |
|
|
|
|
| |
an arch.
Reported by: andreast
|
| |
|
|
|
|
|
| |
Replace a shell for-loop with a bmake .for-loop on the way.
Reported by: danfe
Reviewed by: danfe
|
| |
|
|
|
|
|
|
| |
Remove an extraneous definition of DISTVERSION (which in general we
only need for ports tracking weekly GCC snapshots) and simplify the
definition of GCC_VERSION.
Reported by: andreast [1]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
locale set by the user. Add LANG=C and LC_ALL=C at the beginning of
bsd.port.mk and export them so all commands are executed with the C locale.
LC_ALL=C overrides all other LC_* variables. LANG is used by setlocale(3)
as default value for LC_* variables, so normally it isn't used when LC_ALL
is set, but there's code out there that looks at LANG directly so it's safer
to set it as well. The only commands not captured by this are !=
assignments before any inclusion of bsd.port.*mk.
Introduce USE_LOCALE=<locale> that adds LANG=<locale> and LC_ALL=<locale> to
CONFIGURE_ENV and MAKE_ENV so upstream build systems can be executed with a
different locale (e.g. USE_LOCALE=en_US.UTF-8).
PR: 215882
Exp-run by: antoine
Approved by: portmgr (antoine)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
and lang/gcc48, but is something we have in lang/gcc47 and that lang/gcc
carried over from the days it was about GCC 4.7 (so surviving both the
transitions to GCC 4.8 and recently GCC 4.9).
The underlying issue was addressed upstream 2014-10-24 with r216679,
and in FreeBSD head 2013-09-06 by theraven@ who fixed fixed our
iconv.h to not include stdbool.h.
PR: 161417
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While testing the clang390-import branch, I ran into the following
errors building lang/gcc49:
In file included from /wrkdirs/usr/ports/lang/gcc49/work/gcc-4.9.4/gcc/c/c-objc-common.c:33:
In file included from /usr/include/c++/v1/new:70:
/usr/include/c++/v1/exception:267:5: error: no member named 'fancy_abort' in namespace 'std::__1'; did you mean simply 'fancy_abort'?
_VSTD::abort();
^~~~~~~
/usr/include/c++/v1/__config:451:15: note: expanded from macro '_VSTD'
#define _VSTD std::_LIBCPP_NAMESPACE
^
/wrkdirs/usr/ports/lang/gcc49/work/gcc-4.9.4/gcc/system.h:685:13: note: 'fancy_abort' declared here
extern void fancy_abort (const char *, int, const char *) ATTRIBUTE_NORETURN;
^
1 error generated.
What is happening here, is that the source file includes gcc/system.h,
which defines abort to fancy_abort, and then the source file includes
<new>, which attempts to call _VSTD::abort() (the _VSTD is a libc++
alias for std::). The macro definition then causes the above breakage.
Newer gcc ports, such as gcc5 and gcc6 don't show this issue, because
upstream gcc first added an include of <algorithm> (which indirectly
includes <new>) in r217348 [1], and later even add a direct include of
<new> in r232736 [2].
Fix it for this version, by adding the direct include of <new> to
gcc/system.h. This makes the 'second' includes of <new> in some .c
files superfluous, but at least they won't result in errors.
[1] https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=217348
[2] https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=232736
Approved by: portmgr (antoine)
PR: 212465
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Collection as well as the lang/gcc port from GCC 4.8.5 to GCC 4.9.4!
See http://gcc.gnu.org/gcc-4.9/changes.html for an extensive list of
changes and http://gcc.gnu.org/gcc-4.9/porting_to.html for information
on how to port to that new version (if necessary).
files/java-patch-hier required adjustments, gcc/files/patch-arm-libcpp
is not needed any longer (merged upstream), and we're also loosing the
local Stack Protector patches/backports.
PR: 196712
Tested by: antoine (-exp runs)
Supported by: antoine, kwm, and others
|
| |
|
|
|
|
|
| |
PR: 213570
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
|
| |
|
|
| |
restoring OPTIONS_DEFAULT_powerpc64=BOOTSTRAP.
|
| |
|
|
| |
OPTIONS_DEFAULT.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
GCC can be mis-built, leading to an internal compiler error building
libgcc/libgcov.c, at least on FreeBSD 11.
Adjust OPTIONS_DEFINE_powerpc64 and OPTIONS_DEFAULT_powerpc64
incrementally (with +=) to avoid overwriting settings defined
at the top of the Makefile (or child ports). [1]
Submitted by: swills [1]
Reported by: swills
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
command-line options. According to POSIX, string comparisons (and
hence sorting) are to be performed based on the locale's collating
order. Alas GNU AWK only does so in POSIX mode, whereas starting
with FreeBSD 11 we do so by default, running into a bug (or false
assumption) with that script used by GCC.
Setting MAKE_ARGS such that AWK is always invoked in the C locale
works around this bug.
PR: 210122, 211742
Submitted by: jkim
|
| |
|
|
| |
Discussed with: gerald@
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
and lang/gcc48 ports, now in line across all lang/gcc* ports.
|
| |
|
|
|
|
|
| |
PR: 208294, 208309
Exp-run by: antoine
Approved by: gerald (maintainer)
Differential Revision: https://reviews.freebsd.org/D4157
|
| |
|
|
|
| |
With hat: portmgr
Sponsored by: Absolight
|
| |
|
|
|
|
|
|
|
|
| |
to the versioned executable (gfortran48, gcc48, and g++48).
These standard names are going to remain in place in case of version
upgrades and constitute the default, and expected by users, names.
Suggested by: db
Reviewed by: db
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change is the same as r400632, which updated gcc[56]-devel, but now
for gcc{,48,49,5}. This change is the second attempt at doing this: the
first attempt went in r401072 and was reverted in r401074 because the diff
was bogus and enabled the new MULTILIB option under all platforms instead
of just powerpc64.
This fixes the build of gcc{,48,49,5} under powerpc64 when the system
is built without the lib32 libraries.
More in detail:
If the system is built with lib32 support (WITH_LIB32, which is the default),
building gcc from ports results in a compiler that can target both 64-bit and
32-bit binaries on powerpc64. However, when lib32 support is disabled
(WITHOUT_LIB32), gcc should only be built with 64-bit support or otherwise
the build fails.
To fix this, explicitly disable 32-bit support when /usr/lib32 is not present
and add a MULTILIB option (which is only defined for powerpc64 when 32-bit
support is possible and defaults to yes to preserve the current behavior) to
allow the user to explicitly control this feature.
Approved by: gerald (maintainer), bdrewery (mentor), andreast
Differential Revision: https://reviews.freebsd.org/D3952
|
| |
|
|
|
|
|
| |
lang/gcc.
PR: 203751, 186852 [1]
Submitted by: software-freebsd@interfasys.ch [1]
|
| |
|
|
|
|
|
|
| |
I'm not sure what happened exactly but I think I committed the change from
the wrong client. The applied change enabled the MULTILIB option for all
architectures and not only powerpc64. Let's just revert the commit and do
it properly from scratch; other things might be wrong so I wanna take a
closer look, and it's best to just revert quickly.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change is the same as r400632, which updated gcc[56]-devel, but now
for gcc{,48,49,5}. Waited a week to ensure the change caused nothing to go
horribly wrong but this change is very low risk because it only affects
powerpc64.
This fixes the build of gcc{,48,49,5} under powerpc64 when the system
is built without the lib32 libraries.
More in detail:
If the system is built with lib32 support (WITH_LIB32, which is the default),
building gcc from ports results in a compiler that can target both 64-bit and
32-bit binaries on powerpc64. However, when lib32 support is disabled
(WITHOUT_LIB32), gcc should only be built with 64-bit support or otherwise
the build fails.
To fix this, explicitly disable 32-bit support when /usr/lib32 is not present
and add a MULTILIB option (which is only defined for powerpc64 when 32-bit
support is possible and defaults to yes to preserve the current behavior) to
allow the user to explicitly control this feature.
Approved by: gerald (maintainer), bdrewery (mentor), andreast
Differential Revision: https://reviews.freebsd.org/D3952
|
| |
|
|
| |
PR: 203540
|
| | |
|
| | |
|
| |
|
|
| |
Suggested by: mat
|
| |
|
|
| |
version
|
| |
|
|
|
|
|
|
|
| |
While the feature has a great value, it is right now breaking the build of
lang/gcc. Given the importance of lang/gcc it is better to revert now and
reapply the patch once it has been fixed and passes an exp-run on all supported
version
With hat: portmgr
|
| |
|
|
|
|
|
|
|
|
|
| |
Upstream gcc 4.8 doesn't have support for this - it'll create threads,
but it won't do any of the thread affinity stuff for FreeBSD.
This allows for OMP_PROC_BIND=true to bind threads to their initial
CPUs, leading to some pretty drastic improvements in performance
for certain NUMA workloads.
Approved by: gerald
|
| | |
|
| |
|
|
|
|
| |
Adjust lang/gcc as was done for gcc46+
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
|
| |
|
|
|
| |
PR: 198249
Submitted by: shun.fbsd.pr@dropcut.net
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
The larger part of the patch is a backport from gcc trunk which is sent
upstream for approval.
Thanks to Sean Bruno for testing, Andrew Turner for explaining me fine details
and Gerald for approving.
Approved by: gerald (maintainer)
|
| |
|
|
|
|
| |
This fixes (at least) 87 bugs reported, cf.
https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.8.4
for the full list. No new features.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
|
| |
are added dynamically via the Makefile.
|
| |
|
|
|
|
| |
indexinfo is taking care of generating it at package installation time
Reported by: peter
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to GCC 4.8.3.
This entails updating the lang/gcc port as well as changing the default
in Mk/bsd.default-versions.mk, and it replaces the CONFLICT between the
lang/gcc and lang/gcc47 ports by lang/gcc48.
GCC now uses C++ as its implementation language and performs more
aggressive loop analysis which can be disabled via the
-fno-aggressive-loop-optimizations command-line option.
Compilation of extremely large functions has been signficantly improved,
as have interprocedural optimizations.
A new optimization level -Og has been introduced. It addresses the need
for fast compilation and a superior debugging experience while providing
a reasonable level of run-time performance. This should be better
suitable for development than the default -O0.
A new local register allocator (LRA) has been implemented, which replaces
the 26 year old reload pass and improves generated code quality. For now
it is active on the x86 and x86-64 targets.
AddressSanitizer, a fast memory error detector, has been added and can be
enabled via -fsanitize=address.
Each diagnostic emitted now includes the original source line and a caret
indicating the column.
The new option -Wpedantic is an alias for -pedantic, which is now deprecated.
The C++ frontend and associated run-time library libstdc++ have gained
support for many additional C++11 features. As with previous releases
the Fortrand frontend has seen many improvements as well.
Support for the AArch64 has been added, and there are many improvements
to the x86/x86-64 backend and others.
See http://gcc.gnu.org/gcc-4.8/changes.html for an extense list of changes;
http://gcc.gnu.org/gcc-4.8/porting_to.html for information on how to port
to that new version.
PR: 192025
Tested by: antoine (-exp runs)
|
| |
|
|
|
|
|
|
|
| |
series that closes this branch.
Extend full-regression-test by running contrib/test_summary.
Also clean *.la files in LIBEXEC, and recursively so, there and for
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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]
- Replace USE_BZIP2 by USES=tar:bzip2.
- No longer install rebuild-gcj-db47 (which requires bash among others)
and its man page.
Bump PORTREVISION.
PR: 185902 [1]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
|
| |
GPLv3 with GCC Runtime Library Exception (for the runtime).
|
| |
|
|
|
|
|
|
|
|
|
| |
area to silence some warnings some are concerned about. [1]
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. [2]
Submitted by: miwi [1]
Discussed with: antoine [1][2]
|
| |
|
|
|
|
|
|
|
|
| |
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, fixed with revision 336642 [1]) and GCC (which
should search its own include directories with higher priority) could
lead to build failures.
PR: 184327 [1]
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
the staging infrastructure and had us remove info/gcc46 ourselves. [1]
This has now been addressed in the general infrastructure and actually
causes warnings in some cases. [2]
PR: 184178 [1]
Reported by: amdmi3 [2]
|
| |
|
|
|
|
|
|
| |
name of this port and avoid a package name collision with other GCC
ports. This also allows us to remove LATEST_LINK.
And it finally allows for a simple and proper CONFLICTS between
lang/gcc and lang/gcc46.
|
| |
|
|
|
|
|
| |
remove info/gcc46 ourselves.
Reported by: QAT, amdmi3, mandree, bf, dbn
PR: 184178
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
with new versions of texinfo. [1]
Adopt the new LIB_DEPENDS standard and replace USE_GMAKE by USES=gmake.
Remove an obsolete dependency on bison. [2]
STAGEify.
PR: 183342 [1]
Reported by: Christoph Moench-Tegeder <cmt@burggraben.net> [1], marino [2]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
if present instead of relying on the port we actually depend on.
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.
libstdc++ does not seem to require adjustments, so PR 161417 may not
be relevant in full.
PR: 161417
|
| |
|
|
|
|
|
|
| |
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)
|
| |
|
|
| |
Replace USE_GMAKE by USES=gmake.
|
| |
|
|
| |
Approved by: portmgr (bdrewery)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
bootstrap of GCC, as opposed to just running a simple build.
Bootstrapping is actually the default upstream, we disable it
by default for the stable flavors of GCC since that is a huge
win in terms of build time of the port. No change in default
behavior for this port.
(When bootstrapping, use bootstrap-lean instead of default/vanilla
bootstrap to save on disk space.)
Remove redundant setting of DISTNAME.
|
| |
|
|
|
|
| |
- Change USE_GNOME=pkgconfig|gnomehack to USES=pathfix|pkgconfig while here
Reviewed by: zeising
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
| |
instead of including a pre-built version of the Eclipse Java Compiler
(ECJ) ourselves. [1]
Replace the use of DISTFILES by DISTNAME, since we are now down to
one in all cases.
Make binutils a build dependency as well (not just a run-time dependency).
PR: 175072 [1]
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
architectures where the library is not supported. [1]
Revamp the handling of different languages (frontends, run-times)
by GCC to allow for orthogonal setting them in the future. [2]
Print the list of languages being built as part of pre-everything
and shorten the output of operating system and version there.
Reported by: linimon [1]
Inspired by: jkim [2]
Feature safe: yes
|
| |
|
|
| |
Remove now deprecated comments at the top of Makefile.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
in our ports tree. This speeds up a full port/package test cycle
by 31% on a 4-core system; a simple build/install will benefit even
more.
(This may impact compile time by this compiler a bit, depending on
how well the system compiler optimizes this codebase. And we only
should do this for stable, established versions of GCC.)
Remove ABI version numbers for all library dependencies.
|
| |
|
|
|
|
| |
and later out of the box, no more extra patches necessary.
Feature safe: yes
|
| |
|
|
| |
Tested by: avg, kargl
|
| |
|
|
| |
Feature safe: yes
|
| |
|
|
|
|
|
|
| |
across the board, cf.
http://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&resolution=FIXED&target_milestone=4.6.
for details.
Feature safe: yes
|
| |
|
|
| |
Discussed with: erwin
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of GCC (usually an upstream release). It starts out as GCC 4.6.1 and
is thus in conflict with lang/gcc46 and will move towards later minor
versions of GCC 4.6 and then on to GCC 4.7.
lang/gcc will provide gcc46, g++46, gfortran46 etc. exactly like
lang/gcc46 with which it is interchangible.
This is also planned to be in sync with our existing USE_FORTRAN knob
so that users have the option of using this port, rarely updated, or
the corresponding lang/gcc46 which follows weekly upstream snapshots.
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.
PR: 156857
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
installation and deinstallation.
My code for handling the port installation case sneaked in via
the previous commit.
PR: 155568
Submitted by: ehaupt
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
the GCC 4.6.1 release.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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]
|
| |
|
|
|
| |
PR: 157115
Tested by: joerg, mandree
|
| |
|
|
| |
a single tarball, so this brings a number of changes around that.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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]
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to sensibly list here, but http://gcc.gnu.org/gcc-4.6/changes.html has a
nice overview.
Some highlights include
- a new quad-precision library that's used by the Fortran frontend
(on x86 and amd64);
- new -Wunused-but-set-variable and -Wunused-but-set-parameter warnings
for C family languages (enabled by -Wall and -Wall -Wextra, too);
- new -Wdouble-promotion warning for implicit promotions to double;
- a new general optimization level -Ofast combines -O3 with options that
can affect standards compliance but result in better optimized code;
- link-time optimizations (LTO) now scaling to large input sizes, using
better heuristics, and optimizing more aggressively;
- new command-line options -fstack-usage and -fstrict-volatile-bitfields
(for precisely defining and accessing memory-mapped peripheral registers);
- function attribute leaf that allows for more aggressive optimizations;
- new data type __int128 for targets having wide enough machine-mode support;
- support for selectively enabling and disabling warnings via
#pragma GCC diagnostic has been added. For instance:
#pragma GCC diagnostic error "-Wuninitialized"
foo(a); /* error is given for this one */
#pragma GCC diagnostic push
#pragma GCC diagnostic ignored "-Wuninitialized"
foo(b); /* no diagnostic for this one */
#pragma GCC diagnostic pop
foo(c); /* error is given for this one */
#pragma GCC diagnostic pop
foo(d); /* depends on command line options */
- new command-line option-fmax-errors=N;
- experimental support for some features from the upcoming ISO C1X;
- similarly for ISO C++0x including constexpr, nullptr, noexcept,
unrestricted unions, range-based for loops, opaque enums, implicitly
deleted functions, and implicit move constructors;
- default warning when integers are cast to larger pointer types,
to disable via -Wno-int-to-pointer-cast;
- signficiantly better diagnostics for C++ code;
- loads and loads and loads of improvements to the Fortran frontend;
- a new Go frontend and run-time library;
- massive work on Objective-C and Objective-C++; notably extensive
support for Objective-C 2.0 (not enabled by this port yet);
- support for Intel Core 2 processors (-march=core2, -mtune=core2),
Intel Core i3/i5/i7 processors /with AVS (-march=corei7, -mtune=corei7,
-march=corei7-avx, -mtune=corei7-avx);
- support for AMD Bobcat (fam 14) processors (-march=btver1, -mtune=btver1);
Caveat:
- Most libstdc++ standard headers have been changed to no longer include
the cstddef header as an implementation detail.
|
| |
|
|
| |
Submitted by: andreast
|
| |
|
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
44 flavors of course.
Reported by: linimon
|
| |
|
|
|
| |
Address a long term FIXME related to older versions of FreeBSD by
removing NOMANCOMPRESS=yes.
|
| | |
|
| |
|
|
| |
Set MAKE_JOBS_SAFE to allow for parallel builds.
|
| |
|
|
|
|
|
|
|
|
|
| |
Remove obsolete code to create (empty) man pages in case regular man
pages cannot be created. This catches four dummy man pages we are
now able to remove: gjnih44, grepjar44, jar44, jv-scan44, rmic44,
and rmiregistry44.
Rename the check target to full-regression-test to be in sync with
the lang/gcc43 port. Add a conditional dependency on misc/dejagnu
and make the inclusion of gcc-testsuite in DISTFILES conditional, too.
|
| | |
|
| | |
|
| |
|
|
|
| |
This no longer contains bin/addr2name.awk44. Also remove the
post-build target and its hint for running the testsuite.
|
| |
|
|
|
|
|
|
|
| |
Set PORTNAME, MAINTAINER, COMMENT, and LATEST_LINK unconditionally as
opposed to using ?=.
Add powerpc to NOT_FOR_ARCHS. [1]
PR: 130964 [1]
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
us running into build problems, by an earlier check (pre-extract).
Suggested by: pav
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
