All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Meeuwissen <olaf.meeuwissen@avasys.jp>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: toratani.yasumasa@canon.co.jp,
	printing-architecture@lists.linux-foundation.org,
	Koji Otani <sho@bbr.jp>
Subject: Re: [Printing-architecture] PDF CUPS filter packages
Date: Thu, 05 Jun 2008 08:16:48 +0900	[thread overview]
Message-ID: <87ve0odc4f.fsf@geek.avasys.jp> (raw)
In-Reply-To: <484683B0.2060708@gmail.com> (Till Kamppeter's message of "Wed\, 04 Jun 2008 13\:59\:44 +0200")

Till Kamppeter <till.kamppeter@gmail.com> writes:

> Thank you, now the package rebuilds correctly for me. Next step to fix 
> now for you is to eliminate the necessity of full copies of the Poppler 
> and CUPS source code in the package.

For the record, the "errors" were caused by telling gcc to treat
warnings as errors (see snippet below).  I have not checked the
opfc-pdf-filters sources but this is not the default gcc behaviour,
AFAIK.

  make[2]: Entering directory 
  `/home/till/ubuntu/opfc-pdf-filters/tmp/opfc-pdf-filters-0.4/pdftopdf/src'
  g++ -DHAVE_CONFIG_H -I. -I.. 
  -I/home/till/ubuntu/opfc-pdf-filters/tmp/opfc-pdf-filters-0.4/poppler-0.6//poppler 
  -I/home/till/ubuntu/opfc-pdf-filters/tmp/opfc-pdf-filters-0.4/poppler-0.6/ 
  -DCONFFILE_DIR=\"/etc/cups\" -DPDFTOPDF 
  -I/home/till/ubuntu/opfc-pdf-filters/tmp/opfc-pdf-filters-0.4/poppler-0.6//poppler 
    -Wall -Werror -g -O2 -MT pdf2pdf-P2PCatalog.o -MD -MP -MF 
  .deps/pdf2pdf-P2PCatalog.Tpo -c -o pdf2pdf-P2PCatalog.o `test -f 
  'P2PCatalog.cc' || echo './'`P2PCatalog.cc
  cc1plus: warnings being treated as errors

While I am generally inclined to do this myself, it is a bit of a
mixed blessing as not all gcc versions of all distribution flag the
same things as warnings.  If adding your own warnings to -Wall, you
will very likely compound the issue.

In this particular case, converting string constants to `char *`, I
would say it should be fixed.

> [snip]

Hope this helps,
-- 
Olaf Meeuwissen                   FLOSS Engineer -- AVASYS Corporation
FSF Associate Member #1962           sign up at http://member.fsf.org/

  reply	other threads:[~2008-06-04 23:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03  6:43 [Printing-architecture] PDF CUPS filter packages TORATANI Yasumasa
2008-06-03 13:06 ` Till Kamppeter
     [not found]   ` <20080604.105602.104056266.sho@bbr.jp>
2008-06-04  9:07     ` Till Kamppeter
     [not found]       ` <20080604.181746.02274177.sho@bbr.jp>
2008-06-04 11:59         ` Till Kamppeter
2008-06-04 23:16           ` Olaf Meeuwissen [this message]
     [not found]             ` <20080605.181530.212681540.sho@bbr.jp>
2008-06-05 23:35               ` Olaf Meeuwissen
     [not found]           ` <20080605.153828.28801505.sho@bbr.jp>
2008-06-05  7:25             ` Till Kamppeter
     [not found]               ` <20080605.193227.233691471.sho@bbr.jp>
2008-06-05 10:53                 ` Till Kamppeter
     [not found]                   ` <20080606.145117.189705417.sho@bbr.jp>
2008-06-06  6:55                     ` Till Kamppeter
2008-06-05 21:34                 ` Till Kamppeter
2008-06-05 21:46                 ` Till Kamppeter
2008-06-05 22:07                 ` Till Kamppeter

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=87ve0odc4f.fsf@geek.avasys.jp \
    --to=olaf.meeuwissen@avasys.jp \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=sho@bbr.jp \
    --cc=till.kamppeter@gmail.com \
    --cc=toratani.yasumasa@canon.co.jp \
    /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.