mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Pawel Suchanecki <pawel.suchanecki@gmail.com>
To: "Jürgen Beisert" <jbe@pengutronix.de>
Cc: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] cups: Add new package
Date: Mon, 22 Jul 2013 14:36:10 +0200	[thread overview]
Message-ID: <CACbe1rsO=NNyStpFg=k1y3T=5L0mtxnhDP2KJJ--aULFXj4tPA@mail.gmail.com> (raw)
In-Reply-To: <201307221036.56865.jbe@pengutronix.de>


[-- Attachment #1.1: Type: text/plain, Size: 3076 bytes --]

Jurgen,

2013/7/22 Jürgen Beisert <jbe@pengutronix.de>

> Hi Pawel,
>
> On Saturday 20 July 2013 22:45:11 Pawel Suchanecki wrote:
> > A year ago you wrote:
> >> Seems like my own patches when I tried with CUPS-1.4.8. CUPS is a mess
> >> regarding to cross compile:
> >>
> >> http://www.cups.org/str.php?L2390:
> >> "We currently do not support cross-compiling CUPS, nor do we have plans
> to
> >>  do so."
> >
> > I did cross-compile CUPS-1.6.2 using OSELAS toolchain 2012.12.1 for
> > Mini2440:
> >
> > .../mini2440_custom_packages/cups-1.6.2 $ file scheduler/cupsd
> > scheduler/cupsd: ELF 32-bit LSB shared object, ARM, version 1 (SYSV),
> > dynamically linked (uses shared libs), for GNU/Linux 2.6.32, not
> > stripped
> >
> > although I had to do some manual tweaks in Makefiles. I am currently
> > stuck at trying to install manually on the target.
> >
> > Do you possibly plan to include the recipe for CUPS into ptxdist
> > somewhere in the near future?
>
> It needs more tests and due to the lack of time I'm still stuck at the
> older
> release of CUPS.
>

It seems that you have some version of the CUPS package covered.
It is it available in some release of PTX? I need at least 1.4.x version to
support Zebra printer.


>
> What is your problem? Does the "make install" fails in the CUPS package or
> do
> you need help to find all relevant components which makes CUPS running on
> your
> target (to be able to fill the 'targetinstall' stage in the rule file)?
>

To be honest, I did not use `newpackage' functionality from ptxdist, I went
with manual compilation just using the OSELAS tool-chain instead.

I clearly understand the benefits of using `newpackage' in the long run but
I don't suppose it can help me with my troubles as for now, unless I
misunderstood something.

My CUPS 1.6.x, built 'by hand', is working but only partially. The CUPS
system works, but I am unable to print.
At first, it was due to lack of `cups-filters', which I fail to compile
manually, as it tires to link against stdc from build machine (I guess this
is where ptxdist could help me). Event if it builds it is going to miss
some dependencies (libraries) on target, that ptxdist does not provide
builds for.

So I end up with getting some prebuilt armv4t cups-filters 1.4.x from `
http://shr-project.org/' and tried to couple them with my CUPS 1.6.x build,
but I have 'Filter failed' message as CUPS response.

I am now trying to find out if it will work with 1.4.x CUPS form SHR or if
there is still some problem with my manual installation.

I guess I am writing this to get some insight from more experienced people
(namely you) on how can I install *working* CUPS on Mini2440. I just need
it to print PNG format pixmaps as project requirement.

Is there any way to incorporate the recipe (I assume you have one) for
older CUPS into my ptxdist built distro?

I know this is getting off-topic, sorry about that, but if you could shed
some light... I would greatly appreciate it.

Thanks,
Pawel

[-- Attachment #1.2: Type: text/html, Size: 3811 bytes --]

[-- Attachment #2: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2013-07-22 12:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-20 20:45 Pawel Suchanecki
2013-07-22  8:36 ` Jürgen Beisert
2013-07-22 12:36   ` Pawel Suchanecki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-05-28 12:42 Bart vdr. Meulen
2012-05-30  7:39 ` Michael Olbrich
2012-05-30  8:09   ` Juergen Beisert

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='CACbe1rsO=NNyStpFg=k1y3T=5L0mtxnhDP2KJJ--aULFXj4tPA@mail.gmail.com' \
    --to=pawel.suchanecki@gmail.com \
    --cc=jbe@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox