In article <200103071406.f27E6pO25638@aslan.scsiguy.com> you wrote:
> The assembler makefile doesn't reference yacc, but instead relies
> on gmake's built in rules to figure out how to generate a .c from
> a .y. I'm somewhat surprised that bison doesn't create a link to
> yacc or that gmake doesn't try to look for bison.
Yepp, gmake is kindof stupid in that respect - it does also not try
to use flex if there is no lex, etc... I'd really vote for a BSDish
sys.mk.
> Oh well. We'll just have to be more careful in how future patches
> are generated so that the dependency between the generated firmware
> files and the firmware source only triggers if you are actually
> performing firmware development. Trying to build this simple
> assmebler on everyone's systems is turning out to be just too
> hard.
What about simply removing the firmware source and assembler from the
kernel tree? We have lots of firmware in the kernel tree for which
there isn't even firmware avaible...
The few people that want to do firware development could download it
from your ftp site.
Christoph
-- Of course it doesn't work. We've performed a software upgrade. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Mar 07 2001 - 21:00:23 EST