On Thursday 16 October 2008 03:27:29 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
Hi there!
I'm working on a cross compilation to native windows from an Interix
Gentoo Prefix, using the normal Prefix portage tree. My setup is nearly
the same as when really cross compiling, except that I can execute what
I compile.
I use command line utilities (DEPEND atoms) from Interix, and
On 16-10-2008 09:27:29 +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).
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
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
