* Mika Bostrom <[EMAIL PROTECTED]> [2006-08-30 00:34:24 +0300]: > tags: +moreinfo > > I may have discovered something. Unless I have misinterpreted this > badly, linux from scratch project has tripped over a very similar > problem late this spring. > > The following messages describe pretty much identical problem: > > http://www.mail-archive.com/[email protected]/msg05358.html > http://www.mail-archive.com/[email protected]/msg05368.html > http://www.mail-archive.com/[email protected]/msg05371.html > > They also describe one possible way to find a solution. This may be > a problem in auto*/libtool/whatnot toolchain versions and their > interdependent conflicts. I do not claim to understand how that > particular mess^Wtoolkit works, but at least I can hope that the > maintainer of the package manages. > > (If the second and third mail are to be believed, this could be solved > with a single 'libtoolize --force' invocation. But where should that > go?) > > Thanks, > > -- > Mika BostrĐ–m +358-40-525-7347 -=- The flogging will continue > [EMAIL PROTECTED] www.iki.fi/bostik -=- until morale improves > GPG: 0x039F188E; EC67 5B3A E6E3 6A84 9CB2 94D3 BFCD BD57 039F 188E
Actually I did run "relibtoolize -c -f" -f meaning "--force", which is used as a solution in those messages. So, it's not a solution in itself. There is something else going on here. Thank you for the information nevertheless. Regards, Alex.
signature.asc
Description: Digital signature
