On Tue, Dec 05, 2006 at 11:50:48AM +0100, Karel Kulhavy wrote: > Hello > > I want to use xpm2ppm, but it doesn't work because it says > [EMAIL PROTECTED]:~$ xpmtoppm < vnc/img_00000.xpm > xpmtoppm: Input file has line that is too long (longer than 2048 bytes). > > Obviously, someone programmed with fixed-size buffers. > > I would like to increase the compiled-in buffer size from 2048 to 4096 and > try again. I would like to get the source for netpbm somewhere, change it > and compile. However it turns out to be an impenetrable obstacle: > > - The OpenBSD website describes only some CVS method which seems to involve > getting > sources for all programs in the operating system and I don't have space for
Nope, again, you read wrong. For netpbm, you just have to grab the ports tree. Maybe you should have followed the obvious link `Application packages' and read the fine document there. > that: Filesystem 512-blocks Used Avail Capacity Mounted on > /dev/wd0a 74935160 70114912 1073492 98% / > - Getting sources -> web -> ports -> graphics -> netpbm there are no sources, > only some auxilliary files Of course there are no sources ! but there is a plain indication of where sources are in the Makefile. > - when I download the official netpbm 10.26.34 source and say "y enter > openbsd enter enter enter enter library filename or 'none' [libjpeg.so] > libjpeg.so.62.0 JPEG header directory [default] ==> /usr/local/include > libtiff.so.37.3 /usr/local/include libpng.so.4.2 /usr/local/include > libz.so.4.1 /usr/local/include" (the filenames were determined using locate), > the compilation of netpbm crashes with > libopt results: ' -L/home/clock/netpbm-10.26.34/lib -lnetpbm -ljpeg.so.62' > /usr/bin/ld: cannot find -ljpeg.so.62 > collect2: ld returned 1 exit status > gmake[3]: *** [ppmtompeg] Error 1 > gmake[3]: Leaving directory > `/home/clock/netpbm-10.26.34/converter/ppm/ppmtompeg > Is it possible to compile netpbm on openbsd from the sources without extensive > OpenBSD maintainer expertise? Yes, people routinely manage to do it. But they read the documentation, and don't try to reinvent stuff from scratch. Read the ports documentation. man ports for starters. Basically, all you have to do is untar the ports tarball under /usr/ports (which is reasonably SMALL for your needs, under 30M), then cd graphics/netpbm, and type `make'. You are insisting on doing things your own way. Wishful thinking does not replace reading the documentation. Why don't you try slowing down and reading through stuff ? Are you deficient ? I've got the impression you read one word out of five and skip through most documents like you already know what they contain... By now, it should be painfully obvious that you don't have a clue.
