According to Leo Toetsch:
> Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> > + $(RM_F) $(IMCC_DIR)/imcparser.c
> > + $(RM_F) $(IMCC_DIR)/imclexer.c
>
> This isn't quite right, it works only if you have bison/flex and you
> did Configure.pl --maintainer
>
> If you don't change the files and just
Chip Salzenberg <[EMAIL PROTECTED]> wrote:
> cvsuser 05/04/04 13:03:46
> Modified:config/gen/makefiles root.in
> Log:
> When generating parser or lexer, remove target .c file first.
[ ... ]
> + $(RM_F) $(IMCC_DIR)/imcparser.c
> + $(RM_F) $(IMCC_DIR)/imclexer.c
This isn't qu
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> Andy Dougherty <[EMAIL PROTECTED]> wrote:
>
> > Sorry, I guess I should have been more explicit. What folks apparently do
> > is have the sources on an NFS server mounted read-only. They then build a
> > symlink tree onto a local read-write filesyst
At 10:32 AM +0100 12/2/03, Leopold Toetsch wrote:
Andy Dougherty <[EMAIL PROTECTED]> wrote:
Sorry, I guess I should have been more explicit. What folks apparently do
is have the sources on an NFS server mounted read-only. They then build a
symlink tree onto a local read-write filesystem and r
Andy Dougherty <[EMAIL PROTECTED]> wrote:
> Sorry, I guess I should have been more explicit. What folks apparently do
> is have the sources on an NFS server mounted read-only. They then build a
> symlink tree onto a local read-write filesystem and run the build there.
> Thus they can create all
On Dec 1, 2003, at 8:11 AM, Andy Dougherty wrote:
On Mon, 1 Dec 2003, Leopold Toetsch wrote:
Andy Dougherty <[EMAIL PROTECTED]> wrote:
I can think of one other potential problem: What if the user wants
to
mount the source read-only? Last I checked, except for this issue,
it was
possible to d
On Mon, 1 Dec 2003, Leopold Toetsch wrote:
> Andy Dougherty <[EMAIL PROTECTED]> wrote:
>
> > I can think of one other potential problem: What if the user wants to
> > mount the source read-only? Last I checked, except for this issue, it was
> > possible to do so. For perl5, this ability was oft
Andy Dougherty <[EMAIL PROTECTED]> wrote:
> I can think of one other potential problem: What if the user wants to
> mount the source read-only? Last I checked, except for this issue, it was
> possible to do so. For perl5, this ability was often requested.
We are generating all kinds of files i
On Thu, 27 Nov 2003, Leopold Toetsch wrote:
> JüRgen" "BöMmels <[EMAIL PROTECTED]> wrote:
> > +TOUCH = $(PERL) -e ${PQ}open(A,qq{>>$$_}) or die foreach @ARGV${PQ}
>
> Well done. *But* this f*cking command does still not update time stamps.
>
> Is this a Perl5 failure? Anyway, we need a (golfy)
Juergen Boemmels <[EMAIL PROTECTED]> wrote:
> How about this? Its from perldoc -f utime:
Ah thanks. I should have read that first :)
> TOUCH = $(PERL) -e ${PQ}$now = time; utime $now, $now, @ARGV;${PQ}
s/\$now/\$\$now/g for Makefile's sake.
Touches existing files fine. For imcc.y.flag we could
Leopold Toetsch <[EMAIL PROTECTED]> writes:
> JüRgen" "BöMmels <[EMAIL PROTECTED]> wrote:
> > +TOUCH = $(PERL) -e ${PQ}open(A,qq{>>$$_}) or die foreach @ARGV${PQ}
>
> Well done. *But* this f*cking command does still not update time stamps.
>
> Is this a Perl5 failure? Anyway, we need a (golfy
JüRgen" "BöMmels <[EMAIL PROTECTED]> wrote:
> +TOUCH = $(PERL) -e ${PQ}open(A,qq{>>$$_}) or die foreach @ARGV${PQ}
Well done. *But* this f*cking command does still not update time stamps.
Is this a Perl5 failure? Anyway, we need a (golfy) touch equivalent for
these poor systems not providing o
12 matches
Mail list logo
