I want to add my repo's url to /etc/yum.repos.d/ and have "yum install" find my rpms. <br><br>Maybe my problem is that I really don't understand the difference between in yum's use of $ARCH and $BASEARCH for arm.<br>
<br>After a little reflection, I can just do "trial and error". If my rpms are not found, I can just change the path from ../rpms/armv7hl/... to ../rpms/armv7l/.. and recreate the repo xml files. <br><br>I read on the fedora wiki that userland armv7hl and armv7l complied programs don't mix. But your assurance that the XO is really armv7hl is what I couldn't find easily on the web.<br>
<br>Thanks again,<br><br>George<br><br><div class="gmail_quote">On Fri, Jul 6, 2012 at 6:59 AM, Peter Robinson <span dir="ltr"><<a href="mailto:pbrobinson@gmail.com" target="_blank">pbrobinson@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, Jul 6, 2012 at 11:52 AM, George Hunt <<a href="mailto:georgejhunt@gmail.com">georgejhunt@gmail.com</a>> wrote:<br>
> Thanks Peter,<br>
><br>
> I was confused when I installed latest 12.1.0 on an XO and issued "uname<br>
> -a", to see the response come back armv7l, rather than armv7hl. I was<br>
> thinking that yum would be confused by the difference.<br>
<br>
</div>The kernel isn't hardfp/softfp because the kernel doesn't use maths<br>
co-processors. rpm/yum has been hacked to deal with it. It's all a<br>
little ugly but it works.<br>
<div class="im"><br>
> I'm glad that the trimslice generated rpms I have will be usable. I'll need<br>
> to learn how to override the default arch, so that yum will do what I want<br>
> it to do. But I have google for that!<br>
<br>
</div>Why do you need to override the arch? What exactly are you trying to do?<br>
<div class="HOEnZb"><div class="h5"><br>
> Thanks for your help,<br>
><br>
> George<br>
><br>
><br>
> On Fri, Jul 6, 2012 at 6:39 AM, Peter Robinson <<a href="mailto:pbrobinson@gmail.com">pbrobinson@gmail.com</a>> wrote:<br>
>><br>
>> On Fri, Jul 6, 2012 at 10:42 AM, George Hunt <<a href="mailto:georgejhunt@gmail.com">georgejhunt@gmail.com</a>><br>
>> wrote:<br>
>> > Hi Peter,<br>
>> ><br>
>> > You probably know the answer to this question off the top of your head.<br>
>> ><br>
>> > I've played with fedora's Trimslice armv7hl, using it to recompile XS<br>
>> > rpms.<br>
>> > Now in conversation with OLPC-Australia, I've agreed to try to apply my<br>
>> > stuff to the XO-1.75 pre-release 12.1.0, which I believe is based upon<br>
>> > FC17.<br>
>><br>
>> It is indeed, it's using the F-17 arm hardfp release.<br>
>><br>
>> > Question: Is my easiest path to basically start over, either building up<br>
>> > a<br>
>> > cross compiling tool chain, or maybe try to compile the XS rpms on an<br>
>> > armv7l<br>
>> > machine natively, as I did with the TS, (the XO itself seems the obvious<br>
>> > choice).<br>
>><br>
>> If you have a trimslice why don't you use that and compile natively?<br>
>> In Fedora everything is compiled natively with no cross-compilation.<br>
>><br>
>> > I had trouble earlier getting a tool chain together to run on FC17, on<br>
>> > top<br>
>> > if parallels, on my MAC.<br>
>><br>
>> To be honest I've never cross compiled any ARM packages.<br>
>><br>
>> > Do you have any advice?<br>
>><br>
>> Compile natively :-)<br>
>><br>
>> If you have a Trimslice, Pandaboard or even an XO 1.75 you can compile<br>
>> on all of those using the standard distros. On any of the platforms<br>
>> you can "yum install" or "yum groupinstall " anything you may need and<br>
>> build directly. You might want to add an ext4 formatted usb HDD to use<br>
>> as the storage for building on those platforms as they tend to be a<br>
>> bit quicker than SD card storage.<br>
>><br>
>> Peter<br>
><br>
><br>
</div></div></blockquote></div><br>