Hi guys,
It's time for a small status update. This won't be an extensive list, but at least give you an overview of what has happened since the last time :).
*** We can successfully build ~3500 out of ~4700 Factory packages! ***
Unfortunately Factory is updating so fast that we just haven't managed to do a full build of all these shina packages for the last 3 weeks, so packages you see in the download repository are from 3 weeks ago. To fetch the newer builds, just run "osc getbinaries ...". Beware of dragons though :).
Also, there are a couple of things we have now that weren't there before:
* Lots of qemu fixes to get stuff building
* Kernel rpms so we can generate kernels for the following flavors: default, tegra, omap2plus (Pandaboard), imx51 (EFIKA MX)
* Build fixes for a number of packages (otherwise we wouldn't get 3.5k!)
* U-boot package for pandaboard (thanks Joop!)
* Probably a lot of stuff I can't remember atm. If you have worked on something and want to add it to the list, please reply to this mail so we have more overview :).
So what is still missing from here? Well, these are the pieces I'm tracking right now:
* Kiwi support (Marcus is on it!)
* Kernel testing and making-it-work [1]
* Exception handling [1] keeps us from building Java, keeps us from building most of the other 1200 packages
* hwinfo probably needs some love for ARM
* yast2 could use some love as well :)
* X drivers are probably still missing
* Fixing broken packages, there are still a few that are not broken because of exception handling :)
[1] To handle exceptions we need to be able to unwind state at certain points in the code. This unwinding requires special tables which are different on ARM than on any other platform out there. Now the problem is that even a program as simple as:
#include <stdio.h>
int main(int argc, char **argv)
{
try {
throw -1;
}
catch (int) {
fprintf(stderr, "We caught an exception of type int\n");
}
}
fails to execute on our current builds. Thus gmp and gcj don't build properly and everything depending on Java just doesn't even get built. I'm trying to reproduce this with Linaro's gcc to maybe get some help from them. Once we have that, the kernel might end up working and we should have an almost-completely-built distro (no guarantees for actually working code).
Alex
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
On Sun, November 27, 2011 8:35 pm, Alexander Graf wrote:
>
> On 27.11.2011, at 20:17, Tomas Cech wrote:
>
>> On Thu, Nov 24, 2011 at 04:53:36PM +0100, Alexander Graf wrote:
>>> Hi guys,
>>>
>>> It's time for a small status update. This won't be an extensive list,
but at least give you an overview of what has happened since the last
time :).
>>>
>>> *** We can successfully build ~3500 out of ~4700 Factory packages! ***
>>>
>>
>> I'm still not able to find, where is the right project with armv7l
failing packages, could somebody send link?
>>
>> This one
>> https://build.opensuse.org/project/monitor?commit=Filter%3A&failed=1&pkgnam…
(which can be found on http://en.opensuse.org/Portal:ARM) doesn't show
any armv7l packages...
>
> Ah, sorry, I fixed the link on the wiki now :). Basically your portal to
any interesting information is at
>
> https://build.opensuse.org/project/show?project=openSUSE:Factory:ARM
>
>>
>>> Unfortunately Factory is updating so fast that we just haven't managed
to do a full build of all these shina packages for the last 3 weeks,
so packages you see in the download repository are from 3 weeks ago.
To fetch the newer builds, just run "osc getbinaries ...". Beware of
dragons though :).
>>
>> If it is worth of effort, I can set up that new Efika MX as OBS worker
(if someone help me - prusnak or miska probably already have
>> experience with this). I would just disable it when I'm trying to fix
or test something.
>
> Yes, please :). Adrian probably has a pretty clear idea on what's
required to get this rolling.
>
>>
>>> So what is still missing from here? Well, these are the pieces I'm
tracking right now:
>>>
>>> * Kiwi support (Marcus is on it!)
>>> * Kernel testing and making-it-work [1]
>>
>> I think/hope that I can help a bit here.
>
> I got the pandaboard kernel reasonably well working now, so if you could
tackle the i.MX51 one, I would very much appreciate it :).
>
>>
>>> * Exception handling [1] keeps us from building Java, keeps us from
building most of the other 1200 packages
>>> * hwinfo probably needs some love for ARM
>>> * yast2 could use some love as well :)
>>> * X drivers are probably still missing
>>> * Fixing broken packages, there are still a few that are not broken
because of exception handling :)
>> And with this hopefully too.
>
> There are a couple of generic broken ones thanks to the recent ncurses
changes in factory. I'm still puzzled why bash doesn't compile anymore
for example - it's definitely related to the curses change.
I assume this is the problem, see buildlog (
https://build.opensuse.org/package/rawlog?arch=armv7l&package=bash&project=…
and
https://build.opensuse.org/package/rawlog?arch=armv5el&package=bash&project…)
:
<armv5el>
checking whether gcc -I/home/abuild/rpmbuild/BUILD/bash-4.2
-L/home/abuild/rpmbuild/BUILD/bash-4.2/../readline-6.2 needs
-traditional... no
checking for tgetent... no
checking for tgetent in -ltermcap... no
checking for tgetent in -ltinfo... no
checking for tgetent in -lcurses... no
checking for tgetent in -lncurses... yes
checking which library has the termcap functions... using libncurses
</armv5el>
<armv7l>
checking whether gcc -I/home/abuild/rpmbuild/BUILD/bash-4.2
-L/home/abuild/rpmbuild/BUILD/bash-4.2/../readline-6.2 needs
-traditional... no
checking for tgetent... no
checking for tgetent in -ltermcap... yes
checking which library has the termcap functions... using libtermcap
</armv7l>
>
> Then there are a number of packages that complain in thumb mode "swp"
instructions. However, swp is not guaranteed by the armv7 architecture
anymore, so if there's old thumb code somewhere which gets triggered by
our build, you see those swp errors. The easy fix is to just disable
thumb for that package. Just check texlive-bin on how that works :).
>
>
> Alex
>
>
Regards,
Joop.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Attached patch provides support for ST-Ericsson's U8500 NovaThor as
found in the Snowball board. It compiles and builds fine, but I have yet
to run it (awaiting receipt of board).
Regards,
Andy
--
Andrew Wafaa
IRC: FunkyPenguin
GPG: 0x3A36312F
On 22.11.2011, at 15:47, Andrew Wafaa wrote:
> On Mon, 2011-11-14 at 11:54 +0100, Adrian Schröter wrote:
>> Am Montag, 14. November 2011, 10:19:54 schrieb Andrew Wafaa:
>>> On Mon, 2011-11-14 at 11:03 +0100, Michal Marek wrote:
>>>> On 14.11.2011 10:26, Adrian Schröter wrote:
>>>>> Am Montag, 14. November 2011, 10:06:14 schrieb Michal Marek:
>>>>>> On 14.11.2011 09:08, Adrian Schröter wrote:
>>>>>>> - initial armv7l default kernel config, everything
>>>>>>> enable except
>>>>>>> the non compiling modules - makeing arm configs again
>>>>>>> armvX
>>>>>>> specific
>>>>>>
>>>>>> If the configs are to be placed under config/armvX, then you're
>>>>>> missing a change to rpm/arch-symbols.
>>>>>
>>>>> No, I did not miss it, I reverted it.
>>>>
>>>> Not in the patch you posted. And you additionally need to modify
>>>> ./rpm/arch-symbols --list to list all the arm families.
>>
>> sorry, missed this in my local git. Fixed version attached.
>>
>>>>> There is no way to have a single config for armv5 and armv7 IMHO.
>>>
>>> Correct. It may be possible when armv8 is released in a couple of years,
>>> but having spoken in depth with Linaro who are trying to clean up this
>>> area, they said it is a slow and often painful process but they are
>>> making some progress.
>>>
>>>>>> Also, are you talking to Andrew, who has
>>>>>> been working on more or less the same lately?
>>>>>
>>>>> I had contact but never saw any patch. AFAIK he only works on
>>>>> specific kernels for specific hardware (which would also be armvX
>>>>> specific), while this kernel is supposed to be as near as possible
>>>>> to the standard SUSE kernel.>
>>>> The latest patch he posted is at
>>>> http://lists.opensuse.org/opensuse-kernel/2011-11/msg00024.html.
>>>
>>> Are you saying you want %arm = armv7l or are you saying something else?
>>
>> %arm is "armv5tel armv7l armv8l ...."
>>
>>> At present I have all the arm configs in config/arm/, which would build
>>> on armv7l. Should we add any armv5 devices they would also live in
>>> there. I'm not sure that the -default kernel would actually run on any
>>> hardware, so it would be isolated to qemu really wouldn't it?
>>
>> I think we need to split this again into
>>
>> config/armv5tel
>> config/armv7l
>> config/armv8l
>>
>> what allows us to have a kernel packages with same name but different config.
>>
>
> I've rebased my patch according to Adrian's request to have a separate
> armv* config. All build fine, although I haven't tested - still trying
> to workout how best to do this, any hints?
Thanks, I applied your and Adrian's patches and sat down to refine configs so they actually build properly. We now have 4 flavors:
- default (QEMU?)
- imx51 (EFIKA)
- tegra2
- omap (pandaboard)
I have verified that I could barely boot the omap kernel on a pandaboard. I did however get the weird kernel messages I sent out to the ARM list earlier. But that's a separate issue - at least we have something to base on now.
So if you have an ARMv7 box and you want to have openSUSE running on it, please check if the kernels actually work for you. I'm pretty sure we did some config pieces wrong at random points :)
Also, we have a new build requirement for ARM: mkimage. There is a package on its way to Factory called u-boot-tools which contains mkimage. We need this to convert the zImages to uImages which u-boot can boot off of. But since it's covered by %if %arm we should be fine until it actually hits Factory :).
Alex
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi guys,
To build a kernel on ARM we need the u-boot tool "mkimage". Looking
through OBS I spotted that Joop had already created packages for this
and even got them successfully submitted to Base:System. Great!
However, to make use of them in the kernel rpm I need them to be in
Factory :). Could you guys please settle on the maintainership of the
u-boot packages and submit them to Factory so that I can continue to
build on them?
Thanks,
Alex
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi all,
It looks like openSUSE:Factory:ARM standard armv7l isn't published any more.
The latest update was around November 3 2011.
Regards,
Joop.
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi guys,
Looking at the texinfo build log I stumbled over the following difference between the x86 and the arm build:
###### x86 ######
checking for tgetent in -lncurses... yes
checking for library with termcap variables...
checking ncurses/termcap.h usability... yes
checking ncurses/termcap.h presence... yes
checking for ncurses/termcap.h... yes
###### ARM ######
checking for tgetent in -lncurses... no
checking for tgetent in -lcurses... no
checking for tgetent in -ltermlib... no
checking for tgetent in -ltermcap... no
checking for tgetent in -lterminfo... no
configure: WARNING: probably need a terminal library, one of: ncurses curses termlib termcap terminfo
checking for library with termcap variables...
The build failure in the ARM package seems to be related:
terminal.o: In function `terminal_goto_xy':
/home/abuild/rpmbuild/BUILD/texinfo-4.13/info/terminal.c:235: undefined reference to `tgoto'
If anyone is searching for a (potential) low hanging fruit, I hope this is one :). It is not an emulation bug btw - the native build fails the exact same way.
Alex
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
On Mon, November 14, 2011 10:09 am, Andrew Wafaa wrote:
> On Mon, 2011-11-14 at 09:14 +0100, Joop Boonen wrote:
>> I didn't get to this was working on the kernel. Hopefully I can fix
this issues with this one soon. I have an usb issue, that I need to
fix. ( home:worldcitizen:armv7l kernel-omap4panda )
>>
>
> I've submitted a patch to the kernel team that builds the following
>kernels for 3.1: omap2plus, imx51 and tegra. Let me know if you need
>anything from that to help with u-boot etc.
u-boot and x-boot are not dependent on the kernel as far as I know.
Does this patch give a prompt in the tty's?
I've build the terminal according to http://elinux.org/PandaBoard this
didn't give a prompt in the tty.
For me the only working kernel is the one according to:
http://wiki.meego.com/ARM/OMAP4_Panda#kernel
>
>> After that I'll start working on kiwi.
>>
>> >
>> >> > Hopefully
>> >> > the current build will succeed.
>> >> >
>> >> > If someone wants to help, could someone package u-boot (the arm
>> boot
>> >> > loader) ?
>> >> > I suppose it will be a pre-requirement for the kiwi support.
>> >>
>> >> U-boot has been build for the pandaboard. I used the meego version as
>> a
>> >> base. It still needs a bit of tuning.
>> >> The package can be found here: home:worldcitizen:armv7l
>> >> u-boot-omap4panda
>> >
>> > please look for a devel project and submit to factory.
>> >
>> I've submitted both x-loader-omap4panda and u-boot-omap4panda to
Base:System . (request id 91227 and request id 91228)
>> I've tested both of them on my PandaBoard.
>>
>
> Would it be possible to re-name the packages to fall in line with the
kernels being built? For OMAP it is omap2plus, as per the config. This
should support all omap2plus devices, including the Beagle and Panda.
That's OK. I can rename it. I won't be able to test it on a BeagleBoard.
>
> Regards,
>
> Andy
>
> --
> Andrew Wafaa
> IRC: FunkyPenguin
> GPG: 0x3A36312F
>
>
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hello,
I did not have Internet access for more than a week, and lost a bit
track, what is going on with the openSUSE ARM port. What I see is very
good news: over 3000 packages build already (
https://build.opensuse.org/project/show?project=openSUSE%3AFactory%3AARM
). As I have an EFIKA MX and helped to get some EFIKAs for developers,
my questions relate to it:
- what triplet is used to compile hardfloat binaries? In the archives I
found:
"Currently we're building with -march=armv7-a -mfloat-abi=hard
-mfpu=vfp3-d16 -mthumb." Is it still the case? (I was asked by Debian
ARM HF project lead last week...)
- how are the EFIKAs used?
- I have openSUSE running in a chroot on my smartbook, thanks to
http://michal.hrusecky.net/2011/10/opensuse-arm-chroot-less-then-alpha/
Is there already an image which could be booted directly? Or
instructions how to install it natively on the EFIKA?
I'll be an FSF Hungary conference this weekend, and would be nice to
demo my smartbook with openSUSE running native :)
Bye,
CzP
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
