From mboxrd@z Thu Jan 1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] netpbm: Removal of netpbm config.mk
Date: Thu, 17 Oct 2024 16:07:46 +0100
Message-ID: <EC76C1E3-9C9A-4ADE-96EE-1171BA552768@ipfire.org>
In-Reply-To: <20241014165547.16073-1-adolf.belka@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0884218221368844847=="
List-Id: <development.lists.ipfire.org>
--===============0884218221368844847==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Reviewed-by: Michael Tremer <michael.tremer(a)ipfire.org>
> On 14 Oct 2024, at 17:55, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>=20
> - netpbm addon was removed from IPFire in April 2022. This configuration fi=
le was
> missed at that time.
>=20
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> config/netpbm/config.mk | 690 ----------------------------------------
> 1 file changed, 690 deletions(-)
> delete mode 100644 config/netpbm/config.mk
>=20
> diff --git a/config/netpbm/config.mk b/config/netpbm/config.mk
> deleted file mode 100644
> index 0cb85db6e..000000000
> --- a/config/netpbm/config.mk
> +++ /dev/null
> @@ -1,690 +0,0 @@
> -####This file was automatically created by 'configure.'
> -####Many variables are set twice -- a generic setting, then=20
> -####a system-specific override at the bottom of the file.
> -####
> -# This is a make file inclusion, to be included in all the Netpbm make
> -# files.
> -
> -# This file is meant to contain variable settings that customize the
> -# build for a particular target system configuration.
> -
> -# The distribution contains the file config.mk.in. You edit
> -# config.mk.in in ways relevant to your particular environment=20
> -# to create config.mk. The "configure" program will do this
> -# for you in simple cases.
> -
> -# Some of the variables that the including make file must set for this
> -# file to work:
> -#
> -# SRCDIR: The directory at the top of the Netpbm source tree. Note that
> -# this is typically a relative directory, and it must be relative to the
> -# make file that includes this file.
> -
> -DEFAULT_TARGET =3D nonmerge
> -#DEFAULT_TARGET =3D merge
> -
> -# Fiasco has some special requirements that make it fail to compile on
> -# some systems, and since it isn't very important, just set this to "N"
> -# and skip it on those systems unless you want to debug it and fix it.
> -# OpenBSD:
> -#BUILD_FIASCO =3D N
> -BUILD_FIASCO =3D Y
> -
> -# The following are commands for the build process to use. These values
> -# do not get built into anything.
> -
> -# The C compiler (including macro preprocessor)
> -#CC =3D gcc
> -# Note that 'cc' is usually an alias for whatever is the main compiler
> -# on a system, e.g. the GNU Compiler on Linux.
> -CC =3D cc
> -
> -# The linker.
> -LD =3D $(CC)
> -#LD =3D ld
> -#Tru64:
> -#LD =3D cc
> -#LD =3D gcc=20
> -
> -#If the linker identified above is a compiler that invokes a linker
> -#(as in 'cc foo.o -o foo'), set LINKERISCOMPILER. The main difference is
> -#that we expect a compiler to take linker options in the '-Wl,-opt1,val1'
> -#syntax whereas the actual linker would take '-opt1 val1'.
> -LINKERISCOMPILER=3DY
> -#If $(LD) is 'ld':
> -#LINKERISCOMPILER=3DN
> -
> -#LINKER_CAN_DO_EXPLICIT_LIBRARY means the linker specified above can
> -#take a library as just another link object argument, as in 'ld
> -#pnmtojpeg.o /usr/local/lib/libjpeg.so ...' as opposed to requiring a
> -#-l option as in 'ld pnmtojpeg.o -L/usr/local/lib -l jpeg'.
> -#This variable controls how 'libopt' gets built. Note that with some
> -#linkers, you can specify a shared library explicitly, but then it has
> -#to live in that exact place at run time. That's not good enough for us.
> -
> -LINKER_CAN_DO_EXPLICIT_LIBRARY=3DN
> -#GNU:
> -#LINKER_CAN_DO_EXPLICIT_LIBRARY=3DY
> -
> -# This is the name of the header file that declares the types
> -# uint32_t, etc. This name is used as #include $(INTTYPES_H) .
> -# Set to null if the types come automatically without including anything.
> -
> -# We have a report (2005.09.17) that on IRIX 5.3 with the native IDO
> -# cc, inttypes.h and sys/types.h conflict (and Netpbm programs include
> -# sys/types for other things), so for that environment, <inttypes.h>
> -# won't work, but "inttypes_netpbm.h" might.
> -
> -INTTYPES_H =3D <inttypes.h>
> -# Linux libc5:
> -#INTTYPES_H =3D <types.h>
> -# Solaris:
> -# Solaris has <sys/inttypes.h>, but it doesn't define int_fast2_t, etc.
> -#INTTYPES_H =3D "inttypes_netpbm.h"
> -# Others:
> -#INTTYPES_H =3D <sys/stdint.h>
> -#INTTYPES_H =3D <sys/types.h>
> -# The automatically generated Netpbm version:
> -#INTTYPES_H =3D "inttypes_netpbm.h"
> -
> -# HAVE_INT64 tells whether, assuming you include the header indicated by
> -# INTTYPES_H, you have the int64_t type and related stuff. (If you don't
> -# the build will omit certain code that does 64 bit computations).
> -HAVE_INT64 =3D Y
> -#HAVE_INT64 =3D N
> -
> -# WANT_SSE tells whether the build should use SSE instructions, via the the
> -# standard SSE intrinsics (operators such as '_mm_movemask_epi8'). SSE
> -# instructions are faster than traditional instructions, but aren't availa=
ble
> -# on all CPUs. Also, the standard intrinsics are not available in all
> -# compilers. Even if you say N here, Netpbm may still be built with some
> -# SSE exploitation (e.g. SSE floating point) because the compiler will=20
> -# do it automatically. You can add a -nomsse or -nomsse2 option to
> -# CFLAGS or CFLAGS_PERSONAL to stop that.
> -WANT_SSE =3D N
> -#WANT_SSE =3D Y
> -
> -# CC and LD are for building the Netpbm programs, which are not necessarily
> -# intended to run on the same system on which Make is running. But when w=
e=20
> -# build a build tool such as Libopt, it is meant to run only on the same=20
> -# system on which the Make is running. The variables below define programs
> -# to use to compile and link build tools.
> -CC_FOR_BUILD =3D $(CC)
> -LD_FOR_BUILD =3D $(LD)
> -CFLAGS_FOR_BUILD =3D $(CFLAGS_CONFIG)
> -LDFLAGS_FOR_BUILD =3D $(LDFLAGS)
> -
> -# WINDRES is the program that creates a linkable object file from=20
> -# a Windows Icon (.ico) file.
> -WINDRES =3D windres
> -
> -# MAKE is set automatically by Make to what was used to invoke Make.
> -
> -INSTALL =3D $(SRCDIR)/buildtools/install.sh
> -#Solaris:
> -#INSTALL =3D /usr/ucb/install
> -#Tru64:
> -#INSTALL =3D installbsd
> -#OSF1:
> -#INSTALL =3D $(SRCDIR)/buildtools/installosf
> -#Red Hat Linux:
> -#INSTALL =3D install
> -
> -# STRIPFLAG is the option you pass to the above install program to make it
> -# strip unnecessary information out of binaries.
> -STRIPFLAG =3D -s
> -# If you don't want to strip the binaries, just leave it null:
> -#STRIPFLAG =3D=20
> -
> -SYMLINK =3D ln -s
> -# At least some Windows environments don't have any concept of symbolic
> -# links, but direct copies are usually a passable alternative.
> -#SYMLINK =3D cp
> -
> -#MANPAGE_FORMAT is "nroff" or "cat". It determines in what format the
> -#pointer man pages are installed (ready to nroff, or ready to cat). =20
> -#A pointer man pages is just a single-paragraph pages that tells you there=
is
> -#no man page for the program, to look at the HTML documentation instead.
> -MANPAGE_FORMAT =3D nroff
> -#MANPAGE_FORMAT =3D cat
> -
> -AR =3D ar
> -RANLIB =3D ranlib
> -# IRIX, SCO don't have Ranlib:
> -#RANLIB =3D true
> -
> -# LEX is the beginning of a shell command that runs a Lex-like
> -# pattern matcher generator. Null string means there isn't any such
> -# command. That means the build will skip parts that need one.
> -
> -LEX =3D flex
> -# Solaris:
> -# LEX =3D flex -e
> -# Windows Mingw:
> -# LEX =3D
> -#=20
> -# LEX =3D lex
> -
> -# C compiler options=20
> -
> -# gcc:
> -# -ansi and -Werror should work too, but are not included
> -# by default because there's no point in daring the build to fail.
> -# -pedantic isn't a problem because it causes at worst a warning.
> -#CFLAGS =3D -O3 -ffast-math -pedantic -fno-common \
> -# -Wall -Wno-uninitialized -Wmissing-declarations -Wimplicit \
> -# -Wwrite-strings -Wmissing-prototypes -Wundef -Wno-unknown-pragm=
as
> -# The merged programs have a main_XXX subroutine instead of main(),
> -# which would cause a warning with -Wmissing-declarations or=20
> -# -Wmissing-prototypes.
> -#CFLAGS_MERGE =3D -Wno-missing-declarations -Wno-missing-prototypes
> -# A user of DEC Tru64 4.0F in May 2000 needed -DLONG_32 for ppmtompeg,
> -# but word size-sensitive code was removed from parallel.c in September 20=
04.
> -# A user of Tru64 5.1A in July 2003 needed NOT to have -DLONG_32. In
> -# theory, you need this if on your system, long is 32 bits and int is not.
> -# But it may be completely irrelevant today.
> -#Tru64:
> -#CFLAGS =3D -O2 -std1 -DLONG_32
> -#CFLAGS =3D -O2 -std1
> -#AIX:
> -#CFLAGS=3D -O3
> -#HP-UX:
> -#CFLAGS=3D -O3 -fPIC
> -#IRIX:
> -#CFLAGS=3D -n32 -O3
> -#Amiga with GNU compiler:
> -#CFLAGS=3D -m68020-60 -ffast-math -mstackextend=20
> -# You can add -noixemul for Amiga and successfully compile most of the=20
> -# programs. (Of the remaining ones, if you can supply your own strtod()=20
> -# function, most of them will build with -noixemul). So try building=20
> -# with 'make --keep-going CADD=3D-noixemul' first, then just 'make' to bui=
ld
> -# everything that failed for lack of the ixemul library in the first step.
> -# That way, the parts that don't required the ixemul library won't indicate
> -# a dependency on it.
> -#OpenBSD:
> -#CFLAGS =3D -I/usr/local/include
> -
> -# EXE is a suffix that the linker puts on any executable it generates.
> -# In cygwin, this is .exe and most programs deal with its existence without
> -# us having to know about it. Some don't though, so set this:
> -
> -EXE =3D
> -#Cygwin, DJGPP/Windows:
> -#EXE =3D .exe
> - =20
> -# linker options. =20
> -
> -# LDFLAGS is often set as an environment variable; A setting here overrid=
es
> -# it. So either make sure you want to override it, or do a "LDFLAGS +=3D"=
here.
> -
> -# LDFLAGS is usually not the right place for a -L option, because we put
> -# LDFLAGS _before_ our own -L options, so it would cancel out our
> -# specific selection of libraries. For example, if you say
> -# LDFLAGS=3D/usr/local/lib and an old copy of the libnetpbm is in
> -# /usr/local/lib, then you'd be linking against that old copy instead of
> -# the copy you just built, which is located by a -L option later on the
> -# link command. LIBS is the right variable for adding -L options. LIBS
> -# goes after any of our make files' own -L options.
> -
> -# Eunice users may want to use -noshare so that the executables can
> -# run standalone:
> -#LDFLAGS +=3D -noshare
> -#Tru64:
> -# Russ Allberry says on 2001.06.09 that -oldstyle_liblookup may be necessa=
ry
> -# to keep from finding an ancient system libjpeg.so that isn't compatible =
with
> -# NetPBM. Michael Long found that /usr/local/lib is not in the default
> -# search path, or not soon enough, and he was getting an old libjpeg that
> -# caused all the jpeg symbol references to be unresolved. He had installed
> -# a new libjpeg in /usr/local/lib.
> -#LDFLAGS +=3D -call_shared -oldstyle_liblookup -L/usr/local/lib
> -#AIX:
> -#LDFLAGS +=3D -L /usr/pubsw/lib
> -#HP-UX:
> -#LDFLAGS +=3D -Wl,+b,/usr/pubsw/lib
> -#IRIX:
> -#LDFLAGS +=3D -n32
> -
> -# Linker options for created Netpbm shared libraries.
> -
> -# Here, $(SONAME) resolves to the soname for the shared library being crea=
ted.
> -# The following are gcc options. This works on GNU libc systems.
> -LDSHLIB =3D -shared -Wl,-soname,$(SONAME)
> -# You need -nostart instead of -shared on BeOS. Though the BeOS compiler =
is
> -# ostensibly gcc, it has the -nostart option, which is not mentioned in gcc
> -# documentation and doesn't exist in at least one non-BeOS installation.
> -# BeOS doesn't have sonames built in.
> -#LDSHLIB =3D -nostart
> -#LDSHLIB =3D -G
> -# Solaris, SunOS with GNU Ld, SCO:
> -# These systems have no soname option.
> -#LDSHLIB =3D -shared
> -# Solaris with Sun Ld:
> -#LDSHLIB =3D -Wl,-Bdynamic,-G,-h,$(SONAME)=20
> -#Tru64:
> -#LDSHLIB =3D -shared -expect_unresolved "*"
> -#IRIX:
> -#LDSHLIB =3D -shared -n32
> -#AIX GNU compiler/linker:
> -#LDSHLIB =3D -shared
> -#AIX Visual Age C:
> -#LDSHLIB =3D -qmkshrobj
> -#Mac OSX:
> -# According to experiments done by Peter A Crowley in May 2007, if
> -# libnetpbm goes in a standard place such as /usr/local/lib,
> -# programs need not be built with libnetpbm's location included.
> -# But if it goes elsewhere, the link-editor must include the
> -# location in the executable. It finds the runtime location by
> -# looking inside the library. The information in the library
> -# comes from the install_name option with which the library was
> -# built. It's an alternative to the -rpath option on other systems.
> -#LDSHLIB=3D-dynamiclib
> -#LDSHLIB=3D-dynamiclib -install_name $(NETPBMLIB_RUNTIME_PATH)/libnetpbm.$=
(MAJ).dylib
> -
> -# LDRELOC is the command to combine two .o files (relocateable object file=
s)
> -# into a single .o file that can later be linked into something else. NONE
> -# means no such command is available.
> -
> -LDRELOC =3D NONE
> -# GNU Ld:
> -# Older GNU Ld misspells the option as --relocateable. Newer GNU Ld
> -# correctly spells it --relocatable. The abbreviation --reloc works on
> -# both.
> -#LDRELOC =3D ld --reloc
> -#LDRELOC =3D ld -r
> -
> -
> -# On older systems, you have to make shared libraries out of position
> -# independent code, so you need -fpic or fPIC here. (The rule is: if
> -# -fpic works, use it. If it bombs, go to fPIC). On newer systems,
> -# it isn't necessary, but can save real memory at the expense of
> -# execution speed. Without position independent code, the library
> -# loader may have to patch addresses into the executable text. On an
> -# older system, this would cause a program crash because the loader
> -# would be writing into read-only shared memory. But on newer
> -# systems, the system silently creates a private mapping of the page
> -# or segment being modified (the "copy on write" phenomenon). So it
> -# needs its own private real page frame. In one experiment, A second
> -# copy of Pbmtext used 16K less real memory when built with -fpic than
> -# when built without. 2001.06.02.
> -
> -# We have seen -fPIC required on IA64 and AMD64 machines (GNU
> -# compiler/linker). Build-time linking fails without it. I don't
> -# know why -- history seems to be repeating itself. 2005.02.23.
> -
> -CFLAGS_SHLIB =3D=20
> -# Gcc:
> -#CFLAGS_SHLIB =3D -fpic
> -#CFLAGS_SHLIB =3D -fPIC
> -# Sun compiler:
> -#CFLAGS_SHLIB =3D -Kpic
> -#CFLAGS_SHLIB =3D -KPIC
> -
> -# SHLIB_CLIB is the link option to include the C library in a shared libra=
ry,
> -# normally "-lc". On typical systems, this serves no purpose. On some,
> -# though, it causes information about which C library to use to be recorded
> -# in the shared library and thus choose the correct library among several =
or
> -# avoid using an incompatible one. But on some systems, the link fails.
> -# On 2002.09.30, "John H. DuBois III" <spcecdt(a)armory.com> reports that =
on=20
> -# SCO OpenServer, he gets the following error message with -lc:
> -#
> -# -lc; relocations referenced ; from file(s) /usr/ccs/lib/libc.so(rando=
m.o);
> -# fatal error: relocations remain against allocatable but non-writable=20
> -# section: ; .text
> -
> -SHLIB_CLIB =3D -lc
> -# SCO:
> -#SHLIB_CLIB =3D
> -
> -# On some systems you have to build into an executable the list of
> -# directories where its dynamically linked libraries can be found at
> -# run time. This is typically done with a -R or -rpath linker
> -# option. Even on systems that don't require it, you might prefer to do
> -# that rather than set up environment variables or configuration files
> -# to tell the system where the libraries are. A "Y" here means to put
> -# the directory information in the executable at link time.
> -
> -NEED_RUNTIME_PATH =3D N
> -# Solaris, SunOS, NetBSD, AIX:
> -#NEED_RUNTIME_PATH =3D Y
> -
> -# RPATHOPTNAME is the option you use on the link command to specify
> -# a runtime search path for a shared library. It is meaningless unless
> -# NEED_RUNTIME_PATH is Y.
> -RPATHOPTNAME =3D -rpath
> -
> -# The following variables tell where your various libraries on which
> -# Netpbm depends live. The LIBxxx variable is a full file
> -# specification of the link library (not necessarily the library used
> -# at run time). e.g. "/usr/local/lib/graphics/libjpeg.so". It usually
> -# doesn't matter if the library prefix and suffix are right -- you can
> -# use "lib" and ".so" or ".a" regardless of what your system actually
> -# uses because these just turn into "-L" and "-l" linker options
> -# anyway. ".a" implies a static library for some purposes, though.
> -# If you don't have the library in question, use a value of NONE for
> -# LIBxxx and the build will simply skip the programs that require that
> -# library. If the library is in your linker's (or the Netpbm build's)
> -# default search path, leave off the directory part, e.g. "libjpeg.so".
> -
> -# The xxxHDR_DIR variable is the directory in which the interface
> -# headers for the library live (e.g. /usr/include). If they are in your
> -# compiler's default search path, set this variable to null.
> -
> -# This is where the Netpbm shared libraries will reside when Netpbm is
> -# fully installed. In some configurations, the Netpbm builder builds
> -# this information into the Netpbm executables. This does NOT affect
> -# where the Netpbm installer installs the libraries. A null value
> -# means the libraries are in a default search path used by the runtime
> -# library loader.
> -NETPBMLIB_RUNTIME_PATH =3D=20
> -#NETPBMLIB_RUNTIME_PATH =3D /usr/lib/netpbm
> -
> -# The TIFF library. See above. If you want to build the tiff
> -# converters, you must have the tiff library already installed.
> -
> -TIFFLIB =3D NONE
> -TIFFHDR_DIR =3D
> -
> -#TIFFLIB =3D libtiff.so
> -#TIFFHDR_DIR =3D /usr/include/libtiff
> -#NetBSD:
> -#TIFFLIB =3D $(LOCALBASE)/lib/libtiff.so
> -#TIFFHDR_DIR =3D $(LOCALBASE)/include
> -# OSF, Tru64:
> -#TIFFLIB =3D /usr/local1/DEC/lib/libtiff.so
> -#TIFFHDR_DIR =3D /usr/local1/DEC/include
> -
> -# Some TIFF libraries do Jpeg and/or Z (flate) compression and thus any
> -# program linked with the TIFF library needs a Jpeg and/or Z library. Some
> -# TIFF libraries have such library statically linked in, but others need i=
t to
> -# be linked with the program at link-edit time or dynamically at program l=
oad
> -# time. Make this 'N' if your TIFF library doesn't need such linking. As=
of
> -# 2005.01, the most usual build of the TIFF library appears to require bot=
h.
> -TIFFLIB_NEEDS_JPEG =3D Y
> -TIFFLIB_NEEDS_Z =3D Y
> -
> -# The JPEG library. See above. If you want to build the jpeg
> -# converters you must have the jpeg library already installed.
> -
> -# Tiff files can use JPEG compression, so the Tiff library can reference
> -# the JPEG library. If your Tiff library references a dynamic JPEG=20
> -# library, you must specify at least JPEGLIB here, or the Tiff
> -# converters will not build. Note that your Tiff library may have the
> -# JPEG stuff statically linked in, in which case you won't need=20
> -# JPEGLIB in order to build the Tiff converters.
> -
> -JPEGLIB =3D NONE
> -JPEGHDR_DIR =3D
> -#JPEGLIB =3D libjpeg.so
> -#JPEGHDR_DIR =3D /usr/include/jpeg
> -# Netbsd:
> -#JPEGLIB =3D ${LOCALBASE}/lib/libjpeg.so
> -#JPEGHDR_DIR =3D ${LOCALBASE}/include
> -# OSF, Tru64:
> -#JPEGLIB =3D /usr/local1/DEC/libjpeg.so
> -#JPEGHDR_DIR =3D /usr/local1/DEC/include
> -# Typical:
> -#JPEGLIB =3D /usr/local/lib/libjpeg.so
> -#JPEGHDR_DIR =3D /usr/local/include
> -# Don't build JPEG stuff:
> -#JPEGLIB =3D NONE
> -
> -
> -# The PNG library. See above. If you want to build the PNG
> -# converters you must have the PNG library already installed.
> -
> -# The PNG library, by convention starting around April 2002, gets installed
> -# with names that include a version number, such as libpng10.a and header
> -# files in /usr/include/libpng10. But there is conventionally an unnumber=
ed
> -# alias (e.g. libpng.a, /usr/include/libpng) for the preferred version.
> -#
> -# Recent versions of the library (since some time in the 2002-2006 period)
> -# have an associated 'libpng-config' that tells how to link it. The make
> -# files will use that program if it exists (must be in the PATH). In that
> -# case, PNGLIB and PNGHDR_DIR are irrelevant, but PNGVER is still meaningf=
ul,
> -# because the make file runs 'libpng$(PNGVER)-config'.
> -#
> -# Even more recent versions have the more modern Pkgconfig database entry
> -# to tell how to link it. The make files will try to use that first.
> -#
> -# The normal way to choose the libpng the Netpbm build uses from among mul=
tiple
> -# versions on your system is not to mess with the variables below, but rat=
her
> -# to mess with PKG_CONFIG_PATH or PATH environment variable so that the ve=
rsion
> -# you want to use appears first in the search path.
> -
> -PNGLIB =3D NONE
> -PNGHDR_DIR =3D
> -PNGVER =3D=20
> -#PNGLIB =3D libpng$(PNGVER).so
> -#PNGHDR_DIR =3D /usr/include/libpng$(PNGVER)
> -# NetBSD:
> -#PNGLIB =3D $(LOCALBASE)/lib/libpng$(PNGVER).so
> -#PNGHDR_DIR =3D $(LOCALBASE)/include
> -# OSF/Tru64:
> -#PNGLIB =3D /usr/local1/DEC/lib/libpng$(PNGVER).so
> -#PNGHDR_DIR =3D /usr/local1/DEC/include
> -
> -# The zlib compression library. See above. You need it to build
> -# anything that needs the PNG library (see above). If you selected
> -# NONE for the PNG library, it doesn't matter what you specify here --
> -# it won't get used.
> -#
> -# If you have 'libpng-config' (see above), these are irrelevant.
> -
> -ZLIB =3D NONE
> -ZHDR_DIR =3D=20
> -#ZLIB =3D libz.so
> -
> -# The JBIG lossless image compression library (aka JBIG-KIT):
> -
> -JBIGLIB =3D $(INTERNAL_JBIGLIB)
> -JBIGHDR_DIR =3D $(INTERNAL_JBIGHDR_DIR)
> -
> -# The Jasper JPEG-2000 image compression library (aka JasPer):
> -JASPERLIB =3D $(INTERNAL_JASPERLIB)
> -JASPERHDR_DIR =3D $(INTERNAL_JASPERHDR_DIR)
> -# JASPERDEPLIBS is the libraries (-l options or file names) on which
> -# The Jasper library depends -- i.e. what you have to link into any
> -# executable that links in the Jasper library.
> -JASPERDEPLIBS =3D
> -#JASPERDEPLIBS =3D -ljpeg
> -
> -# And the Utah Raster Toolkit (aka URT aka RLE) library:
> -
> -URTLIB =3D $(BUILDDIR)/urt/librle.a
> -URTHDR_DIR =3D $(SRCDIR)/urt
> -
> -# The X11 library has facilities for talking to an X Window System
> -# server. It is required by Pamx.
> -
> -X11LIB =3D NONE
> -X11HDR_DIR =3D
> -
> -#X11LIB =3D /usr/lib/libX11.so
> -#X11HDR_DIR =3D
> -
> -# The Linux SVGA library (Svgalib) is a facility for displaying graphics
> -# on the Linux console. It is required by Ppmsvgalib.
> -
> -LINUXSVGALIB =3D NONE
> -LINUXSVGAHDR_DIR =3D=20
> -
> -#LINUXSVGALIB =3D /usr/lib/libvga.so
> -#LINUXSVGAHDR_DIR =3D /usr/include/vgalib
> -
> -# WINICON_OBJECT is the object file to bind into all Netpbm executables
> -# to provide the icon for Windows to use for it. Null for none.
> -WINICON_OBJECT =3D
> -#WINICON_OBJECT =3D $(BUILDDIR)/icon/netpbm.o
> -
> -# If you don't want any network functions, set OMIT_NETWORK to "Y".
> -# The only thing that requires network functions is the option in
> -# ppmtompeg to run it on multiple computers simultaneously. On some
> -# systems network functions don't work or we haven't figured out how to=20
> -# make them work, or they just aren't worth the effort. =20
> -OMIT_NETWORK =3D
> -#DJGPP/Windows, Tru64:
> -# (there's some minor header problem that prevents network functions fro=
m=20
> -# building on Tru64 2000.10.06)
> -#OMIT_NETWORK =3D Y
> -
> -# These are -l options to link in the network libraries. Often, these are
> -# built into the standard C library, so this can be null. This is irrelev=
ant
> -# if OMIT_NETWORK is "Y".
> -
> -NETWORKLD =3D=20
> -# Solaris, SunOS:
> -#NETWORKLD =3D -lsocket -lnsl
> -# SCO:
> -#NETWORKLD =3D -lsocket, -lresolv
> -
> -# DONT_HAVE_PROCESS_MGMT is Y if this system doesn't have the usual
> -# Unix process management stuff - fork, wait, etc. N for a regular Unix
> -# system.
> -DONT_HAVE_PROCESS_MGMT =3D N
> -
> -# The following variables are used only by 'make install' (and the
> -# variants of it). Paths here don't, for example, get built into any
> -# programs.
> -
> -# This is where everything goes when you do 'make package', unless you
> -# override it by setting 'pkgdir' on the Make command line.
> -PKGDIR_DEFAULT =3D /tmp/netpbm
> -
> -# This is where test results are written when you do 'make check', unless
> -# you override it by setting 'resultdir' on the Make command line.
> -RESULTDIR_DEFAULT =3D /tmp/netpbm-test
> -
> -# Subdirectory of the package directory ($(pkgdir)) in which man pages
> -# go.
> -PKGMANDIR =3D share/man
> -
> -# File permissions for installed files.
> -# Note that on some systems (e.g. Solaris), 'install' can't use the=20
> -# mnemonic permissions - you have to use octal.
> -
> -# binaries (pbmmake, etc)
> -INSTALL_PERM_BIN =3D 755 # u=3Drwx,go=3Drx
> -# shared libraries (libpbm.so, etc)
> -INSTALL_PERM_LIBD =3D 755 # u=3Drwx,go=3Drx
> -# static libraries (libpbm.a, etc)
> -INSTALL_PERM_LIBS =3D 644 # u=3Drw,go=3Dr
> -# header files (pbm.h, etc)
> -INSTALL_PERM_HDR =3D 644 # u=3Drw,go=3Dr
> -# man pages (pbmmake.1, etc)
> -INSTALL_PERM_MAN =3D 644 # u=3Drw,go=3Dr
> -# data files (pnmtopalm color maps, etc)
> -INSTALL_PERM_DATA =3D 644 # u=3Drw,go=3Dr
> -
> -# Specify the suffix that want the man pages to have.
> -
> -SUFFIXMANUALS1 =3D 1
> -SUFFIXMANUALS3 =3D 3
> -SUFFIXMANUALS5 =3D 5
> -
> -#NETPBMLIBTYPE tells the kind of libraries that will get built to hold the
> -#Netpbm library functions. The value is used only in make file tests.
> -# "unixshared" means a unix-style shared library, typically named like=20
> -# libxyz.so.2.3
> -NETPBMLIBTYPE =3D unixshared
> -# "unixstatic" means a unix-style static library, (like libxyz.a)
> -#NETPBMLIBTYPE =3D unixstatic
> -# "dll" means a Windows DLL shared library
> -#NETPBMLIBTYPE =3D dll
> -# "dylib" means a Darwin/Mac OS shared library
> -#NETPBMLIBTYPE =3D dylib
> -
> -#NETPBMLIBSUFFIX is the suffix used on whatever kind of library is=20
> -#selected above. All this is used for is to construct library names.
> -#The make files never examine the actual value.
> -NETPBMLIBSUFFIX =3D so
> -
> -# "a" is the suffix for unix-style static libraries. It is also
> -# traditionally used for shared libraries on AIX. The Visual Age C
> -# manual says sometimes .so works on AIX, and GNU software for AIX
> -# 5.1.0 does indeed use it. In our experiments, it works fine if you
> -# name the library file explicitly on the link, but isn't in the -l
> -# search order. If you name the library explicitly on the link, the
> -# library must live in exactly the same position at run time, so we
> -# can't use that. Therefore, you cannot build both static and shared
> -# libraries with AIX. You have to choose.
> -#NETPBMLIBSUFFIX =3D a
> -# For HP-UX shared libraries:
> -#NETPBMLIBSUFFIX =3D sl
> -# Darwin/Mac OS shared library:
> -#NETPBMLIBSUFFIX =3D dylib
> -# Windows shared library:
> -#NETPBMLIBSUFFIX =3D dll
> -
> -#STATICLIB_TOO is "Y" to signify that you want a static library built
> -#and installed in addition to whatever library type you specified by
> -#NETPBMLIBTYPE. If NETPBMLIBTYPE specified a static library,
> -#STATICLIB_TOO simply has no effect.
> -STATICLIB_TOO =3D Y
> -#STATICLIB_TOO =3D N
> -
> -#STATICLIBSUFFIX is the suffix that static libraries have. It's
> -#meaningless if you aren't building static libraries.
> -STATICLIBSUFFIX =3D a
> -
> -#SHLIBPREFIXLIST is a blank-delimited list of prefixes that a filename
> -#of a shared library may have on this system. Traditionally, it's
> -#just "lib", as in libc or libnetpbm. On Windows, though, varying
> -#prefixes are used when multiple alternative forms of a library are
> -#available. The first prefix in this list is what we use to name the
> -#Netpbm shared libraries.
> -#
> -# This variable controls how 'libopt' gets built.
> -#
> -SHLIBPREFIXLIST =3D lib
> -#Cygwin:
> -#SHLIBPREFIXLIST =3D cyg lib
> -
> -NETPBMSHLIBPREFIX =3D $(firstword $(SHLIBPREFIXLIST))
> -
> -#DLLVER is used to version the DLLs built on cygwin or other
> -#windowsish platforms. We can't add this to LIBROOT, or we'd
> -#version the static libs (which is bad). We can't add this
> -#at the end of the name (like unix does with so numbers) because
> -#windows will only load dlls whose name ends in "dll". So,
> -#we have this variable, which becomes the end of the library "root" name
> -#for DLLs only.
> -#
> -# This variable controls how 'libopt' gets built.
> -#
> -DLLVER =3D
> -#Cygwin
> -#DLLVER =3D $(NETPBM_MAJOR_RELEASE)
> -
> -#NETPBM_DOCURL is the URL of the main documentation page for Netpbm.
> -#This is a directory which contains a file for each Netpbm program,
> -#library, and file type. E.g. The documentation for jpegtopnm might be in
> -#http://netpbm.sourceforge.net/doc/jpegtopnm.html . This value gets
> -#installed in the man pages (which say no more than to read the webpage)
> -#and in the Manweb netpbm.url file.
> -NETPBM_DOCURL =3D http://netpbm.sourceforge.net/doc/
> -#For a system with no web access, but a local copy of the doc:
> -#NETPBM_DOCURL =3D file:/usr/doc/netpbm/
> -
> -# RGB_DB_PATH is where Netpbm looks for the color database when the RGBDEF
> -# environment variable is not set. See pm_config_in.h for details.
> -RGB_DB_PATH =3D /usr/share/netpbm/rgb.txt:/usr/lib/X11/rgb.txt:/usr/share/=
X11/rgb.txt:/usr/X11R6/lib/X11/rgb.txt
> -
> -
> -
> -
> -####Lines above were copied from config.mk.in by 'configure'.
> -####Lines below were added by 'configure' based on the GNU platform.
> -DEFAULT_TARGET =3D nonmerge
> -NETPBMLIBTYPE=3Dunixshared
> -NETPBMLIBSUFFIX=3Dso
> -STATICLIB_TOO=3DN
> -CFLAGS =3D -O3 -ffast-math -pedantic -fno-common -Wall -Wno-uninitialized=
-Wmissing-declarations -Wimplicit -Wwrite-strings -Wmissing-prototypes -Wund=
ef -Wno-unknown-pragmas
> -CFLAGS_MERGE =3D -Wno-missing-declarations -Wno-missing-prototypes
> -LDRELOC =3D ld --reloc
> -LINKER_CAN_DO_EXPLICIT_LIBRARY=3DY
> -LINKERISCOMPILER =3D Y
> -CFLAGS_SHLIB +=3D -fPIC
> -TIFFLIB =3D libtiff.so
> -JPEGLIB =3D libjpeg.so
> -ZLIB =3D libz.so
> -NETPBM_DOCURL =3D http://netpbm.sourceforge.net/doc/
> --=20
> 2.47.0
>=20
--===============0884218221368844847==--