aarch64 acceleration is now enabled.

armv6hl still waits for new gcc48

I keep an eye on it...
adrian


Am Donnerstag, 12. September 2013, 17:50:41 schrieb Adrian Schröter:
> Am Donnerstag, 12. September 2013, 10:26:42 schrieb Alexander Graf:
> > On 12.09.2013, at 04:39, Adrian Schröter wrote:
> > > Am Donnerstag, 12. September 2013, 10:36:46 schrieb Adrian Schröter:
> > >> Hi,
> > >> 
> > >> I have a working setup for using the accelerated binaries for aarch64
> > >> builds in
> > >> 
> > >>  home:adrianSuSE:branches:openSUSE:Factory:ARM
> > >> 
> > >> also, I am working on accelerated armv6hl.
> > >> 
> > >> Is there any reason not to apply the current state already in
> > >> openSUSE:Factory:ARM for aarch64?
> > > 
> > > okay, armv6hl works also now accelerated.
> > > 
> > > Any objections not to use it in openSUSE:Factory:ARM ?
> > > 
> > > Still missing bits are:
> > > * no x86_64 bash on aarch64 yet
> > > * reverted "fix msg* to support iconv". This leads to file conflicts
> > > 
> > >   and make the package not installable.
> > >   => this should not be needed, because files are provided by
> > >   glibc-locale
> > >   
> > >      package. If that one is not installed something general is broken.
> > >   
> > >   Alex, any comment on that?
> > 
> > I don't remember :). It might have been a hack to satisfy different paths
> > for x86_64 and armv7.
> 
> after discussing with Dirk we decided to drop entire iconv/msg* stuff for
> now. It was a bit flaky in the past.
> 
> aarch64 accel stuff exists now in openSUSE:Factory:ARM, but it is not yet
> enabled in prjconf.
> 
> armv6hl waits that my cross compiler changes get accepted in
> openSUSE:Factory. (I think creating own compiler packages in
> openSUSE:Factory:ARM is more messy)

-- 

Adrian Schroeter
email: [email protected]

SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 
(AG Nürnberg)
Maxfeldstraße 5                         
90409 Nürnberg 
Germany 



--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to