On Aug 23, 2013, at 7:54 AM, David Chisnall wrote:
On 23 Aug 2013, at 14:52, Warner Losh i...@bsdimp.com wrote:
No. That breaks non x86 architecutres. gcc must remain in base for now, or
there's no bootstrap ability. Nobody has done the lifting to cleanly
integrate gcc as a port
On Aug 23, 2013, at 4:01 PM, Alfred Perlstein wrote:
On 8/23/13 3:35 AM, David Chisnall wrote:
On 23 Aug 2013, at 10:58, Bernhard Fröhlich de...@freebsd.org wrote:
I don't know if you are aware that IF you really do that we will have
serious
problems to ship packages for 10. USE_GCC=any
On May 7, 2013, at 11:41 PM, Simon J. Gerraty wrote:
On Tue, 7 May 2013 21:25:37 -0600, Warner Losh writes:
where does MAKEOBJDIRPREFIX come into play?
I don't normally use it, it is a handy but rather crude implement.
I normally use
MAKEOBJDIR='${.CURDIR:S,${SRCTOP},${OBJTOP
On May 7, 2013, at 9:42 PM, Garrett Cooper wrote:
On Tue, May 7, 2013 at 2:26 PM, Garrett Cooper yaneg...@gmail.com wrote:
On Tue, May 7, 2013 at 2:00 PM, Warner Losh i...@bsdimp.com wrote:
On May 7, 2013, at 2:46 PM, Garrett Cooper wrote:
On May 7, 2013, at 1:39 PM, Brooks Davis
On Mar 7, 2013, at 8:07 PM, Eitan Adler wrote:
On 7 March 2013 18:03, Tijl Coosemans t...@coosemans.org wrote:
On 2013-03-07 22:36, Warner Losh wrote:
On Mar 7, 2013, at 2:28 PM, Dimitry Andric wrote:
On 2013-03-07 21:22, Tijl Coosemans wrote:
...
Because it's the practical thing to do
On Mar 7, 2013, at 2:28 PM, Dimitry Andric wrote:
On 2013-03-07 21:22, Tijl Coosemans wrote:
...
Because it's the practical thing to do? Old code/makefiles can't possibly
be expected to know about compilers of the future, while new code can be
expected to add -std=c11.
I am not sure I
On Jan 25, 2013, at 4:31 AM, Konstantin Belousov wrote:
On Fri, Jan 25, 2013 at 08:41:11AM +, David Chisnall wrote:
Hi All,
In 10.0, the plan is not to ship any GPL'd code, so I'd like to start
disconnecting things from the default build, starting with gcc. I've been
running a
On Jan 25, 2013, at 3:18 PM, Andriy Gapon wrote:
on 25/01/2013 21:35 Warner Losh said the following:
This has been talked about in a vague way for years.
Warner,
just a nitpick, couldn't resist - sorry, so for years we talked about the
magic
10.x release to become GPL-free
On Dec 13, 2012, at 6:18 AM, Erik Cederstrand wrote:
Den 13/12/2012 kl. 14.10 skrev David Chisnall thera...@freebsd.org:
Hi Eric,
The easiest way of doing this is to make /usr/bin/ld (in the host system and
in the bootstrap) into a symbolic link that points to whatever the selected
Hi Pete,
the best way to find out if support for archives are needed is to release it
for testing. People find the craziest things when testing in a wider arena.
Alternatively, see if can survive /usr/ports being thrown at it :) even clang
can't do that yet (although it isn't always clang's
On Jul 6, 2012, at 1:11 PM, David Chisnall wrote:
On 6 Jul 2012, at 17:54, Andriy Gapon wrote:
Yeah. Honestly speaking I myself was not aware of what is written in that
link
and I thought that our gcc ports (from ports) added /usr/local/include to the
default search path by some
On Feb 26, 2012, at 2:37 PM, Alexander Best wrote:
hi there,
any chance support for setting CC/CXX/CPP unconditionally in src.conf could be
added before the release of freebsd 10.0? the way it is done atm is really not
intuitive. the rule should really be:
- make.conf = applies globally
On Nov 6, 2011, at 1:58 PM, Alexander Best wrote:
On Sun Nov 6 11, Dimitry Andric wrote:
On 2011-11-06 21:33, Alexander Best wrote:
...
the problem is, something like
uint x;
if (x 0) ...
clang will warn about this, yet it is 100% valid code so my vote would be to
make such an
On Nov 6, 2011, at 2:13 PM, Rui Paulo wrote:
The only argument against this tautological check that I agree with is when
the code is explicitly trying to be safe. If the developer checks for i 0
when indexing an array he/she is trying to guard against possible pitfalls in
the future when
On Nov 6, 2011, at 5:47 PM, Rui Paulo wrote:
On Nov 6, 2011, at 4:36 PM, Warner Losh wrote:
On Nov 6, 2011, at 2:13 PM, Rui Paulo wrote:
The only argument against this tautological check that I agree with is when
the code is explicitly trying to be safe. If the developer checks for i
0
I'm all for leaving it on because things like char are signed on some
architectures and unsigned on others. This leads to bugs that only appear on
one architecture. This warning will, at least, flag those usages.
On Oct 17, 2011, at 10:56 AM, Gerald Pfeifer wrote:
On Mon, 17 Oct 2011,
We really need a 'SYSTEM_COMPILER={gcc,clang,xxx}' sort of knob.
Warner
On Aug 18, 2011, at 2:04 PM, Kostik Belousov wrote:
On Thu, Aug 18, 2011 at 09:54:41PM +0200, Dimitry Andric wrote:
The problem is in your make.conf. Effectively, you are doing:
CC = clang
CXX = clang++
which will
You need to use buildworld or one of its sub-targets.
Warner
On Aug 4, 2011, at 2:38 AM, majia gm wrote:
Hi, everyone.
I'm building the libc code which derived from a current trunk
mirror/freebsd/head under PCBSD 8.2 which contains FreeBSD 8.2
release.
I'm trying to test the modified
On Jun 25, 2011, at 9:16 AM, Gerald Pfeifer wrote:
On Wed, 22 Jun 2011, Damjan Marion wrote:
I see 3 options to fix this:
1. Ask clang folks to patch llvm to use old mnemonics (mov r0, r0, rrx
instead of rrx r0,r0)
2. Maintain same patch for freebsd only
3. patch binutils to support
On Jun 21, 2011, at 3:12 AM, Damjan Marion wrote:
On Jun 17, 2011, at 9:16 PM, Warner Losh wrote:
On Jun 17, 2011, at 12:38 PM, Damjan Marion wrote:
Now, I'm back on my original problem, clang invokes /usr/bin/as which is
i386 AS instead of ARM version in obj tree.
That's a bogus
101 - 120 of 120 matches
Mail list logo
