Page 1 of 1

Devxx_precise_5.7.1 installed, make doesn't work

Posted: Wed 25 Sep 2013, 06:41
by cy3a
i tried to install foo2zjs:a linux printer driver for ZjStream protocol. I followed steps from page: http://foo2zjs.rkkda.com/
I installed devxx_precise_5.7.1, but when i try to do "make" it said:
Error: must install GNU dc with -e option!
What shall i do?
Thanx.

Posted: Wed 25 Sep 2013, 08:00
by Karl Godt
What it said : Get a regular dc binary , since it appears that your Puppy uses the busybox dc applet
Type

Code: Select all

type -a dc
readlink -f `which dc`
dc --help
to check for your dc version .

http://packages.ubuntu.com/precise/dc
dl it and open it with xarchive somewhere and fetch the dc binary and put it into /bin directory .

Posted: Wed 25 Sep 2013, 10:43
by rcrsn51
Why are you compiling this driver from source? A year ago, you used a driver PET here.

Posted: Mon 30 Sep 2013, 14:45
by cy3a
rcrsn51 wrote:Why are you compiling this driver from source? A year ago, you used a driver PET here.
that was with puppy 4.3.1. Now i have 5.7.1, but pet driver doesn't work.

Posted: Mon 30 Sep 2013, 15:14
by rcrsn51
If you are using a Puppy with a newer kernel, like Precise 571, the foo2xxx driver requires a patch. It is posted here as foo2xxx_udev_patch_upup387-1.0.pet .

The installation procedure is:

1. Install the foo2xxx PET (if not done already)
2. Install the patch PET
3. Reboot the printer
4. Install the printer in CUPS (if not done already)
5. Print something

Please report back with your success or failure. This is important testing on your part.

Posted: Mon 30 Sep 2013, 15:40
by cy3a
rcrsn51 wrote:If you are using a Puppy with a newer kernel, like Precise 571, the foo2xxx driver requires a patch. It is posted here as foo2xxx_udev_patch_upup387-1.0.pet .

The installation procedure is:

1. Install the foo2xxx PET (if not done already)
2. Install the patch PET
3. Reboot the printer
4. Install the printer in CUPS (if not done already)
5. Print something

Please report back with your success or failure. This is important testing on your part.
now it is working just fine, thanx a lot :)