RE: [Ltib] Alsa troubles

[Stuart Hughes]

Hi Markus,

This is a new problem, not the alsa issue?

Looks to me like you're trying to install on an ubuntu (or similar)
system that is using dash instead of bash as it's default shell.  This
causes clauses like: cp a/b/{c,d,e} f/g/ to fail.  Later versions of
ltib (which I've not yet merged out) fix this, but in this case you'll
need to:

1/ Remove completely the failed LTIB install (rm -rf /opt/ltib
or /opt/freescale depending on where you got it)

2/ Change your default shell to bash.  I'd actually advise changing
the /bin/sh symlink to point to bash. It's not just LTIB that barfs on
dash.

3/ Re-run the ltib installer.

Regards, Stuart

On Tue, 2007-09-18 at 17:07 +0200, Markus Bollinger wrote:
> Hello Stuart,
> 
> my colleague has successfully built the same alsa-driver on another
> system,
> so I think my problem is simply a configuration error.
> 
> I reinstalled everything from scratch (with the CD "mITX-GP-20061024")
> on another computer and I ran into following problem:
> 
> After installation from the CD the first call to ./ltib I get an error
> for creation of /tmp/rpm-mbr/BUILD, /tmp/rpm-mbr/SOURCE, ..
> directories
> On the second call (after manually creating the directories) I get an
> error for "texinfo" generation. see file attached.
> 
> Could the problem be the SHELL (/bin/bash version 3.2.13), what do you
> think ? What shell should be used ?
> 
> Markus.
> 
> 
> 
> -----Original Message-----
> From:   Stuart Hughes [mailto:address@hidden
> Sent:   Mon 9/17/2007 5:34 PM
> To:     Markus Bollinger
> Cc:     address@hidden
> Subject:        RE: [Ltib] Alsa troubles
> 
> Hi Markus,
> 
> I just had a look at the log and noticed:
> 
>                  from memory_wrapper.c:21:
> /home/exaudi/ltib-mpc8349itx-gp-20061024/rootfs/usr/src/linux/include/asm/setup.h:8:28:
>  asm-m68k/setup.h: No such file or directory
> 
> I've seen this before in a difference context, from what I recall the
> include/asm-ppc/setup.h file should not need to include
> asm-m68k/setup.h, I think you can simply comment out this include
> line.
> 
> Regards, Stuart
> 
> 
> On Mon, 2007-09-17 at 16:33 +0200, Markus Bollinger wrote:
> > Hello Stuart,
> > thank you for your quick response!
> >
> > Platform is : Freescale MPC8348E-mITX-GP board
> > The package is : alsa-driver (version 1.0.15rc1)
> >
> > I tried to use $DEV_IMAGE/usr/src/linux as you suggested and I
> attached the results :
> > output from ltib and the alsa-driver.spec file
> >
> > Now the headers can be found, but not all of them.
> >
> > I had a look in ltib -m config, but the kernel headers are already
> included.
> >
> > Regards,
> > Markus.
> >
> >
> >
> > > -----Message d'origine-----
> > > De : Stuart Hughes [mailto:address@hidden
> > > Envoyé : Friday, September 14, 2007 7:04 PM
> > > À : Markus Bollinger
> > > Cc : address@hidden
> > > Objet : Re: [Ltib] Alsa troubles
> > >
> > > Hi Markus,
> > >
> > > Can you tell me:
> > >
> > > * Which platform you are building for
> > > * Which package this is (I mean the output from running ltib
> > > with this selected).  I'd need to know the exact spec file as
> > > there are a few in dist/lfs-5.1/alsa-lib
> > >
> > > For userspace packages, the header files come from the
> > > toolchain, kernel header file should not be directly included.
> > >
> > > For some packages that need kernel headers, you need to use
> > > the ones belonging to the kernel used for the target
> > > (/usr/src/linux won't work).
> > > For some examples see: blob-imx21ads.spec for an example. 
> > > Basically you need to do 2 things:
> > >
> > > 1/ add something to the spec file that says the kernel is in
> > > $DEV_IMAGE/usr/src/linux
> > >
> > > 2/ in ltib -m config, turn on:
> > > [*] Include kernel headers
> > >
> > > Regards, Stuart
> > >
> > > On Fri, 2007-09-14 at 16:48 +0200, Markus Bollinger wrote:
> > > > Hello!
> > > >
> > > > I have some troubles to generate the alsa-driver
> > > > (alsa-driver-1.0.15rc1) for a PowerPC target.
> > > > (alsa-driver outside of the kernel source tree).
> > > >
> > > > If I call ltib with a standard alsa-driver.spec file that calls
> > > > ./configure --prefix=%{_prefix} --host=$CFGHOST --build=
> %{_build}
> > > >
> > > > this leads to a wrong path to kernel headers during make (path
> to
> > > > linux headers of the system where I compile on).
> > > >
> > > > If I specify
> > > > ./configure --prefix=%{_prefix} --host=$CFGHOST --build=
> %{_build}
> > > > --with-kernel=/usr/src/linux the headers cannot be found at
> > > all (e.g.
> > > > /usr/src/linux/headers/linux/version.h)
> > > > but the file rootfs/usr/src/linux/headers/linux/version.h
> exists ??
> > > >
> > > > Is there something I misunderstood ? Or a configuration
> > > problem ? Or a
> > > > bug ? Who has compiled a recent alsa-driver ?
> > > >
> > > > Markus.
> > > >
> > > > P.S. sorry if this a silly newbie question....
> > > >
> > > >
> > > > _______________________________________________
> > > > LTIB home page: http://bitshrine.org
> > > >
> > > > Ltib mailing list
> > > > address@hidden
> > > > http://lists.nongnu.org/mailman/listinfo/ltib
> > >
> > >
> 
> 
> 
> 
> 
>