2006/12/23, Hisham Muhammad <[EMAIL PROTECTED]>: > On 12/22/06, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > > On 12/22/06, Rafael Jeffman <[EMAIL PROTECTED]> wrote: > > > On 12/20/06, Lucas C. Villa Real <[EMAIL PROTECTED]> wrote: > > > > > > > > GLib looks for 'glib-genmarshall' if cross-compiling. > > > > > > I'm not sure, but it seems to me that 'glib-genmarshal' does not > > > depend on GLib and could have it's own package. Debian often has many > > > packages creatend from a single source. I'm not a fan of this > > > approach, but it seems feasible *for this specific case*, which > > > doesn't seem to happen unless very occasionally. > > > > Yes, it could.. but since this is a problem tied only to cross > > compilation, maybe we can just enhance our CheckDependencies parser so > > that it can recognize things like this in BuildDependencies: > > > > GCC 4.1.1 [!cross] > > GLib [cross,!ppc] > > > > This would indicate that one need to have GLib on the host if cross > > compiling (except if compiling for ppc), and that GCC should be > > ignored if doing a cross compilation. > > Oops, turns out that the syntax is not clear enough. I would have > interpreted the "," as an "or", not and "and". I think "or" is more > useful, or else [arm,ppc] does not make sense. > Yes, or is more useful, if we only are to use one operator. Perhaps introducing another operator for and, if we come to the conclussion that we need one.
-- /Jonas _______________________________________________ gobolinux-devel mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
