Quote:
Originally Posted by knc1
GLIBC_2.0 ???
Are you building these tool-chain generations or using pre-built ones?
In either case - -
Is there a chance that glibc is never getting re-downloaded and re-built?
Since everything is dependent on the tool-chain - a "make clean" on the entire Buildroot system is required when making a change to the tool-chain.
Even when just selecting a different external tool-chain.
I am sorry that I can't be running these Buildroot builds in parallel with you - but I am still trying to solve some local problems in getting a new RAM kernel built.
|
dont think so. I utterly delete the output folder. and start again.
that pretty much nerfs all known BR foofs.
as for the 2.0.. I probably just didn't search the right things as my test clearly show that 2.7 occurs in the 2008q3 TC and my obviously errantly located search did not reflect that fact.
well one more build with q1 then I will be sure...