Bug#696909: chromium segfaults on startup on armhf

[shawnlandden]

It works when built with gold 2.23 on an armv6+ hardware host (bug 696284). 
This bug is also a dup, and was njotriced shortely after chromium 22 was made 
to build again on arm (ftbfs since chromium 18) due to my patches.

peter green  wrote:

>Note: adding debian-arm to cc for feedback from other porters.
>
>Jonathan Nieder wrote:
>> Hi Peter,
>>
>> peter green wrote:
>>
>>   
>>> Patch to make the package use bfd rather than gold on armel and
>armhf is
>>> attached. I may or may not upload this as a NMU.
>>> 
>>
>> If you'll have time to continue working on chromium:arm in the
>future,
>> it would probably be better to just add yourself to pkg-chromium on
>> alioth
>Like any other package if chromium gives us problems over in raspbian I
>
>will try to get those problems fixed and will contribute what I
>discover 
>back to debian where appropriate but I don't have any real knowlege of 
>chromium's internals or build system nor do I have the time or 
>inclination to learn them.
>
>Anyway I have some bad news. When I try to do an armel build with bfd
>on 
>my imx board I get.
>  LINK(target) out/Release/chrome
>/usr/bin/ld.bfd.real: failed to set dynamic section sizes: Memory
>exhausted
>collect2: ld returned 1 exit status
>
>I have plenty of swap so i'm pretty sure the real problem is not memory
>
>per-se but address space. I had the same problem with the raspbian
>build 
>(but not with the debian armhf build) and for raspbian I worked arround
>
>it by building with user mode qemu on an x64 host (which provides 
>significantly more virtual address space than any real arm system) but 
>i'm not sure that is acceptable for debian.
>
>Thoughts on what to do for chromium on armel? leave it broken? drop it 
>completely? upload packages built with bfd under user mode qemu 
>(assuming that succeeds and produces usable packages) to the archive?
>
>
>-- 
>To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org
>with a subject of "unsubscribe". Trouble? Contact
>listmas...@lists.debian.org
>Archive: http://lists.debian.org/50f46ff0.6080...@p10link.net

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Bug#696909: Dup

[shawnlandden]

This is a DUP of 680566. You can't just use bfd without memory saving options 
cause the link can use more than 2gb addressable limit on arm boxes without 
pae. Gold 2.23 builds chromium correctly. (But not on armel without workarounds 
due to bug 696284)
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

Bug#697404: ITP: libnxt -- Simple command-line tool for Lego NXT

[shawnlandden]

Slavko  wrote
>   Package name: libnxt
>Version: 0.3
>Upstream Author: David Anderson 
>URL: http://code.google.com/p/libnxt/
>License: GPL
>LibNXT is an utility library for talking to the LEGO Mindstorms NXT
>intelligent brick at a relatively low level. It currently does:

>The package provides two binary files:
>
> * fwexec to upload image file to NXT brick and then execute it
> * fwflash to flash firmware image to NXT brick
>
Are you sure no other programs out there use these binary names in the path? 
These seem far too general for a program that only flashes NXT bricks

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#667077: Update

[shawnlandden]

Damian,

Can you post your work on this so that I can do some work that depends on this 
without replicating your work?
-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.