例のEmbedded uClibc GentooなGeodeは一応bootした.
シリアルコンソールとかFrame BufferとかdropbearなSSHとか,
まだ/etc以下の調整が必要也.
man, info, doc抜きで,展開したkernelのソース,ebuildのツリー,
Portageのキャッシュをお掃除して,self update/debugが最低限可能な様に
toolchainとGentooなバイナリを残した状態で大体,300MB弱になった.
runtime環境で必要十分な状態...
詰まり,ヘッダファイルや普段使わないライブラリやら
バイナリやらを整理すれば,100MB以下にする事も出来るケド,
わざわざbinpkgを作るのは性に合わないので,
ベースにするrootfsで無理なダイエットはしないつもり. :)
[The Geode one tentative boots w/ embedded uClibc Gentoo.
But, it needs more pokings for serial console, frame buffer, dropbear SSH or so
which are configured by /etc files.
No man/info/doc stuffs,
cleaning extracted kernel sources/ebuild tree/Portage cache,
to make it keep to update/debug itself, leaving tool chain and gentoo's utils.
Now, its size is about 300MB or so.
Of cource, really iif runtime env which is not madantory ton of headers,
unneeded libs, not normally bins.
And yes, it's not quiet difficult to reduce the size less than 100MB.
But to make binpkg myself is not my taste, duh.
So hardly diet for my base rootfs isn't sane, IMHO. :)]
で,sys-apps/pcmcia-csやらsys-apps/pcmciautilsを弄っていたら,
dev-utils/yaccとsys-devel/bisonでcollision-protectにハマる.
profileのsystemで入ってくるsys-devel/bisonを-yオプション付きで使えば,
YACC compatな動作をするので,dev-util/yaccを入れる必要は無いハズ.
今の所,virtual/yaccが無い所為でdev-util/yaccに直接DEPENDしてる. :(
#gentoo-dev-help@FreeNode.netで訊いてみると,
YACC compatなブツは四つ以上有るらしい.
後でbugzillaに貼っとくか,メモメモ. :P
[BTW, when poking sys-apps/pcmcia-cs and sys-apps/pcmciautils,
dev-util/yacc and sys-devel/bison have file collision for these bad dependencies.
These PCMCIA packages have dev-util/yacc as directly DEPEND atom,
but sys-devel/bison was emerged as one of system profle stuffs,
and then "bison -y" is YACC compat, though.
So, it's the fault of no virtual/yacc ATM.
According to #gentoo-dev-help guy,
4 or more YACC compat ones in official ebuild tree.
Hmm, this memo will remind me to need to file virtual/yacc RFC to bugzie. :P]
O HAI THIS BLOG PURPZIEZ 2 B UZED AZ MAH PLESIOUS MEM. :)
0 件のコメント:
コメントを投稿