silo fails to build with recent ext2fs libraries

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


Recently I've discovered that silo fails to build with recent ext2fs 
libraries. Debian bug report [0] shows the relevant part of the build 
log. Someone also reported the same problem on gentoo forum just a few 
days ago [1].

As far as I can understand, the problem arises because newer ext2fs 
library versions introduced additional symbols, depending on libc 
functions not implemented in silo, into the same object files which 
contain the symbols used by the second stage. Since linker operates on 
object file level, it pulls in these symbols along with needed ones, 
then fails to resolve their dependencies because they are not 
implemented in silo and we are not linking against libc.

I was hoping that I can create a reduced ext2fs library containing 
only necessary symbols, but later recognized that this would require 
compiling and maintaining an explicit list of such symbols and their 
dependencies, which would be pretty tedious and error prone. I've also 
tried pruning the symbols causing the failure from the original 
library, however it's not possible in some cases, as some of them are 
mentioned in relocation entries. Another option would be to start 
linking against libc to work around this problem, but I don't know why 
it was not done in the first place, some size constraints perhaps?


Best regards,
Jurij Smakov                                           jurij@xxxxxxxxx
Key:                      KeyID: C99E03CC
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at

[Linux MIPS Home]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite News]     [MIPS Architecture]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux