I built an "optimized" Crux 2.4 using the following parameters:

export CFLAGS="-march=prescott -O2 -pipe -fomit-frame-pointer"
export CXXFLAGS="${CFLAGS}"
export MAKEFLAGS="-j3"

I then built core, opt and xorg and mastered an iso image per these
instructions:

http://article.gmane.org/gmane.linux.distributions.crux.general/2561/match=iso

The new system is up and running fine.

I'd like to do it this way instead:

http://crux.nu/Public/BuildingISO
(the git pull must be done inside the iso dir, btw)

but I could use more up to date instructions.

Anyone have an "official" list of commands that will cause the git
sources to build?

I've had success with some that I could figure out:

make kernel (custom for my hardware)
make core
make opt (pruned to match the crux iso)
make xorg (pruned to match my video hardware)

but not with

make bootstrap
make iso
etc.

Thanks,

Chris

Any, yes, I realize that my "tuning" probably did little or nothing;
in fact I've probably just wasted many hours on a worthless endeavor.
But, sometimes you've just got to prove things to yourself the hard
way. The joke is REALLY on me if -march-prescott is indeed identical
to -march=i686
_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
http://lists.crux.nu/mailman/listinfo/crux

On Feb 17, 2008 5:40 PM, Chris Pemberton <cjpembo@gmail.com> wrote:
> I built an "optimized" Crux 2.4 using the following parameters:
>.....

Ok, I managed to git the most up to date sources, including the
new_iso-buildref.txt file, which is very detailed.
You don't get this file if you follow the directions verbatim on the
crux website...

I have a (possibly simple) question regarding that file:

What does "WC" stand for in the following lines:

# checkout your new_iso, core, opt, and xorg git WCs
# (I just copy them from my user's local WC)

Thanks,

Chris
_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
http://lists.crux.nu/mailman/listinfo/crux

Hello, Chris.

On Mon, 18 Feb 2008 01:04:08 -0600
"Chris Pemberton" <cjpembo@gmail.com> wrote:

> [...]
> What does "WC" stand for in the following lines:
>
> # checkout your new_iso, core, opt, and xorg git WCs
> # (I just copy them from my user's local WC)
It stands for so-called git 'working copy' which is a synonym of
'copy of the project tree'. Some explanation is at [1].

[1] http://git.or.cz/course/svn.html#know

--
Mikhail Kolesnik
ICQ: 260259143
IRC: mike_k at freenode/#crux, rusnet/#yalta
_______________________________________________
CRUX mailing list
CRUX@lists.crux.nu
http://lists.crux.nu/mailman/listinfo/crux