Re: yesss, sound in 2.0.36

Peter T. Breuer (
Sat, 5 Dec 1998 12:32:15 +0100 (MET)

"A week, arrgh, a month of mondays ago Michael Elizabeth Chastain wrote:"
> Last month you wrote:
> > .. I gotta say that Michael Chastain has changed the sound
> > Makefiles to a format that is slightly utterly incomprehensible.
> :-/
> Which part, the first part with all the lists, or the second part
> where it preprocesses firmware files for PSS and Turtle Beatch?

First part. I doubt that my sanity survived until the second part.
In any case, I had neutered the firmware.c code by then, after
fruitlessly searching for where it hoped to get sys_open and friends
from. I haven't gone back and unneutered it yet.

> The first part is about 1/3 the size of the previous Makefile
> and a lot easier to write correctly. But you are right, it is
> based on some novel idioms, and I did not document these idioms.
> I will make a note to document this better in the future.

Please do. A "how to modify" for power users. A normal mind would
wrench itself hopelessy into oblivion at this part:

# Each configuration option enables a list of files.

ifeq ($(ARCH),m68k)
obj-$(CONFIG_DMASOUND) += dmasound.o

Note that the name of the variable denoting the list you act on is
calculated. Self modifying code, in fact. I can cope with that. I
think life started hurting at "# Declare multi-part drivers. ".
Sentient death ocurred near "# The 'int-*' lists are the intermediate
files used to build the multi's." After that, the comments indicate that
the author was having trouble too.

> files. 'Make' does not have native support for this so I have to
> keep track of dependency information by hand and use a dummy
> dependency.

Moral: depend on dummies.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at