On Mon, Mar 11, 2013 at 02:18:51PM -0700, Steve Kargl wrote:
> On Mon, Mar 11, 2013 at 10:05:47PM +0100, Dimitry Andric wrote:
> > On 2013-03-11 20:00, Jan Beich wrote:
> > > Dimitry Andric writes:
> > >
> > >> $ echo 'sub/foo.barx' | grep sub/foo.bar
> > >> $ echo $?
> > >> 1
> > >
> > > $ echo
On Mon, Mar 11, 2013 at 10:05:47PM +0100, Dimitry Andric wrote:
> On 2013-03-11 20:00, Jan Beich wrote:
> > Dimitry Andric writes:
> >
> >> $ echo 'sub/foo.barx' | grep sub/foo.bar
> >> $ echo $?
> >> 1
> >
> > $ echo 'sub/foo.barx' | env -i grep sub/foo.bar
> > $ echo 'sub/foolbarx' | env -i gr
On 2013-03-11 20:00, Jan Beich wrote:
> Dimitry Andric writes:
>
>> $ echo 'sub/foo.barx' | grep sub/foo.bar
>> $ echo $?
>> 1
>
> $ echo 'sub/foo.barx' | env -i grep sub/foo.bar
> $ echo 'sub/foolbarx' | env -i grep sub/foo.bar
> $ echo 'sub/foo.barx' | env -i grep 'sub/foo\.bar'
> sub/foo.barx
Dimitry Andric writes:
> $ echo 'sub/foo.barx' | grep sub/foo.bar
> $ echo $?
> 1
$ echo 'sub/foo.barx' | env -i grep sub/foo.bar
$ echo 'sub/foolbarx' | env -i grep sub/foo.bar
$ echo 'sub/foo.barx' | env -i grep 'sub/foo\.bar'
sub/foo.barx
$ echo 'sub/foo.barx' | env -i grep -o sub/foo.bar
sub
11.03.2013 18:57, O. Hartmann пишет:
On Mon, 2013-03-11 at 17:29 +0100, Dimitry Andric wrote:
On 2013-03-11 14:15, Niclas Zeising wrote:
BSD grep does something very strange here:
$ echo 'foo.bar' | grep foo.bar
foo.bar
$ echo 'foo.barx' | grep foo.bar
foo.barx
$ echo 'sub/foo.bar' | grep su
On Mon, 2013-03-11 at 17:29 +0100, Dimitry Andric wrote:
> On 2013-03-11 14:15, Niclas Zeising wrote:
> > On 03/11/13 14:13, Steve Kargl wrote:
> ...
> >> No. Here's my make.conf.
> >>
> >> KERNCONF=SPEW
> >> CPUTYPE?=opteron
> >> FFLAGS+= -O2 -pipe -march=native -mtune=native -funroll-loops
> >>
On 2013-03-11 14:15, Niclas Zeising wrote:
On 03/11/13 14:13, Steve Kargl wrote:
...
No. Here's my make.conf.
KERNCONF=SPEW
CPUTYPE?=opteron
FFLAGS+= -O2 -pipe -march=native -mtune=native -funroll-loops -ftree-vectorize
MALLOC_PRODUCTION="YES"
WITHOUT_LIB32="YES"
WITHOUT_MODULES="YES"
WITHOUT
On 03/11/13 14:13, Steve Kargl wrote:
> On Mon, Mar 11, 2013 at 11:17:51AM +0100, Dimitry Andric wrote:
>> On 2013-03-10 00:39, Steve Kargl wrote:
>> ...
>>> If you have a clang built FreeBSD-current, then it is no
>>> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor
>>> the upcoming gcc-4.
On Mon, Mar 11, 2013 at 11:17:51AM +0100, Dimitry Andric wrote:
> On 2013-03-10 00:39, Steve Kargl wrote:
> ...
> > If you have a clang built FreeBSD-current, then it is no
> > longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor
> > the upcoming gcc-4.8.0. AFAICT, the problem is related
> > t
On 03/11/2013 12:00, Niclas Zeising wrote:
On 2013-03-11 11:58, Hartmann, O. wrote:
Am 03/11/13 11:17, schrieb Dimitry Andric:
On 2013-03-10 00:39, Steve Kargl wrote:
...
If you have a clang built FreeBSD-current, then it is no
longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor
the upcom
On Mon, 2013-03-11 at 12:00 +0100, Niclas Zeising wrote:
> On 2013-03-11 11:58, Hartmann, O. wrote:
> > Am 03/11/13 11:17, schrieb Dimitry Andric:
> >> On 2013-03-10 00:39, Steve Kargl wrote:
> >> ...
> >>> If you have a clang built FreeBSD-current, then it is no
> >>> longer possible to *bootstrap
On 2013-03-11 11:58, Hartmann, O. wrote:
> Am 03/11/13 11:17, schrieb Dimitry Andric:
>> On 2013-03-10 00:39, Steve Kargl wrote:
>> ...
>>> If you have a clang built FreeBSD-current, then it is no
>>> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor
>>> the upcoming gcc-4.8.0. AFAICT, the
On 03/11/2013 11:17, Dimitry Andric wrote:
On 2013-03-10 00:39, Steve Kargl wrote:
...
If you have a clang built FreeBSD-current, then it is no
longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor
the upcoming gcc-4.8.0. AFAICT, the problem is related
to /usr/bin/cpp. I haven't tried earli
Am 03/11/13 11:17, schrieb Dimitry Andric:
> On 2013-03-10 00:39, Steve Kargl wrote:
> ...
>> If you have a clang built FreeBSD-current, then it is no
>> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor
>> the upcoming gcc-4.8.0. AFAICT, the problem is related
>> to /usr/bin/cpp. I haven'
On 2013-03-10 00:39, Steve Kargl wrote:
...
If you have a clang built FreeBSD-current, then it is no
longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor
the upcoming gcc-4.8.0. AFAICT, the problem is related
to /usr/bin/cpp. I haven't tried earlier versions of
gcc.
I have built the lang/
On Sat, Mar 09, 2013 at 05:02:56PM +0100, Dimitry Andric wrote:
> On Mar 9, 2013, at 16:36 , "Hartmann, O." wrote:
> > I have one specific FreeBSD 10.0-CURRENT box (FreeBSD 10.0-CURRENT #0
> > r248061: Fri Mar 8 19:44:30 CET 2013 amd64) which rejects to build
> > either lang/gcc or lang/gcc46 wit
Am 03/09/13 17:02, schrieb Dimitry Andric:
> On Mar 9, 2013, at 16:36 , "Hartmann, O." wrote:
>> I have one specific FreeBSD 10.0-CURRENT box (FreeBSD 10.0-CURRENT #0
>> r248061: Fri Mar 8 19:44:30 CET 2013 amd64) which rejects to build
>> either lang/gcc or lang/gcc46 with the very same error sh
On Mar 9, 2013, at 16:36 , "Hartmann, O." wrote:
> I have one specific FreeBSD 10.0-CURRENT box (FreeBSD 10.0-CURRENT #0
> r248061: Fri Mar 8 19:44:30 CET 2013 amd64) which rejects to build
> either lang/gcc or lang/gcc46 with the very same error shown below.
…
> checking whether cc supports -ped
I have one specific FreeBSD 10.0-CURRENT box (FreeBSD 10.0-CURRENT #0
r248061: Fri Mar 8 19:44:30 CET 2013 amd64) which rejects to build
either lang/gcc or lang/gcc46 with the very same error shown below.
The box is compiled with CLANG (buildworld/kernel).
It doesn't matter whether I compile tho
19 matches
Mail list logo
