[alsa-devel] [PATCH] alsa-driver git repo: Build problems when copying symlink to itself

[Colin Guthrie]

'Twas brillig, and Takashi Iwai at 14/03/11 09:43 did gyre and gimble:
> At Sat, 12 Mar 2011 10:30:48 +0000,
> Colin Guthrie wrote:
>>
>> Hi,
>>
>> After doing a "simple":
>> git clone alsa-driver
>> git clone alsa-kernel
>> cd alsa-driver
>> ./gitcompile --with-debug=full --with-isapnp=yes --with-sequencer=yes
>> --with-moddir=updates/alsa:
>>
>> The build bombed out pretty quickly with the following error.
> 
> Can't reproduced with my trees.  Could you try the GIT trees below
> instead?
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/alsa-driver-build.git
> git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git

OK, so I should have explained it a bit better - tho' in actual fact my
fixes wont really help much....


I was using the trees @

git://git.alsa-project.org/alsa-driver.git
 and
git://git.alsa-project.org/alsa-kernel.git


I tried cloning the repos you suggested and ran the script and all was well.

The problem I generally encountered was that as time passes (as it has
since the last time I used my clones) and you do a git pull, the patches
that are needed change.

When these change, the file alsa-driver/includes/sound/.includes (which
is generated by alsa-driver/includes/sound/Makefile) is *not* updated.
Therefore, the patch information is bogus and incorrect.

Really the build script needs to rm that file or the Makefile has to be
able to update it accordingly.

I also run into the same problem when trying to chase down a regression
(a pre-bisect checks). I was not able to rebuild the older drivers
easily without rm'ing the above .includes file. Obviously even with the
two patches I attached previously, it only papers over the problem as
the .include file is simply out of date. Correcting the .include file
should avoid the need for my changes.

Am I missing a trick here or is it part of the bi-secting process?

Also please see my other mail about *how* to do a bisect here - while
keeping alsa-driver and alsa-kernel in sync....

In an ideal world I need to downgrade to 1.0.23 or 1.0.22 of ALSA to
check to see if the problem still existed, but can't find a super easy
way to do that (other than perhaps just building myself a really old
kernel from my distro's VCS).

Col

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
  Mageia Contributor [http://www.mageia.org/]
  PulseAudio Hacker [http://www.pulseaudio.org/]
  Trac Hacker [http://trac.edgewall.org/]