> I don't know what "info make" "Syntax of Static Pattern Rules" is (since I
> don't have info installed on my Solaris system) but I'm guessing that
> whatever it is, it's the underlying cause for Solaris make to complain:
info is the texinfo doc reader, generally used for GNU
documentation.. thu
# New Ticket Created by Jeff Clites
# Please include the string: [perl #24087]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=24087 >
I'm getting a crash on Mac OS X on test 17 of
languages/imcc/t/syn/macro.t, which is try
Andy Dougherty writes:
> On Wed, 1 Oct 2003, Leopold Toetsch wrote:
>
> > Andy Dougherty wrote:
> >
> > > Building with Sun's Workshop compiler, I'm currently getting stuck when
> > > comiling core_ops.c with the message:
> > >
> > > "bit.ops", line 349: a cast does not yield an lvalue
>
> >
On Wed, 1 Oct 2003, Leopold Toetsch wrote:
> Andy Dougherty wrote:
>
> > Building with Sun's Workshop compiler, I'm currently getting stuck when
> > comiling core_ops.c with the message:
> >
> > "bit.ops", line 349: a cast does not yield an lvalue
> > ((UINTVAL) $1 >>= $2;
> *(
Sun's Workshop compiler complains about the use of a non-constant
initializer in the giant vtable initialization in the class_init()
functions generated by classes/pmc2c.pl. Here's a sample error message:
"array.c", line 649: non-constant initializer: op "NAME"
Here's a suggested fix:
--- p
Andy Dougherty wrote:
Building with Sun's Workshop compiler, I'm currently getting stuck when
comiling core_ops.c with the message:
"bit.ops", line 349: a cast does not yield an lvalue
"bit.ops", line 349: a cast does not yield an lvalue
Sure enough, line 349 in bit.ops is
((UINTVAL
Joseph Ryan wrote:
According to the CVS log for /languages/imcc/imcc.l, "::" is now
allowed inside an identifier name. However, when I try to create
an example like:
.sub foo::bar
end
.end
It gives the error:
error:imcc:parse error, unexpected LABEL, expecting IDENTIFIER
Is this
Michael Scott (via RT) <[EMAIL PROTECTED]> writes:
> PIO_parse_open_flags thinks that "<" is the same as "<". This
> could lead to errors such as using "<<" instead of ">>".
I solved the problem with a different patch. Your solution was not
easily extendeble with the planned but not impl
Building with Sun's Workshop compiler, I'm currently getting stuck when
comiling core_ops.c with the message:
"bit.ops", line 349: a cast does not yield an lvalue
"bit.ops", line 349: a cast does not yield an lvalue
Sure enough, line 349 in bit.ops is
((UINTVAL) $1 >>= $2;
I don't
On Wed, 1 Oct 2003, Leopold Toetsch wrote:
> Thanks to Andy for the feedback - I have replaced that part with a
> simpler and probably less gnuish make rule.
Thanks. That works better. (I'm now stuck elsewhere, but that's a
separate issue.)
--
Andy Dougherty [EMAIL PROTECTED]
We now have 5 distributions currently being worked on in the Phalanx
project. See http://qa.perl.org/phalanx/status.html for details.
Come join the fun! Pick a module and let me know about it!
xoa
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
According to the CVS log for /languages/imcc/imcc.l, "::" is now
allowed inside an identifier name. However, when I try to create
an example like:
.sub foo::bar
end
.end
It gives the error:
error:imcc:parse error, unexpected LABEL, expecting IDENTIFIER
Is this a bug, or am I misu
In my last commit I forgot to remove makefiles/root.in from the check in
list - and worse, I've checked it out immediately - so that my original
is gone.
If it doesn't work please undo the changes to makefiles/root.in or leave
it - lets just see, how its goes.
leo
I've committed that part directly as it should be totally independent of
the immanent changes to the build system.
It cleans up some remaining cruft from the old days when assemble.pl
happened to be used.
More importantly there are now two different ways to run tests through
the PIR assembler:
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #24082]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=24082 >
Thanks to Andy for the feedback - I have replaced that part with a
simpler and proba
Andy Dougherty <[EMAIL PROTECTED]> wrote:
> I don't know what "info make" "Syntax of Static Pattern Rules" is
It was a rule like:
$(dir/o_files) : %.o : %.c dependencies
Its now separated into two.
Thanks for the feedback, I've sent an updated version to bugs-parrot.
leo
Juergen Boemmels <[EMAIL PROTECTED]> wrote:
> If nobody objects I will commit this change tomorrow.
I really thought that stuff is already committed - but obiously isn't -
my bad. A minute ago I had checked in build system changes WRT languages
to use parrot instead of imcc.
This will for sure co
On Wed, 1 Oct 2003, Leopold Toetsch wrote:
> The only problematic thing AFAIK might be the automatic rule in
> root.in:594 that includes the private imcc headers for building
> IMCC_O_FILES. I don't know if other makes are capable of "info make"
> "Syntax of Static Pattern Rules". If not, we proba
"Jonathan Worthington" <[EMAIL PROTECTED]> writes:
> - Original Message -
> From: "Juergen Boemmels" <[EMAIL PROTECTED]>
> To: "Brent Dax" <[EMAIL PROTECTED]>
> Cc: "'Steve Fink'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Tuesday, September 23, 2003 6:38 PM
> Subject: Re: [RfT] Conf
# New Ticket Created by Leopold Toetsch
# Please include the string: [perl #24080]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt2/Ticket/Display.html?id=24080 >
Attached is a first attempt to prepare for the move of languages/imcc to
imcc and to
20 matches
Mail list logo
