From: Alexander Aring <alex.aring@gmail.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] ptxdist-2013.01.0 Cups support required but cups-config notlocated. Make sure cups-devel related files are installed.
Date: Wed, 27 Aug 2014 10:02:31 +0200 [thread overview]
Message-ID: <20140827080229.GA3103@omega> (raw)
In-Reply-To: <5286ad27de15b63b7e39e97f5e17bf81@dcl.com.tr>
On Tue, Aug 26, 2014 at 03:08:06PM +0300, Bilal TAŞ wrote:
>
>
> Hello
>
> I'm trying build cups with ptxdist-2013.01.0. I see this
> error, Do you have any idea ?
>
No you compiling samba here. Samba uses cups (libcups) to provide a
windows printer share, that's why configure fails. Because samba can't
find the libcups and dev files, etc...
I remember that cups has a buildsystem which isn't made for cross compiling.
You need to change the buildsystem to cross compiling it.
Another solution would be a cross compiling sandbox system like
scratchbox [0]. I don't know what's the state of this project is and you
need to do the same effort like to fix cups buildsystem for cross compiling.
It's difficult to handle with scratchbox, but it can handle better
buildsystem which are not made for cross compiling.
Example "replacing /usr/bin/gcc with cross compiler instead setting env", I
think ptxdist set CC variables or something else only.
For example if a Makefile contains the call "gcc -o bar foo.c" it will
call the gcc from your PATH. This is not cross compile friendly. Correct
would be a "$(CC) -o bar foo.c" - which is cross compile friendly
because you can change the compile call.
I don't want to say scratchbox is better than ptxdist, it's only another
solution to cross compile software which are not made to cross compile and
when you will merge ptxdist and scratchbox I think you can forget it anyway.
("it's for experts only").
> ---------------------
> target:
> samba.prepare
> ---------------------
not cups here, it's samba.
- Alex
[0] http://www.scratchbox.org/
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2014-08-27 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 12:08 Bilal TAŞ
2014-08-26 13:52 ` Bruno Thomsen
2014-08-27 6:21 ` [ptxdist] ptxdist-2013.01.0 Cups support required butcups-config notlocated. Make sure cups-devel rel?==?UTF-8?Q?ated " Bilal TAŞ
2014-08-27 8:08 ` [ptxdist] ptxdist-2013.01.0 Cups support required butcups-config?notlocated. " Alexander Aring
2014-08-27 10:19 ` [ptxdist] ptxdist-2013.01.0 Cups support requiredbutcups-config?notlocated. Make sure cups-devel rel?==?UTF-8?Q?ated filesare installed Bilal TAŞ
2014-08-27 8:06 ` [ptxdist] ptxdist-2013.01.0 Cups support required but cups-config notlocated. Make sure cups-devel related files are installed Alexander Aring
2014-08-29 8:45 ` Juergen Borleis
2014-08-29 9:01 ` Alexander Aring
2014-08-29 9:09 ` Juergen Borleis
2014-08-27 8:02 ` Alexander Aring [this message]
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=20140827080229.GA3103@omega \
--to=alex.aring@gmail.com \
--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