[gentoo-dev] bison/flex extra runtime packages

[gentoo-dev] bison/flex extra runtime packages

[Duft Markus]

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 all others
(RDEPEND, PDEPEND) from winnt.

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)... 

Is there any better Idea around?

Cheers, Markus

Re: [gentoo-dev] bison/flex extra runtime packages

[Fabian Groffen]

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). 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)... 

Not sure if I understand correctly, but if you're aiming for
dev-libs/bison-bin, then I prefer to keep on using an overlay for winnt.
It's too evasive, IMO.  We can just create a new overlay either in
gentoo-alt or a new top-level one on overlays.g.o.


-- 
Fabian Groffen
Gentoo on a different level

Re: [gentoo-dev] bison/flex extra runtime packages

[Robin H. Johnson]

[-- Attachment #1: Type: text/plain, Size: 662 bytes --]

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?

-- 
Robin Hugh Johnson
Gentoo Linux Developer & Infra Guy
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 329 bytes --]

RE: [gentoo-dev] bison/flex extra runtime packages

[Duft Markus]

> 
> 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     : robbat2@gentoo.org
> GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

Re: [gentoo-dev] bison/flex extra runtime packages

[Mike Frysinger]

[-- Attachment #1: Type: text/plain, Size: 652 bytes --]

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 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)...

that doesnt make sense.  there is no separate "bison-runtime" nor "flex-
runtime".  either a package uses bison or it does not, there is no in between.  
same goes for flex.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]