How can I get and install build-essentials and kernel-headers using wget?

Hi,
I have a small embedded system running 2.6.30.2 Linux kernel. I would like to build a couple of device drivers. The system is using a built from scratch kernel. For this reason no 'apt-get' is available. The apt tools are what I usually depend on to manage packages. Without the tool how can I create a build environment? I do have network connectivity the 'wget' tool on the system. No windowing manager is yet loaded.

Thanks in advance for your replies,

Zoanie

Are you developing on another system? If so you can use aptitude to download the *.deb and then install with dpkg.

Or just go to the website and download the *.deb (or wget the address). What distro is this anyway (ubuntu, debian, or other debian based)?

Originally Posted by pljvaldez Are you developing on another system? If so you can use aptitude to download the *.deb and then install with dpkg. Or just go to the website and download the *.deb (or wget the address). What distro is this anyway (ubuntu, debian, or other debian based)?

Hi pljvaldez,
I am developing on an Unbuntu disto. I built the embedded target system using buildroot (www.buildroot.org). I've had some problems getting the buildroot system to load a package manager. I tried to load portage (www.gentoo.org) but it complains about the install. The target does not have dpkg available.

zoanie

Well, that's much beyond my expertise. I though it would be as easy as downloading the binaries manually and installing them. Sorry I can't be of any more help.

Originally Posted by pljvaldez Well, that's much beyond my expertise. I though it would be as easy as downloading the binaries manually and installing them. Sorry I can't be of any more help.

Ouch! - I am way hosed.... I'm working on the assumption that everything will work out if I forget about the buildroot shtuff, download a kernel on the target, then (make xconfig; make; make modules; make modules_install). The target is a resource limited PC/104 board with an anemic 486 processor. That is the reason for using buildroot in the first place. The other way I'm thinking about is to use the 'chroot' utility and somehow still be able to build a system on my workstation.