ct-ng is moving rapidly on, how do we keep it useful?

[twobob]

hmm. I have python. now Im confused.

[NiLuJe]

Do you still have the build.log of the failed build?

[twobob]

I can fail another



EDIT: doh - have to be later. gotta go. BBL

[twobob]

Hokay. This TC is not doing the business. spits out 2.7 calls?

I'll have another play and check my work is as it should be but definitely getting wrong output

[NiLuJe]

@twobob: Depending on what the exact symbols you're getting are, it might need some more CFLAGS massaging . (Or... more intrusive work. It's not perfect, I know. It works pretty well for what I do, but for a fully automated system with a broad choice of packages, it might be too much work... )

[twobob]

I was thinking of a "watered down" version.

If I could get something that was much closer to the 2007 q3 CS TC offering it would probably have more value in the Buildroot context.

so perhaps the question should be:

"ct-ng is moving rapidly on, how do we keep it usefully similar to the kindle 3?"

I believe Hawhill uses ct-ng also - I will perhaps give him a nudge and ask him for a config. Happy to put in the work to document the best practices. Guess I will go through the options again - from the beginning.

Thanks Niluje

[NiLuJe]

@twobob: One way to do that, while keeping the tricks to a minimum, and still using a decent GCC version, would be to find the latest GCC version that can be used to build glibc 2.5. (It's still in ct-ng, IIRC. if not, it's pretty easy to fix, since it was at one point ).

I don't *think* it builds properly with GCC 4.7, but I might be wrong, been a while since I tried.

[twobob]

Originally Posted by NiLuJe

@twobob: One way to do that, while keeping the tricks to a minimum, and still using a decent GCC version, would be to find the latest GCC version that can be used to build glibc 2.5. (It's still in ct-ng, IIRC. if not, it's pretty easy to fix, since it was at one point ).

I don't *think* it builds properly with GCC 4.7, but I might be wrong, been a while since I tried.

okay. that's on my todo list then thanks

http://www.kegel.com/crosstool/cross....43/buildlogs/ is a nice list

[thatworkshop]

So twobob, NiLuJe, knc1, geekmaster (maybe? he's away I guess ), what's your preference for x-compiling?
I like ct-ng.

[knc1]

Originally Posted by idoit

So twobob, NiLuJe, knc1, geekmaster (maybe? he's away I guess ), what's your preference for x-compiling?
I like ct-ng.

crosstool-ng project is dead.
Its author, Yann E. Morin, is putting in his free time working on Buildroot.

Note: Even the crosstool-ng backend of Buildroot has been pulled (by Morin) rather than continue to maintain it.

There is a fairly recent thread on x-compiling preference's here.
Hmm....
I think Aries started the thread.

[NiLuJe]

Still using ct-ng .

Cf. kindle-x-tc-2013.10.N.tar.gz in https://www.mobileread.com/forums/showthread.php?t=88004, it contains (among other things) my ct-ng patches & configs.

[thatworkshop]

Originally Posted by NiLuJe

Still using ct-ng .

Cf. kindle-x-tc-2013.10.N.tar.gz in https://www.mobileread.com/forums/showthread.php?t=88004, it contains (among other things) my ct-ng patches & configs.

Thanks knc1.
Wish I knew this yesterday man! I didn't realize ct-ng is dead!!! Recent version seems really recent! 2013-10-02
Yesterday, I opted for ct-ng instead of exactly Buildroot!!! Buildroot is backed up by ulibC? And it uses ct-ng too.

Thanks NiLuJe, spent long hours on building ct-ng, I guess I'll keep it. Question is: I used the sample arm-unknown-linux-gnueabi. That'll do for Kindle (esp. Kindle 3 in mind) right?

[thatworkshop]

By the way, NiLuJe, I strongly suggest you ask mods to change the title of that HUGE thread to: USBNetwork, Font & ScreenSaver Hacks for Kindles 2.x, 3.x & 4.x
which is just reordering of them. The reason is for newbies to this forum, they come to jailbreak their device... next word they learn is USBnetworking. See? The previous title doesn't emphasize on how important and basic this thread is.

[knc1]

Originally Posted by idoit

Thanks knc1.
Wish I knew this yesterday man! I didn't realize ct-ng is dead!!! Recent version seems really recent! 2013-10-02
Yesterday, I opted for ct-ng instead of exactly Buildroot!!! Buildroot is backed up by ulibC? And it uses ct-ng too.

Thanks NiLuJe, spent long hours on building ct-ng, I guess I'll keep it. Question is: I used the sample arm-unknown-linux-gnueabi. That'll do for Kindle (esp. Kindle 3 in mind) right?

Part of the removal of the old "back end" toolchain feature from Buildroot was the conversion of the toolchain generation into true "packages".

Currently only three (with one more a "WIP") uClibc, glibc and eglibc toolchains can be selected.

Yann does do 'bug fixing' as time is available, but that is expected (by Yann) to become less and less over time.
(I am paraphrasing Yann comments over time on the BR mailing list.)

[thatworkshop]

Originally Posted by knc1

Part of the removal of the old "back end" toolchain feature from Buildroot was the conversion of the toolchain generation into true "packages".

Currently only three (with one more a "WIP") uClibc, glibc and eglibc toolchains can be selected.

Yann does do 'bug fixing' as time is available, but that is expected (by Yann) to become less and less over time.
(I am paraphrasing Yann comments over time on the BR mailing list.)

I'll switch to Buildroot. Plan: Get Arch Linux ARM with awesome wm up and running on this lttle thingie.

P.S. Man "awesome" is really awesome! I'm in <3.

P.S.S. Did anyone notice, I'm gradually leaning more towards K3 than Touch devices! That doesn't look normal!!!