All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Boor <florian.boor@kernelconcepts.de>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] directfb: Allow native builds of directfb 1.7.6
Date: Wed, 11 Mar 2015 10:24:17 +0100	[thread overview]
Message-ID: <550009C1.80502@kernelconcepts.de> (raw)
In-Reply-To: <CAJ86T=WvZ=cU2GCQ=P3XPar-WhQvhZFX0MbPcL7ahtkiW8xrhA@mail.gmail.com>

Hi Arndre,

On 10.03.2015 23:32, Andre McCurdy wrote:
> Are you sure that excluding tslib-native from DEPENDS works? Since
> -lts is hardcoded in LDFLAGS (see directfb.inc) the linker won't run
> unless libts.so is found in sysroot (regardless of whether or not you
> configure with "--with-inputdrivers=none"). That being said, I don't
> know if -lts really needs to be hardcoded in LDFLAGS, it's been there
> since directfb was first imported into oe-core, with no explanation of
> comment.

yes it works - tested it and made sure that there was no native libts around
from a previous build.
But you are right, this hardcoded -lts in LDFLAGS looks strange. I can take a
look at this later since I need to build and test this anyway.

Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: +49 271-771091-15
and the reality of tomorrow.            Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904]        florian.boor@kernelconcepts.de
                                        http://www.kernelconcepts.de/en


  reply	other threads:[~2015-03-11  9:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 22:04 [PATCH v2] directfb: Allow native builds of directfb 1.7.6 Florian Boor
2015-03-10 22:32 ` Andre McCurdy
2015-03-11  9:24   ` Florian Boor [this message]
2015-03-11 23:42     ` Andre McCurdy

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=550009C1.80502@kernelconcepts.de \
    --to=florian.boor@kernelconcepts.de \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-core@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.