On Wed, Nov 01, 2006 at 09:20:00PM +0100, Luca wrote: > Hi Vladimir, > I didn't send the output of the set command simply because I'm not at > home and I don't have remote access to my pc from the house of a friend > of mine... [...] > I was modifying some things because I'm working on a automation build > process of system plus creating live and installation isos (CD and DVD). > I've set a general config.cache file that is loaded before each package > configure process and set other dirs like tools.cross, tools.chain, > tools.native etc... So, there is at least a possibility that something in your scripts is wrong. I've got difficulty imagining why a general config.cache would be useful, but each to his own. However, you _are_ deviating from the book (three sets of tool directories), so things can break in unexpected ways. I'm reminded of people who decided not to build the first part of LFS in /mnt/lfs/tools - from time to time they get strange breakages because /tools has been hardcoded into patches.
I strongly recommend you do what I suggested yesterday - try to configure texinfo in the normal way so that it fails, then look at the appropriate config.log (without going back through the thread, I don't know if it's the top level config.log or one in a subdirectory) and look at the results which caused the error message. It might be embarrassing (I've had my share of these, such as passing -mpcu=7450 to a cross-compile for x86), it might be specific to your variations, or it might be something that other people will hit (maybe even a problem with the book). It's that last possibility that really concerns me, plus the opportunity for you to learn how to debug configure problems. Ken -- das eine Mal als Tragödie, das andere Mal als Farce _______________________________________________ Clfs-support mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-support
