All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Snyder <jay.snyder@tycoelectronics.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: gs-8.64 -- cups-gs broken (by cups-config output)
Date: Tue, 3 Aug 2010 15:23:09 -0400	[thread overview]
Message-ID: <4C586C9D.9060808@tycoelectronics.com> (raw)
In-Reply-To: <mailman.47.1280852515.3621.openembedded-devel@lists.openembedded.org>

The problem seems to be caused by the cups-config program.

With my old build:
$/home/oe/build/tmp/staging/x86_64-linux/usr/bin/i686-angstrom-linux/cups-config 
--serverbin
/usr/lib/cups


With my current build:
$/home/oe/build-2010-07-29/tmp/sysroots/x86_64-linux/usr/bin/i686-angstrom-linux/cups-config 
--serverbin
/home/oe/build-2010-07-29/tmp/sysroots/i686-angstrom-linux/usr/lib/cups


It is the extra /home/oe/build-2010-07-29/tmp/sysroots/i686-angstrom-linux

on the beginning of the path that breaks things.

I am using the cups 1.4.3 recipe, and had been using cups 1.4.2 with my 
old build that was based on a git pull from 2009-dec-04.

Thanks,
Jay



      parent reply	other threads:[~2010-08-03 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.47.1280852515.3621.openembedded-devel@lists.openembedded.org>
2010-08-03 18:36 ` gs-8.64 -- cups-gs broken Jay Snyder
2010-08-03 19:23 ` Jay Snyder [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=4C586C9D.9060808@tycoelectronics.com \
    --to=jay.snyder@tycoelectronics.com \
    --cc=openembedded-devel@lists.openembedded.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.