o Now uses libtool
o Lib-version changes from libXbae.so.8 to libXbae.so.4
-> implies modification of grace port
o PR: ports/45655
Originator: James E. Flemer <jflemer@alum.rpi.edu>
The screen is split into as many parts as there are files to watch.
Compiles on both -STABLE and -CURRENT.
PR: ports/46958
Submitted by: Michael L. Hostbaek <mich@freebsdcluster.org>
just happens to be fatal there, and a coding botch. The first problem is
that it assumes a termcap interface (which is an emulation on freebsd),
and provides its own terminfo wrappers around termcap.. so that's two
avoidable translation layers... termcap file -> terminfo (libncurses) ->
termcap API emulation (libncurses) -> terminfo (zsh emlulation). zsh
forgot to prototype the tiget* functions (which return pointers) so we
have an integer (implicit declaration) being cast to a pointer which
is fatal. The second problem is that zsh tries to use _mktemp() to get
around the __warn_references in our C library, but also neglects a
prototype there and has the same fatal int/pointer problem.
It is likely all the zsh* ports need these fixes. A test compile on
pluto1.freebsd.org will highlight the problem.
I do not know why the packaging fails for ia64. termcap.so and
terminfo.so are not being built for some reason, this change doesn't
solve that problem.
Note:
Object files built with version 6.0 of Intel(R) Compilers may not link
properly with objects built with version 7.0 of Intel(R) Compilers.
Rebuilding of the object files is suggested.
Changes between the submitted version and the committed version:
- update to 078 instead of 075
- treat excessive parameters in function calls as an error instead
of a warning (removed compatibility with a not named MS product, as
suggested by Intel)
- allow to override the INTEL_FLEXLM_LICENSE variable
From the submitter:
- Unbreak usage of signal.h on -current and RELENG_5_0.
(committers note: see below)
- Fix ownership of installed files when built as non-root.
- Fix the patched versions of the icc- and the icpc-script to work with options
containing spaces (e.g. '-DFOOBAR="foo bar"').
- Install 'clicense' and 'csupport' in the docs-dir even if NOPORTDOCS is
defined, the later is not optional but required by 'icid'.
- Move the ld-wrapper to a sub-dir and thus out of what is normally set in
PATH to prevent footshooting (this isn't perfect but simple until someone
reworks this port to provide FreeBSD-compatibility in another way... or
Intel releases a native version).
- Patch the headers to better fit for FreeBSD (hopefully...).
Notes: - Icc7 is more picky about unknow options than the previous versions,
i.e. the gcc-options normally supplied in CFLAGS unless altered in
/etc/make.conf. Therefore compilation of ports with icc likely fail
if the standard CFLAGS are not unset (e.g. `make CC=icc CFLAGS=""`)
or replaced by options valid for icc.
- When compiling multi-threaded C-code make sure to link with icc and
option '-mt' (for ports e.g. via PTHREAD_CFLAGS) otherwise libc_r
won't be linked in correctly.
Submitted by: marius@alchemy.franken.de
Additional information:
- rev 1.20 of src/sys/i386/include/signal.h introduced __aligned which
isn't handled in sys/cdefs.h for non GCC compilers (at least not in
publically available sources)
- the FreeBSD stdarg.h is missing a macro for va_copy() in the non GCC case,
we handle it in the port, but be prepared to get problems when the base
system gets fixed
- we don't use the icc-buildin of alignof()
- Intel provides a float.h which has different floatingpoint values
(e.g. MAX_FLOAT) than we have in the base system, in the port we use the
FreeBSD header (Warner knows about the issue... at least he got a mail
from me and Marius)
- we replace __wchar_t with __ct_rune_t because icc has a build-in type
for it, this affects "typedef __ct_rune_t __wchar_t;" in sys/_types.h.
It isn't known if this may be evil...
- icc doesn't need the option "-mt" anymore to generate thread safe code,
but our FreeBSD version still needs it to be able to choose libc_r
instead of libc
If a src-committer wants to address any of the above mentioned issues he
should first contact me, I may have already some fixes in my local tree.
