Hi Riku,
On Mon, Jun 04, 2012 at 09:59:14AM +0300, Riku Voipio wrote:
> > the fix is not to use the arm-specific code
> > path, but I'd like to test as it is there for a reason
>
> looking at the code, the only reason for the arm-specific code
> is speed. As far as I see, we can disable it safel
> the fix is not to use the arm-specific code
> path, but I'd like to test as it is there for a reason
looking at the code, the only reason for the arm-specific code
is speed. As far as I see, we can disable it safely for now.
Riku
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.
Hi,
I have a patch at [1] that fixes the build (tested on abel.debian.org).
However I had no time to verify that the fixed package (still) works on
actual armel hardware yet (the fix is not to use the arm-specific code
path, but I'd like to test as it is there for a reason).
Regards
Evgeni
[1]
I don't have any armel hardware to test this on, but I was really
hoping that 0.9.32-1 would build here as it builds on Ubuntu armel:
https://launchpadlibrarian.net/90887444/buildlog_ubuntu-precise-armel.notify-osd_0.9.32-0ubuntu5_BUILDING.txt.gz
-- Andrew Starr-Bochicchio
Ubuntu Developer
Source: notify-osd
Version: 0.9.23-2
Severity: important
User: debian-...@lists.debian.org
Usertags: eabi
Hi,
your package FTBFS on armel:
| CC notify_osd-egg-fixed.o
| gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. -I. -I. -I..
-DDATADIR=\""/usr/share"\" -pthread -I/usr/include/gtk-2.0
-I/us
5 matches
Mail list logo