Performing substitutions during post-patch breaks tools such as mkpatches,
making it very difficult to regenerate correct patches after making changes,
and often leading to substituted string replacements being committed.
Existing SHA1 digests verified, all found to be the same on the
machine holding the existing distfiles (morden). Existing SHA1
digests retained for now as an audit trail.
different from the PR (When submitting patch to pkgsrc with
adding more patches, submitter should do cvs add
patches/patch-hoge, before creating the pkgsrc patch, thanks).
I belive both simulavr and avr-libc will be packaged fine with this.
(upstream)
4.7.3 to 4.8.3 -- From grepping 'avr' from NEWS file:
--------------
On AVR, the configure option --with-avrlibc supported since GCC 4.7.2
is turned on per default for all non-RTEMS configurations. This option
arranges for a better integration of [3]AVR Libc with avr-gcc. For
technical details, see [4]PR54461. To turn off the option in non-RTEMS
configurations, use --with-avrlibc=no. If the compiler is configured
for RTEMS, the option is always turned off.
* Support has been added for the AVR-specific configure option
--with-avrlibc=yes in order to arrange for better integration of
[3]AVR-Libc. This configure option is supported in avr-gcc 4.7.2
and newer and will only take effect in non-RTEMS configurations. If
avr-gcc is configured for RTEMS, the option will be ignored which
is the same as specifying --with-avrlibc=no. See [4]PR54461 for
more technical details.
3. http://www.nongnu.org/avr-libc/
4. http://gcc.gnu.org/PR54461
#include <avr/io.h> /* Port Definitions from AVR-LibC */
* [297]14064 [avr-elf] -fdata-sections triggers ICE
* [302]16884 [avr-elf] [fweb related] bug while initializing
4.5.3 to 4.7.3
--------------
For the changes for 4.7, see following page.
http://gcc.gnu.org/gcc-4.7/changes.html
(Picking up AVR related topic from above info):
The AVR port's libgcc has been improved and its multilib
structure has been enhanced. As a result, all objects
contributing to an application must either be compiled with
GCC versions up to 4.6.x or with GCC versions 4.7.1 or
later. If the compiler is used with AVR Libc, you need a
version that supports the new layout, i.e. implements #35407.
The AVR port's -mshort-calls command-line option has been
deprecated. It will be removed in the GCC 4.8 release. See
-mrelax for a replacement.
The AVR port only references startup code that clears .bss and
the common section resp. initializes the .data and .rodata
section provided respective sections (or subsections thereof)
are not empty, see PR18145.
Applications that put all static storage objects into
non-standard sections and / or define all static storage
objects in assembler modules, must reference __do_clear_bss
resp. __do_copy_data by hand or undefine the symbol(s) by
means of -Wl,-u,__do_clear_bss resp. -Wl,-u,__do_copy_data.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
using the system/Pkgsrc zlib. At least on Ubuntu, the internal zlib fails to
get past configuration.
Use the standard Pkgsrc (or builtin) zlib instead.
Bump PKGREVISION to reflect the minor difference in build strategy.
(pkgsrc)
Removing:
patches/patch-aa
(was not to install: install-subdir at libiberty)
patches/patch-ac
(was not to install tree-inline.o cppdefault.o for Mac OS X,
equivalent target does not have these files for now)
patches/patch-gcc_toplev.h
Upstream corrected the problem as:
-extern inline int
+static inline int
Adding:
patch-gcc_config_avr_driver-avr_c
To fix the problem like:
error: non-void function 'avr_device_to_arch' should return a value [-Wreturn-type]
patch-libiberty_Makefile.in
Not install libiberty.a
to avoid duplication (conflict) with other cross tool-chain (mef@).
(upstream)
For the changes from 4.4.1 to 4.5, see following page.
http://gcc.gnu.org/gcc-4.5/changes.html
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
* Remove BUILD_DEPENDS on bison, it already in USE_TOOLS.
* Remove USE_BZIP2, not buildlink with bzip2, no effect.
* Remove custom do-* target, *_DIRS is sufficient to do so and use it instead.
* Remove MAKE_FLAGS="c c++", it was not used, and it result in missing "gcov"
after above modification.
* then, add user-destdir support, inspired by PR 42438.
PKGLOCALEDIR and which install their locale files directly under
${PREFIX}/${PKGLOCALEDIR} and sort the PLIST file entries. From now
on, pkgsrc/mk/plist/plist-locale.awk will automatically handle
transforming the PLIST to refer to the correct locale directory.
around at either build-time or at run-time is:
USE_TOOLS+= perl # build-time
USE_TOOLS+= perl:run # run-time
Also remove some places where perl5/buildlink3.mk was being included
by a package Makefile, but all that the package wanted was the Perl
executable.
