On Tue, Sep 1, 2009 at 12:17 PM, Simon 'corecode' Schubert
corec...@fs.ei.tum.de wrote:
Michel Alexandre Salim wrote:
I plan to do that (looking at the other Linux port right now too). I
already have a custom Makefile for cpdup anyway, and before I tried
using bmake I already tried using gcc
On Tue, Sep 1, 2009 at 11:42 PM, Matthew
Dillondil...@apollo.backplane.com wrote:
I like the concept of throwing together an export hierarchy,
but it might be too much maintainance to physically separate
the git components out within the primary repo.
Using git submodules, the
Oh, a tarball iso good enough, thanks.
--
Michel
On Sep 3, 2009 3:34 PM, Simon apos;corecodeapos; Schubert
corec...@fs.ei.tum.de wrote:
Michel Alexandre Salim wrote: On Tue, Sep 1, 2009 at 11:42 PM, Matthew
Dillondil...@apollo.ba...
I don't want to use submodules, because they change
tried
using bmake I already tried using gcc by hand. I must say the bundled
rules in Dragonfly's make are quite impressive.
--
Michel Alexandre Salim
On Tue, Sep 1, 2009 at 3:03 AM, Sascha Wildners...@online.de wrote:
Michel Alexandre Salim schrieb:
Where is aliases_parse.h supposed to be generated?
We do basically:
yacc -d -o aliases_parse.c aliases_parse.y
Aha, thanks! This is where our bmake went wrong -- rather than
specifying
: error: ‘T_EOF’ undeclared (first use in this function)
*** Error code 1
Where is aliases_parse.h supposed to be generated?
Thanks,
--
Michel Alexandre Salim