> On Thu, Oct 16, 2008 at 09:27:29AM +0200, Duft Markus wrote:
> > Now some package of mine in a local overlay requires bison and flex.
> > It's quite hard to get those to build _and_ work on winnt, so I
> though
> > about splitting the bison ebuilds in dev-util/bison and
> > dev-libs/bison-runtime (and the same for flex). What do you think
> about
> > this? Before we started using portage at our company I built the
> > runtimes only for winnt, so I know this works (for me)...
> Does yacc build+work maybe?

Hmm, haven't tried, I must admit, since our software has an explicit
depend on binson, since it uses it's runtime library. That's why I would
require distinct packages for bin and runtime. Bin should be built as
interix executable, which dependes on m4, which I just can't get to work
on winnt, and runtime should be built as winnt, since I need to link
against it.

After playing _many_ hours, this seems to be the only solution. If there
are objections against this, I can do it in a local overlay. I just
wanted to discuss it, to not do it in the overlay when others might want
this too, and just don't have time to do it :)

Cheers, Markus

> --
> Robin Hugh Johnson
> Gentoo Linux Developer & Infra Guy
> E-Mail     : [EMAIL PROTECTED]
> GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

Reply via email to