[Crash-utility] current crash spec file

[Dave Anderson]

----- Original Message -----
>
>
> ----- Original Message -----
> >
> >
> > Hi Dave,
> >
> > crash/extensions/sial.so is missing in my mock build, after using your
> > crash-6.0.7-0.src.rpm from http://people.redhat.com/anderson. To correct
> > this problem flex and bison is required within the BuildRequires: step.
> >
> > current step:
> > BuildRequires: ncurses-devel zlib-devel
> >
> > my step:
> > BuildRequires: ncurses-devel zlib-devel flex bison
> >
> > Is it possible to fix it in the future ?
> >
> > Mit freundlichen Grüßen / Kind regards
> >
> > Axel Wirbser
> >
> > Build & Packaging Spezialist
> > IBM Systems & Technology Group, Systems Software Development
> > Technical Operations & Linux Technologies, Systems Software
> > Management
>
> Right, I understand the situation, but it's done that way on purpose.
> That's the reason that the extensions/sial.mk file has this:
>
> all:
>         @if [ -f /usr/bin/flex ] && [ -f /usr/bin/bison ]; then \
>           if [ -f ../$(GDB)/crash.target ]; then \
>             make -f sial.mk sial.so; else \
>           echo "sial.so: build failed: requires the crash $(GDB)
>           module"; fi \
>         else \
>           echo "sial.so: build failed: requires /usr/bin/flex and
>           /usr/bin/bison"; fi
>
> i.e., precisely for situations like yours, but where a user does not have flex
> and bison installed, and has no interest in SIAL.  The idea is to keep the upstream
> spec file as unrestrictive as possible.
>
> Is it possible to restrict the BuildRequires to only the extensions
> subpackage?
>
> Dave

I should also mention that in crash-6.0.8 (most likely) the SIAL sources
will no longer be part of the crash source code package.  Luc Chouinard
has created an upstream "eppic" git project (Embeddable Pre-Processor and
Interpreter for C) to host his formerly-named SIAL sources:

  http://code.google.com/p/eppic/source/checkout

The idea will be to git clone/pull the eppic sources into the crash source
tree with each new release (and whenever the user desires to do so after that).
Luc's original idea was to have the user do the git operation manually, but I'm 
trying to convince him to put the git pull/clone operation in the sial.mk
file so that it's seamless.

Dave