Hi all,
I now have two working openSUSE ARM images. For the Pandaboard and the
Toshiba AC100.
I wonder if we have a location where these images can be put so people who
want to test or help out the openSUSE ARM project?
These images can be used for a local native (osc/kiwi) build.
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,
On my BeagleBoard xM, I did a zypper up and while installing libgdk_pixbuf-2_0-0-2.26.0-1.2 I got this warning/error:
********************************************************************************
Installing: libgdk_pixbuf-2_0-0-2.26.0-1.2 [done]
Additional rpm output:
g_module_open() failed for /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: /usr/lib/libxml2.so.2: unexpected reloc type 0x03
********************************************************************************
Is it a known problem?
I think it may lead to problems for apps using this lib.
Regards,
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Here is a mail received on -kernel list about ARM configs.
Guillaume
-------- Message original --------
Sujet: [opensuse-kernel] master armv7l configs
Date : Fri, 27 Apr 2012 10:32:23 -0400
De : Jeff Mahoney <jeffm(a)suse.de>
Pour : openSUSE Kernel <opensuse-kernel(a)opensuse.org>
Copie à : Andrew Wafaa <awafaa(a)opensuse.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all -
When I merged 3.4-rc1, I disabled ARM builds. I'd like to re-enable
them now, but have no idea what the ARM guys want for config options.
Can someone go through and sync the configs up and send a patch/pull
request for the new configs that also enable armv7l in config.conf?
Thanks.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJPmq33AAoJEB57S2MheeWy2poP/2TF3CWppk2dvZdN9Sahoceu
D2Z6I2FTUzyAHpMcl/vEkKRoE9PyOwqRJT+bS1UX2uHqGrO4Sf3RP8RyAmflpTws
zAs5ESdCho0u6bwUxEmx5erMAfvFwIH5IFXhmPpuWDymym9xxMxzrK24+toUwCAt
u8e6sLETqW5jqD7kStA1xTRu5/jrB6Nu8/AkAZDG9GEm8gr2lEg0cfUMUOPbmk2l
42c1QjwHLlJNhSAXAgHpxFwjht4JuviJEraDpSFJlnk4yozMiI3cTkAeuY/iBRmu
9j5e4M6FHuWCjUOoZ6M2nBBmEz/FMSdtRmgg7vfYTOgkNc1Bire4M2SIcnlXihES
jNs/i/AgD37fFGUyGsUrQ7pp35lMi1xTQr4dfzYiYn5vWEHFD1Dv0hP9SNQjrQrm
0JreL5GZdxE3tcnOP95Tt/jMxgITOZe4EqB/rci7HbU5o4Z+oxkFlYRb+v+FSD63
MksZUS5WzCBsIXz2sgUyj1+9TP75ujBgT359KFCzOyXiMZD2416+kS7as9adG4AU
axxTavEUDETE5fiKPsBuX8cp5Ctyw3dAKF5hCC/OVjcBGY4qNnt5DTZYR42moh+9
a8vG/DVO4UiOrJh6F7AwBSH7PWwwNNVjsZaToKakThbCqwX3XDcVxCjsLiIQqbgF
YhL/Zn7sN9dUvy2ku45b
=PrwQ
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-kernel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-kernel+owner(a)opensuse.org
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Howdy y'all,
maybe you know about "People of openSUSE", a series of the news team to
introduce openSUSE people to our users and news-readers.
As ARM is one of the buzz words in the IT world this year, it might be
interesting to hear something about our ARM team and what your doing in
general.
I planned to to a People of openSUSE special, and if you're interested,
I'd be very glad to send you some questions to answer.
kind regards,
--
Kim Leyendecker, openSUSE Wiki Team
GPG Key: 664265369547B825 | leyendecker(a)opensuse.org
http://www.opensuse.org - Linux for open minds
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
Hi all,
I see that davocot12 fails to build for arm. The newer version of dovecot
dovecot20 builds without a problem.
I wonder if I also can use "ExcludeArch: %arm" for dovecot12, as a newer
working alternative exists.
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 all,
I wonder if it wouldn't be better to disable building all gcc compilers <
4.6 for ARM.
I see that they fail to build and they use build capacity. I don't think
these compilers won't be fixed for ARM anyway?
I don't think that they will be used?
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 all,
I've just checked out why v8 fails for ARM.
If fails with the following rpmlint error:
<quote>
RPMLINT report:
===============
(none): E: badness 10000 exceeds threshold 1000, aborting.
libv8-3.armv7l: E: shlib-policy-name-error (Badness: 10000) libv8preparser3
Your package contains a single shared library but is not named after its
SONAME.
</quote>
For the x86 factory build it doesn't, the packages are created without a
problem.
Might it mean that the rpmlint for ARM is different for ARM?
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,
Builds from my home project fail. With a simple build (gcc devmem2.c -o devmem2), I get the following error:
|gcc: error trying to exec 'cc1': execvp: No such file or directory|
Maybe due to errors while gcc 4.7 switch? Or incomplete rebuild?
Regards,
Guillaume
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
That sounds like a great way to use real ARM boards for OBS. Does anyone feel like giving it a try? :)
Alex
Begin forwarded message:
> From: Anup Patel <anup(a)brainfault.org>
> Subject: [Android-virt] [ANNOUNCE] [OFFTOPIC] Xvisor ARM with and/or without virtualization extensions
> Date: 24. April 2012 15:36:34 MESZ
> To: linux-arm-kernel(a)lists.infradead.org, linux-kernel(a)vger.kernel.org, android-virt(a)lists.cs.columbia.edu, beagleboard(a)googlegroups.com, xen-arm(a)lists.xensource.com
>
> Xvisor (eXtensible Versatile hypervISOR) is an open source bare-metal
> monolithic hypervisor, which aims towards providing virtualization solution,
> which is light-weight, portable, and flexible with small memory foot print
> and less overhead. It is distributed under GNU Public License (GPLv2).
>
> Xvisor has most of the features expected from a modern full-fledged hypervisor,
> such as:
> - Tree based configuration
> - Tickless and high resolution timekeeping
> - Wall-clock for tracking real-time
> - Threading framework
> - Host device driver framework
> - CPU virtualization
> - Address space virtualization
> - IO device emulation framework
> - Pass through hardware access
> - Dynamic guest creation/destruction
> - Serial port virtualization
> - Management terminal
>
> The ARM port of Xvisor (or Xvisor ARM) supports a wide range of ARM processors
> namely:
> - ARM9 (Boards: VersatilePB)
> - Cortex-A8 (Boards: Realview-PB-A8)
> - OMAP3 (Boards: BeagleBoard-xM)
> - Cortex-A9 (UP) (Boards: Vexpress-A9)
> - Cortex-A15 (UP) Without VE (Boards: Vexpress-A15)
> - Cortex-A15 (UP) With VE (Boards: Vexpress-A15)
>
> For all supported ARM processors Xvisor ARM is able to boot multiple unmodified
> Linux-3.0.4 guest with a fairly interactive and smooth Busybox 0.19.2 console.
>
> On real hardware specifically BeagleBoard-xM (OMAP3 @ 600 MHz) we get near
> native CPU performance (i.e. Native Linux 3.0.4 gives 1120 DMIPS whereas Linux
> 3.0.4 running as guest on Xvisor ARM gives 960 DMIPS)
>
> Please try out our Xivsor Cortex-A15 demo on ARM Fast Models 7.0 and/or
> Linaro QEMU (2.02 or higher). To download the demo tarball visit:
> https://docs.google.com/open?id=0B0ABS_s60oP_WjNQQ0QtUzNmdmc
>
> Xvisor is currently hosted on Github, to clone or download source code please
> visit following links:
> Wiki: https://github.com/xvisor/xvisor/wiki
> Mainline Repository: https://github.com/xvisor/xvisor
> Stagging Repository: https://github.com/avpatel/xvisor-next
>
> Our developer mailing list is xvisor-devel[at]googlegroups[
> dot]com, please feel free to post your queries or join our development
> mailing list.
>
> _______________________________________________
> Android-virt mailing list
> Android-virt(a)lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/android-virt
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org
After booting my Pandaboard ES (image "LimeJeOS-openSUSE-Factory-ARM-panda.armv7l-1.12.1-Build10.1.raw") there is no
wlan0 device. Regarding to the information here <http://elinux.org/Panda_How_to_kernel_3_2_rcx> there should be a wl12xx
driver, but "modprobe -l" does not list such a driver.
Is this a known issue?
Regards
endym
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-arm+owner(a)opensuse.org