All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmx.net>
To: Norm Jacobs <Norm.Jacobs@Sun.COM>
Cc: printing-architecture <printing-architecture@freestandards.org>,
	"desktop_printing@osdl.org" <desktop_printing@osdl.org>
Subject: [Printing-architecture] Building PAPI implementation
Date: Wed, 17 May 2006 15:28:03 +0200	[thread overview]
Message-ID: <446B24E3.2080702@gmx.net> (raw)

Now I am trying to build the PAPI package from
http://openprinting.sourceforge.net/ I am building the current
Subversion state, rev 164.

There I have encountered some problems:

- At first I needed to patch the build infrastructure a little bit to
make it compiling the Apache support. The patch on the acinclude.m4 file
you can find here:

http://www.linuxprinting.org/till/tmp/papi-1.0-acinclude-m4-apache-apr1.patch

- Then I had a problem building the software, as
source/mod_ipp/mod_ipp.c includes the file apr_compat.h in case of
building with Apache support. According to

http://www.apache.org/dist/apr/CHANGES-APR-1.2

this header file was removed on the transition from APR 0.9.5 to 1.0.0
and I have 1.2.7 on Mandriva's Cooker. So here the Apache module needs
to be updated to the current Apache/APR API.

   Till


             reply	other threads:[~2006-05-17 13:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 13:28 Till Kamppeter [this message]
2006-05-17 14:32 ` [Printing-architecture] Re: Building PAPI implementation Norm Jacobs
2006-05-17 21:03   ` Till Kamppeter
2006-05-18  9:48     ` [Desktop_printing] " Till Kamppeter
2006-05-18 15:29       ` Till Kamppeter
2006-05-18 19:02         ` Norm Jacobs
2006-05-18 21:24           ` Till Kamppeter
2006-05-18 22:25             ` Till Kamppeter
2006-05-19  3:35               ` Norm Jacobs
2006-05-19  9:38                 ` Till Kamppeter
2006-05-19 12:13                   ` Norm Jacobs

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=446B24E3.2080702@gmx.net \
    --to=till.kamppeter@gmx.net \
    --cc=Norm.Jacobs@Sun.COM \
    --cc=desktop_printing@osdl.org \
    --cc=printing-architecture@freestandards.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.