I need yacc

[Almost-retired]

What repo do I need to enable to be able to get yacc?

Thanks, Gene

[AS]

I have successfully used bison where yacc was required, available in standard repos.

$ yacc --help
Usage: /usr/bin/bison [OPTION]... FILE
Generate a deterministic LR or generalized LR (GLR) parser employing
LALR(1), IELR(1), or canonical LR(1) parser tables.  IELR(1) and
canonical LR(1) support is experimental.

...

AS

[Almost-retired]

I did find byacc which made it one or two steps past the missing yacc.  I will also get bison.

However bison did not help, from that terminal:
make[2]: Entering directory `/home/gene/src/mailfilter-0.8.2/src'
: -+ -i -Prc -orcfile.cc rcfile.ll
g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/local/include -I. -I../include -I.. -DLOCALEDIR=\"/usr/local/share/locale\" -I../intl -I.. -I../include -I.   -Wall -g -O2 -MT rcfile.o -MD -MP -MF .deps/rcfile.Tpo -c -o rcfile.o rcfile.cc
g++: rcfile.cc: No such file or directory
g++: no input files
make[2]: *** [rcfile.o] Error 1

And indeed, the first step, making rcfile.cc from rcfile.ll, does not result in an rcfile.cc being built.  Not sure if I understand that syntax ": -+ -i -Prc -orcfile.cc rcfile.ll" shown above, its almost like the Makefile itself is defective.

I am trying to remake mailfilter from the src tarball as its sensitivity to 8 bit chars makes it a bit less than 100% useful in today's age of everything speaking 16 bit chars.
That sensitivity is causing what look like legal headers to be barfed over, and if mailfilter upchucks, then fetchmail skips the pull from that mailserver.

Then I have to log into that servers webmail access and delete the offending message IF I can find it, or even remove mailfilter from that ISP stanza in fetchmailrc for one pull cycle.

That is turning into a PIMA.

Is there another filter utility that works like mailfilter, but which might accept the full 8 and 16 bit characters?

I also am not sure which is correct, maybe the headers are supposed to be 7 bit ascii only, and its the message that is defective.

Wading through the swahili in rfc822 is not my strong suite.

Thanks as, Gene

[AS]

And indeed, the first step, making rcfile.cc from rcfile.ll, does not result in an rcfile.cc being built.  Not sure if I understand that syntax ": -+ -i -Prc -orcfile.cc rcfile.ll" shown above, its almost like the Makefile itself is defective.

the "-+" look like a lex option ... (generate C++ scanner class)

However, because mailfilter-0.8.2 actually is in repo ... it's should have been compiled with the current/available tools ...i.e flex

[Almost-retired]

Installing that doidn't effect the error msg, sorry.
Now I will be 'out of pocket' for about 5 days.  I may pursue this further when I get back.

Thanks as, Gene

[kjpetrie]

Since this is the same version that is in the repo, you will have to patch it to implement the change, in which case, why don't you save yourself the trouble and set up a packaging environment, download the pclos SRPM, learn to build packages, and produce a new package. The .spec file in the SRPM will tell you what packages are needed to build it and do most of the work for you.

All you will then need to do is produce the patch to change the program's behaviour.

[Almost-retired]

I just might do that, kjpetrie, when I am once again back in Dodge.  Thanks & Cheers, Gene

[T6]

you don't have to enable more than one repo, all the pclinux repos are identical, mirrors of a main server

what you find in one is the same as the other, sometimes one is a little outdated so be patient

if the app you mention is outdated, a package request could be useful here

[Almost-retired]

'if the app you mention is outdated, a package request could be useful here"

That would be nice.  If it worked.  So far, every package update or inclusion request because its just not there, has been ignored, and in one case the requesting post was deleted and I was chastised by PM for making the request.  So it is in fact a bit of a sore topic to me.  The net result is that this machine is the only one with a remaining pclos install out of 3 originally.  I don't like the *buntu framework, particularly trying to do networking in hosts file style.

But, everything I can't do on this box, Just Works(TM) on the *buntu's once I figure out how *buntu does it.

List of can't do's:

1. ssh -Y fails, any moving image fails to open its display window.  Stills are fine.

2. can't install 11quartus software for fpga work, libxml2.so is broken, no gzdirect call.

3. Ditto for the Spartus fpga stuff but do not now recall the errant package that breaks that install, before it has done more than unpack the selk-unpacking archive.

4. Heekscad/heekscnc will not build. Windows version runs ok under wine.

5. Mailfilter won't build, see this thread.

The list might be even longer, but this would appear to be beating a dead horse.

Yes, its stable, I have a 28 day uptime right now, in spite of the kde install being as bleeding edge as can be, but that stability appears to be obtained by restrictions on what is allowed to be done.

Thanks T6, & Cheers, Gene

[T6]

about package requests, it is the only place where everyone is strict here, you have to be precise and you must ask a viable app to be added

beta, alpha or unmaintained/unstable apps are out of the question

no idea what was the particular situation on your posts so can't say more

about stability and restrictions, yes, one makes possible the other

everyone loves a stable system, nobody wants unstable and wonderful apps making your wonderful os crash like a test plane

exchange one thing for another