[ale] Slackware v10.2 compile woes
Bob Kruger
bkruger at mindspring.com
Mon Oct 24 13:03:57 EDT 2005
Interestingly, last night after all was settled, I put a mirrored Slack v7.1 HD back in the old system, and it ran and compiled just fine. Ahhh, the days when a 6.4G HD was all you needed...
Memory was fine, video was fine. Compiled Samba, PHP, and the 2.4.28 kernel without a hitch.
I now think that the problem was just a matter of hardware incompatibility with the newer version of GCC. Regardless, the Slack 10.2 HD now sits in a newer machine.
On an interesting side note, this whole episode goaded me into trying Gentoo 2005 v1. The setup could have been easier, but it is running on an older P600 with no problems. Once running, it has no vices that I can see. In fact, I am getting less errors when compiling library files using -shared than with Slack. One thing I did notice, as this was my first time compiling the kernel. It appears as if the the "make modules" command is no longer needed with kernel 2.6.x, as a simple make compiled all the kernel modules for me.
Intersting. Sort of reminds me of Slackware before Slack got a little bloated...
V/r
Bob
> On 10/23/05, *James P. Kinney III* <jkinney at localnetsolutions.com
> <mailto:jkinney at localnetsolutions.com>> wrote:
>
> Ah ,hardware. If I recall, the hard drive choked on that syustem that
> was running 7.1. I suspect that a reinstall of 7.1 will still not
> allow
> compilations. A board level voltage spike caused by a dying power
> supply
> can damage RAM in subtle ways while cooking other parts like hard
> drives.
>
> It's VERY frustrating to realize that the one component that can kill
> everything in the system is being produced to lower and lower
> lifetime
> expectancy standards. Some of my older equipment is running just fine
> after 7-8 years of daily use while some of the newer stuff is good for
> 1-2 years tops. Most of the system failures I have seen in the past 3
> years have been caused by an intermittent power supply issue. Poor
> quality analog components like capacitors and choke coils are to blame
> for the vast majority of the crappy power supplies that have broken my
> and my clients stuff.
>
> It doesn't help that everyone wants to "save money" so the power
> supply
> installed is the smallest capable of just running the box as
> shipped. So
> add a DVD burner to that old system and play Russian Roulette with
> your
> hard drive. Power supply makers rate their device to the absolute
> maximum it could possible put out assuming all the components are
> fully
> up to spec and the bean counters didn't by a bargain that "fell of
> the
> truck". The sad reality is power supplies don't put out what their
> label
> says except for a very brief test time.
>
> So I size up my power supply to provide full power for every device
> running at maximum and still have at least a 30% overhead before the
> labeled rating is hit. I would much prefer a 50% overhead but newer
> systems are already such power hogs I can't get a 2kw internal power
> supply!
>
>
> </rant>
>
> On Sun, 2005-10-23 at 16:42 -0400, Bob Kruger wrote:
> > James;
> >
> > I have pretty much decided that the problem is hardware induced. I
> > just pulled the HD with the Slack 10.2 distro in it, put it in
> another
> > machine, and I can compile to my heart's content. The old
> motherboard
> > had no problems with Slack 7.1 - it peacefully ran for four years.
> > But, it will not peacefully coexist with Slack 10.2. Its time has
> > come and gone.
> >
> > Thanks all who wrote back.
> >
> > V/r
> >
> > Bob
> >
> > James P. Kinney III wrote:
> > > On Sun, 2005-10-23 at 15:32 -0400, Bob Kruger wrote:
> > >
> > > > Christopher;
> > > >
> > > > Fair enough. The three shown here are "segmentation
> faults" Here are
> > > > some snippets. Firstly, compiling samba 3.0.22b:
> > > >
> > >
> > > I'm not running slack 10.2. Nor have I had compilation issues
> with the
> > > slack machines I do have.
> > >
> > > However, I have seen seg faults during compiles. 2 were memory
> faults
> > > (RAM was bad in ways that only a compiler would find or
> memtest86) and 2
> > > were bad applications configures. On one of the bad app
> configs, I had
> > > to do a lot more than just ./configure; make; make install.
> There were a
> > > bunch of settings I had to tweak.
> > >
> > > Samba, MySQL and PHP are monster applications that usually
> need much
> > > more than the vanilla ./configure to make correctly.
> > >
> > >
> > >
> > >
> ____________________________________________________________________
> > >
> > > _______________________________________________
> > > Ale mailing list
> > > Ale at ale.org <mailto:Ale at ale.org>
> > > http://www.ale.org/mailman/listinfo/ale
> >
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org <mailto:Ale at ale.org>
> > http://www.ale.org/mailman/listinfo/ale
> --
> James P. Kinney III \Changing the mobile computing world/
> CEO & Director of Engineering \ one Linux user /
> Local Net Solutions,LLC \ at a time. /
> 770-493-8244 \.___________________________./
> http://www.localnetsolutions.com
>
> GPG ID: 829C6CA7 James P. Kinney III (M.S . Physics)
> <jkinney at localnetsolutions.com <mailto:jkinney at localnetsolutions.com>>
> Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
>
> iD8DBQBDXAJYYZCtw4KcbKcRArc7AJ9R30acpPJvZzOHi5MQYWUc9YzAAACgtutL
> Y6awP/ESO0fCXMABAQiWbqk=
> =ZVsd
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org <mailto:Ale at ale.org>
> http://www.ale.org/mailman/listinfo/ale
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Ale mailing list
>Ale at ale.org
>http://www.ale.org/mailman/listinfo/ale
>
Probably made in China by some 5 yr old kid.................................
_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale
More information about the Ale
mailing list