From: HAYASHI K. <ha...@cl...> - 2014-02-24 09:25:30
|
Hi, On Mon, 24 Feb 2014 16:22:50 +0900 HAYASHI Kentaro <ha...@cl...> wrote: > > Hi, > > On Mon, 24 Feb 2014 14:51:58 +0900 (JST) > Kouhei Sutou <ko...@cl...> wrote: > > > Hi, > > > > In <26081b58bc6a4431a17d3af67edf6d89@BY2PR07MB123.namprd07.prod.outlook.com> > > "[Groonga-talk] Porting to ARM" on Mon, 24 Feb 2014 04:46:40 +0000, > > Nicholas Robert Kemp <nr...@my...> wrote: > > > > > Hi. My name is Nick Kemp. I am working with a company called Linaro who is porting open source Linux packages to the ARM architecture. I was looking at the code for Groonga and I noticed that there was some assembly in there that might cause problems if running in an ARM environment and I wanted to determine the best way to solve this problem. > > > > Thanks for looking at Groonga! > > I'm sorry but I don't have an ARM machine. If you build > > Groonga on an ARM environment and report build errors, we > > can talk about these errors. Could you try it? > > > > > > Thanks, > > -- > > kou > > > > I don't have an ARM machine too, but I may be able to check Groonga build errors on ARM build environment > such as Koji (http://arm.koji.fedoraproject.org/koji/) > It may help with you to solve this problem. > I've just tried to check whether I can collect build error logs on ARM environment by using Fedora ARM build system. Here is the build errors on it. (Groonga 4.0.0) http://arm.koji.fedoraproject.org/work/tasks/6093/2246093/build.log We can talk about errors, based on actual logs. Would it be helpful? |