Hi ppl,
My basic idea is to have chroot-ed environment which will be the full
system and then to install separate system with only minimal stuff
(without gcc, portage, ...). When I need to update the minimal system I
will first update the chrooted one and the emerge the updates onto the
new
forgottenwizard wrote:
On 19:42 Thu 27 Sep , Petar Dimitrijevic wrote:
Hi ppl,
My basic idea is to have chroot-ed environment which will be the full
system and then to install separate system with only minimal stuff (without
gcc, portage, ...). When I need to update the minimal system
Andreas Niederl wrote:
Hi,
Petar Dimitrijevic wrote:
Hi ppl,
My basic idea is to have chroot-ed environment which will be the full
system and then to install separate system with only minimal stuff
(without gcc, portage, ...). When I need to update the minimal system I
will first update
forgottenwizard wrote:
On 23:04 Thu 27 Sep , Petar Dimitrijevic wrote:
forgottenwizard wrote:
On 19:42 Thu 27 Sep , Petar Dimitrijevic wrote:
Hi ppl,
My basic idea is to have chroot-ed environment which will be the full
system and then to install separate system
Neil Bothwick wrote:
On Fri, 28 Sep 2007 00:51:45 +0200, Petar Dimitrijevic wrote:
I'm not cross compiling. I'm compiling the packages on i686 arch for
i686 arch.
The C3 is i586 not i686. Compile for i686 and it will crash. I built a
system booting from CF on an Epia board and I used
Andreas Niederl wrote:
Petar Dimitrijevic wrote:
Andreas Niederl wrote:
[...]
Note, that you have to include libstdc++.so yourself if you're not
emerging gcc into your /install.
You mean just to copy libstdc++.so to /lib or emerge libstdc++ ?
[...]
Just copy
6 matches
Mail list logo
