On Thursday 12 March 2009, Andi Kleen wrote: > to be honest the estimate of adding btree directories in 3kLOC > of code seems very optimistic.
Is that a bet? > >> This symbol is only supposed to be shared between separate compilation > >> units within fs/tux3, not be visible outside our module. How do we do > >> that? > > > > You can't. Bear in mind that we want the allyesconfig kernel to link > > and run, and that includes tux3. So do it manually by prefixing > > everything with tux3_ or whatever. (does it need the "3"?) > > AFAIK it could be done by using special linker scripts for the sublinks. > But I'm not sure it's worth it because that would require listing of the > symbols > in some file. Would need some Makefile magic. > > For modules I also had the "namespace" patches some time ago which implemented > simple namespace support. Should probably resurrect that. Per-module name scope would be a nice creature comfort. Well, for now the offending names will just get tux_ed. Regards, Daniel _______________________________________________ Tux3 mailing list [email protected] http://mailman.tux3.org/cgi-bin/mailman/listinfo/tux3
