pdftk compiling problems on FreeBSD

[=?big5?q?Patrick=20Dung?=]

Thank you for helping.
 
I am trying your solution.
 
But the directory structure is like this:
# ls -l
total 26
drwxr-xr-x  2 root  wheel   512 Mar  8 09:04 debian
drwxr-xr-x  5 root  wheel   512 Mar 18 18:03 itext-1.1
drwxr-xr-x  2 root  wheel   512 Mar 18 18:03 pdftk
-rw-r--r--  1 root  wheel  8404 Mar  8 09:05  pdftk.1.manpage.txt

The problem Makefile is in itext-1.1.
 
The post-patch doesn't seem to run recursively inside the itext-1.1.
 
Regards
Patrick

Oliver Eikemeier <eikemeier at fillmore-labs.com> wrote:
Patrick Dung wrote:

> Thank you.
> 
> I am now making the files the the ports.
> It can now fetch the tarball from the pdftk website.
> I am fighting with the Makefile.
> 
> Now I have encountered one problem. My machine is a FreeBSD 4.9.
> It does not have gcj and gcjh (gcc 3.x stuff). After installing the 
> gcc33 port, gcc33, g++33, gcj33, gcjh33 are created.
> The problem is that the Makefiles in the pdftk tarball hardcoded to use 
> the name of the binaries (e.g., g++, gcj, gcjh) instead of macros.
> The number of Makefiles is not small, I think I would be silly to make 
> many patch files for them.

Maybe something like

USE_REINPLACE=yes

post-patch:
@${FIND} ${WRKSRC} -type f -name Makefile | \
${XARGS} ${REINPLACE_CMD} -Ee "s/[[:<:]]g\+\+/g\1${CXX}/g" \
-e "s/[[:<:]]gc(c|jh?)[[:>:]]/gc\1${CC:S/^gcc//}/g" \;

will help? Otherwise using macros in the Makefiles seems like a good idea
to me.

Oliver
¥²±þ§Þ¡B¶¼ºq¡B¤p¬P¬P...
®öº©¹aÁn  ±¡¤ß³sô
http://ringtone.yahoo.com.hk/