Prev: running an app on remote X
Next: iptables LOG not in syslog
From: Mikhail Zotov on 13 Apr 2010 04:34
On Mon, 12 Apr 2010 23:25:12 +0300
Timothy Madden <terminatorul(a)gmail.com> wrote:

> William Hunt wrote:
> > On Sun, 11 Apr 2010, Dan C wrote:
> >> On Sun, 11 Apr 2010 13:47:13 +0300, Timothy Madden wrote:
> >>> Is there a way for me to create a Slackware DVD that I compiled
> >>> from sources with my CFLAGS and CXXFLAGS, that I could then
> >>> install Slackware from, so I would have all my OS compiled for my
> >>> CPU ?
> >> Sure. The entire source is available from any Slack mirror.
> >> Get started.
> >
> > ... by looking in ./source/*.tar.gz and studying the SlackBuild
> > scripts, about 240 or so. maybe compare the standard base
> > against a 64 bit version for more clue. That's just the start
> > of it, Common oppinion seems to be that any benefit gained is
> > outweighed by the effort required.
> >
>
> Is there a script to compile all packages with one command ?

No.

> Ok I know compiling the kernel is not configured with CFLAGS, but I
> already have the kernel compiled, so what I want is to compile all
> the other packages.

One can get an idea about the order packages should be compiled
by studying UPGRADE.TXT available in the root of the distro tree.
A deeper understanding can be obtained from Linux-From-Scratch-HOWTO
and Linux From Scratch Guide available at http://tldp.org/guides.html

--
Mikhail

P.S. IMHO, recompiling Slackware `from scratch' can be an interesting
exercise but will most likely be a waste of time.

From: Sylvain Robitaille on 16 Apr 2010 01:46
Mikhail Zotov wrote:

> A deeper understanding can be obtained from Linux-From-Scratch-HOWTO
> and Linux From Scratch Guide available at http://tldp.org/guides.html

I second this suggestion.

When I was doing ASAP ("Another Slackware Alpha Port"; stalled for many
years, before I'd completed it for Slackware-10.0, but there is still an
official plan to revive the project using current sources), I used Linux
from Scratch to guide me as to the order to build things in, at least up
to the point that I had a self-hosting system (following which I just
went off and compiled things by software "subsets" ("l", "d", "n", "ap",
....)

> P.S. IMHO, recompiling Slackware `from scratch' can be an interesting
> exercise but will most likely be a waste of time.

Unless the goal is to have Slackware running on an architecture for
which it is not officially available. Not every computer has an x86 or
x86_64 compatible CPU.

--
----------------------------------------------------------------------
Sylvain Robitaille syl(a)encs.concordia.ca

Systems analyst / AITS Concordia University
Faculty of Engineering and Computer Science Montreal, Quebec, Canada
----------------------------------------------------------------------
From: Timothy Madden on 17 Apr 2010 12:43
Mikhail Zotov wrote:
> On Mon, 12 Apr 2010 23:25:12 +0300
> Timothy Madden <terminatorul(a)gmail.com> wrote:
>
>> William Hunt wrote:
>>> On Sun, 11 Apr 2010, Dan C wrote:
>>>> On Sun, 11 Apr 2010 13:47:13 +0300, Timothy Madden wrote:
>>>>> Is there a way for me to create a Slackware DVD that I compiled
>>>>> from sources with my CFLAGS and CXXFLAGS, that I could then
>>>>> install Slackware from, so I would have all my OS compiled for my
>>>>> CPU ?
>>>> Sure. The entire source is available from any Slack mirror.
>>>> Get started.
>>> ... by looking in ./source/*.tar.gz and studying the SlackBuild
>>> scripts, about 240 or so. maybe compare the standard base
>>> against a 64 bit version for more clue. That's just the start
>>> of it, Common oppinion seems to be that any benefit gained is
>>> outweighed by the effort required.
>>>
>> Is there a script to compile all packages with one command ?
>
> No.

Ok, at least is there a script or some way to automate compilation of
those hundreds of packages so I do not have to review each one by hand ?


Thank you,
Timothy Madden
From: Dan C on 17 Apr 2010 15:23
On Sat, 17 Apr 2010 19:43:43 +0300, Timothy Madden wrote:

> Mikhail Zotov wrote:
>> On Mon, 12 Apr 2010 23:25:12 +0300
>> Timothy Madden <terminatorul(a)gmail.com> wrote:
>>
>>> William Hunt wrote:
>>>> On Sun, 11 Apr 2010, Dan C wrote:
>>>>> On Sun, 11 Apr 2010 13:47:13 +0300, Timothy Madden wrote:
>>>>>> Is there a way for me to create a Slackware DVD that I compiled
>>>>>> from sources with my CFLAGS and CXXFLAGS, that I could then install
>>>>>> Slackware from, so I would have all my OS compiled for my CPU ?
>>>>> Sure. The entire source is available from any Slack mirror. Get
>>>>> started.
>>>> ... by looking in ./source/*.tar.gz and studying the SlackBuild
>>>> scripts, about 240 or so. maybe compare the standard base against a
>>>> 64 bit version for more clue. That's just the start of it, Common
>>>> oppinion seems to be that any benefit gained is outweighed by the
>>>> effort required.
>>>>
>>> Is there a script to compile all packages with one command ?
>>
>> No.
>
> Ok, at least is there a script or some way to automate compilation of
> those hundreds of packages so I do not have to review each one by hand ?

No.

I suggest you just give up your silly idea and get on with life.


--
"Ubuntu" -- an African word, meaning "Slackware is too hard for me".
"Bother!" said Pooh, as he turned the launch key.
Usenet Improvement Project: http://twovoyagers.com/improve-usenet.org/
Thanks, Obama: http://brandybuck.site40.net/pics/politica/thanks.jpg
From: Grant on 17 Apr 2010 16:46
On 17 Apr 2010 19:23:58 GMT, Dan C <youmustbejoking(a)lan.invalid> wrote:

>On Sat, 17 Apr 2010 19:43:43 +0300, Timothy Madden wrote:
>
>> Mikhail Zotov wrote:
>>> On Mon, 12 Apr 2010 23:25:12 +0300
>>> Timothy Madden <terminatorul(a)gmail.com> wrote:
>>>
>>>> William Hunt wrote:
>>>>> On Sun, 11 Apr 2010, Dan C wrote:
>>>>>> On Sun, 11 Apr 2010 13:47:13 +0300, Timothy Madden wrote:
>>>>>>> Is there a way for me to create a Slackware DVD that I compiled
>>>>>>> from sources with my CFLAGS and CXXFLAGS, that I could then install
>>>>>>> Slackware from, so I would have all my OS compiled for my CPU ?
>>>>>> Sure. The entire source is available from any Slack mirror. Get
>>>>>> started.
>>>>> ... by looking in ./source/*.tar.gz and studying the SlackBuild
>>>>> scripts, about 240 or so. maybe compare the standard base against a
>>>>> 64 bit version for more clue. That's just the start of it, Common
>>>>> oppinion seems to be that any benefit gained is outweighed by the
>>>>> effort required.
>>>>>
>>>> Is there a script to compile all packages with one command ?
>>>
>>> No.
>>
>> Ok, at least is there a script or some way to automate compilation of
>> those hundreds of packages so I do not have to review each one by hand ?
>
>No.
>
>I suggest you just give up your silly idea and get on with life.

Yes. I've tried Gentoo too ;) If recompiling slackware looked like a
good idea I'd have done it years ago. Simply no motivation.

I know from benchmarking stock kernel vs custom kernel there's little
performance gain to be had (~1% or 2%? ). Custom kernels have a win in
size and load time, and having the correct drivers to suit the hardware.
By necessity, the stock kernel tries to be very good for the majority
of machines and is thus generalised, at a slight cost to performance.

While it may pay to compile number-crunch9ing apps to suit the machine,
not the entire OS, just look at 'top' and see what's using the most of
CPU. Like caching, work on the 10% that is running 90% (or 5%/95%) of
the time, not the lot.

Grant.
--
http://bugs.id.au/
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: running an app on remote X
Next: iptables LOG not in syslog