[gs-bugs] [Bug 691306] "make -f base/unix-gcc.mak" no longer works

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Sat May 15 01:11:29 UTC 2010


http://bugs.ghostscript.com/show_bug.cgi?id=691306

--- Comment #1 from Hin-Tak Leung <hintak at ghostscript.com> 2010-05-15 01:11:28 UTC ---
(In reply to comment #0)
> Because of the FreeType integration the base/unix-gcc.mak and base/unixansi.mak
> files no longer work, both produce:
> 
> make: *** No rule to make target `obj/fapif.dev', needed by `obj/fapi.dev'. 
> Stop.
> 
> 
> Some of our customers continue to use these files instead of autogen.sh or
> ./configure, so dropping support for them will meet with some resistance.

I can fix the fapi.dev error (and will commit a change) - but there is another
problem further down, which is libtiff - one of libtiff's header file is
autoconf generated, so even if you do "make -f base/unix-gcc.mak", you will
still need new code to drive libtiff's ./configure.

Just ranting - base/unix-gcc.mak is almost the same as base/Makefile.in from
which ./configure generates Makefile, so customer who habitually edit
base/unix-gcc.mak can edit base/Makefile.in because running ./configure, and it
would come to almost the same thing.

-- 
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the gs-bugs mailing list