Re: silo fails to build with recent ext2fs libraries

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



From: Jurij Smakov <jurij@xxxxxxxxx>
Date: Wed, 18 Jan 2012 00:20:08 +0000

> On Tue, Jan 17, 2012 at 01:51:51PM -0500, David Miller wrote:
>> From: David Miller <davem@xxxxxxxxxxxxx>
>> Date: Tue, 17 Jan 2012 12:56:56 -0500 (EST)
>> 
>> > I'm looking into the rest.
>> 
>> So just adding the stubs (or your idea, linking with libc) doesn't
>> work at all.
>> 
>> All the new features in libext2 that get linked in cause the second
>> stage bootloader image to grow too large.
>> 
>> I'll just have to extract the parts of libext2 that we actually need
>> into a stripped down local copy in SILO and I guess this will make
>> us immune to this issue showing up again in the future.
> 
> If you haven't put too much effort into it yet, can you give me a 
> few days to experiment with dropping unnecessary symbols from the 
> built library using objcopy? If it turns out to be simple, I'd rather 
> use this than duplicating code.

We've been fighting this problem for years, it only gets worse and
all of these various hacks are error prone.

The only real solution is to write something made for a bootloader and
that's what I'm already doing.  The code isn't that hard at all.

--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux