Thanks for the kind responses.
I used the yacc and lex that came with my SunOS 5.8, then
tried bison 1.28 and flex 2.5.4, and none worked well.
I think the exact problems were both in compilation and
linking, but I only vaguely remember.
I will post the exact symptom(s) as soon as I have time to
reproduce the trouble (and I will have to do it anyway).
Regards,
hiro
> -----Original Message-----
> From: Matt D. Robinson [mailto:yakker@xxxxxxxxxxxxxx]
> Sent: Monday, July 16, 2001 16:46
> To: Luc Chouinard
> Cc: Hiro Sugawara; lkcd@xxxxxxxxxxx
> Subject: Re: Compiling on SunOS
>
>
> To take this a step further, what lex/yacc revision are you using?
> And is this an RPM-based user-land, and if so, which RPMs?
>
> If this is as simple as changing 'yacc' to 'bison', that's easy,
> but if you're using the same lex/yacc revision that is commonly
> used on x86 RH systems, then we've got a whole other problem to
> solve.
>
> --Matt
>
> Luc Chouinard wrote:
> >
> > Hiro, I did a checkin last week on sourceforge to fix a problem with
> > using the bison parser instead of yacc. Make sure you
> cvs/update with
> > the latest. If you are running with the latest, then send
> me the error
> > messages that you get I'll check it out.
> >
> > Let me know,
> >
> > Hiro Sugawara wrote:
> > >
> > > Hi!
> > >
> > > I am porting LKCD to our embedded PPC Linux with SunOS 5 as the
> > > host. With modified gdbserver as an agent, lcrash can now show
> > > ps, backtrace process stack, disassemble the code, and do other
> > > things on a live kernel.
> > >
> > > One big problem is that the lex and yacc files do not compile
> > > well on SunOS. I work around this problem by using Linux to
> > > produce *.c files from the source and then copying those files
> > > by hand.
> > >
> > > Does anybody have encountered (and hopefully solved) this
> > > problem?
> > >
> > > hiro
> >
> > --
> > Luc
>
|