Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 02 May 2010 14:58:24 -0500
From:      Robert Noland <rnoland@FreeBSD.org>
To:        Garrett Cooper <yanefbsd@gmail.com>
Cc:        Demelier David <demelier.david@gmail.com>, "freebsd-ports@freebsd.org" <freebsd-ports@freebsd.org>
Subject:   Re: graphics/dri fails to build.
Message-ID:  <1272830304.2613.17.camel@balrog.2hip.net>
In-Reply-To: <28390E7D-8ED1-42F0-9476-537A9128D3E5@gmail.com>
References:  <20100502090442.GA2548@Abricot.malikania.fr> <20100502092610.GA50721@Abricot.malikania.fr> <1272803451.2452.17.camel@balrog.2hip.net> <28390E7D-8ED1-42F0-9476-537A9128D3E5@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2010-05-02 at 11:46 -0700, Garrett Cooper wrote:
> On May 2, 2010, at 5:30 AM, Robert Noland <rnoland@FreeBSD.org> wrote:
> 
> > On Sun, 2010-05-02 at 11:26 +0200, Demelier David wrote:
> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=143723
> >>
> >> It seems adding CFLAGS+=-march-=native solved the problem but I  
> >> don't want to
> >> keep this flag everytime in my make.conf
> >>
> >> How this flag could solve the problem ? I can't understand.
> >
> > This actually stems from libdrm.  Intel requires certain atomics that
> > are not available on pure i386.  They are present in code built for  
> > i486
> > +.  The default cpu was changed to i486 some time .
> 
> Should the port be marked broken with -march=i386 then?

Well, I'm not sure quite how we would do that... but if your
kernel/world is not really old, it should just work unless you force gcc
to produce code that will run on i386.

robert.

> -Garrett
-- 
Robert Noland <rnoland@FreeBSD.org>
FreeBSD




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1272830304.2613.17.camel>