On Fri, Jan 09, 1998 at 02:13:41AM +0200, Neilen Marais wrote:
> But IMHO its silly keeping seperate headers... Why not just leave the
> links to /usr/src/linux/include? /usr/src/linux is anyway the standard
> location for the kernel, and it makes sense to always use your current
> kernel's header
>kernel-source package that libc6-dev depends on is going to be
>available
>this week, or alternatively, can I *safely* force the libc6-dev to
>install with 2.0.32_2.0.32-1 kernel source?
Yeah, sure, just make sure /usr/include/linux is a symlink pointing to
/usr/src/linux/include/linux, and that
go and get the latest 2.0.32-3 from dists/unstable/main/binary/devel
and give you a nice install
good luck
kusuma
Damir J. Naden wrote:
>
> Yes, I did exactly that: put both packages on the same dpkg --install
> line (thanks to Scott Ellis for responding within an hour of my original
> post). E
On Mon, 5 Jan 1998, Damir J. Naden wrote:
> Yes, I did exactly that: put both packages on the same dpkg --install
> line (thanks to Scott Ellis for responding within an hour of my original
> post). Everything installed cleanly and the system works as expected.
> Next hurdle seems to be installing
Yes, I did exactly that: put both packages on the same dpkg --install
line (thanks to Scott Ellis for responding within an hour of my original
post). Everything installed cleanly and the system works as expected.
Next hurdle seems to be installing of the libc6-dev to be able to
compile my own kerne
Yes Remco is right, I have not tried it thou.., give it a try... and
good luck
kusuma
Remco Blaakmeer wrote:
>
> On Tue, 6 Jan 1998, Wiria A Kusuma wrote:
>
> > ok, I do it this way, after the ldso_1.9.6-2.deb, I do
> > dpkg -i libc5_5.4.38-0.1.deb, of couse it is complaining about libc6,
> > j
On Tue, 6 Jan 1998, Wiria A Kusuma wrote:
> ok, I do it this way, after the ldso_1.9.6-2.deb, I do
> dpkg -i libc5_5.4.38-0.1.deb, of couse it is complaining about libc6,
> just ignore it, and leave it unconfigure..., then do a dpkg for
> libc6_2.0.6-2.deb, I am sure you will be able to do it thi
ok, I do it this way, after the ldso_1.9.6-2.deb, I do
dpkg -i libc5_5.4.38-0.1.deb, of couse it is complaining about libc6,
just ignore it, and leave it unconfigure..., then do a dpkg for
libc6_2.0.6-2.deb, I am sure you will be able to do it this time, then
you can go back to dpkg -i libc5_5.4.3
ok, I do it this way, after the ldso_1.9.6-2.deb, I do
dpkg -i libc5_5.4.38-0.1.deb, of couse it is complaining about libc6,
just ignore it, and leave it unconfigure..., then do a dpkg for
libc6_2.0.6-2.deb, I am sure you will be able to do it this time, then
you can go back to dpkg -i libc5_5.4.3
On Sun, 4 Jan 1998, Damir J. Naden wrote:
> I have spent last hour going thru the mailing list archives and still
> came out empty-handed:
> I have installed a base system froma the current base disks from hamm
> which point to the current bo disks. Those include libc5_5.4.33-6
> library. Next ste
Hi, everyone --
I have spent last hour going thru the mailing list archives and still
came out empty-handed:
I have installed a base system froma the current base disks from hamm
which point to the current bo disks. Those include libc5_5.4.33-6
library. Next step was to try and upgrade to ldso_1.9
11 matches
Mail list logo
