From: Juergen Beisert <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: bilal.tas@dcl.com.tr
Subject: Re: [ptxdist] ptxdist-2014.01.0 with OSELAS.Toolchain-2013.12.1 kobs-ng.compile
Date: Mon, 10 Feb 2014 09:59:55 +0100 [thread overview]
Message-ID: <201402100959.55622.jbe@pengutronix.de> (raw)
In-Reply-To: <201402100940.07531.jbe@pengutronix.de>
Hi Bilal,
On Monday 10 February 2014 09:40:07 Juergen Beisert wrote:
> On Friday 07 February 2014 12:17:06 bilal.tas@dcl.com.tr wrote:
> > [...]
> >
> > `/opt/BSP-Phytec-phyFLEX-i.MX6-PD13.1.0/platform-phyFLEX-i.MX6/build-targ
> >et/kobs-ng-12.02.01/src' make[1]: *** [all-recursive] Error 1 make[1]:
> > Leaving directory
> > `/opt/BSP-Phytec-phyFLEX-i.MX6-PD13.1.0/platform-phyFLEX-i.MX6/build-targ
> >et/kobs-ng-12.02.01' make: ***
> > [/opt/BSP-Phytec-phyFLEX-i.MX6-PD13.1.0/platform-phyFLEX-i.MX6/state/kobs
> >-ng.compile] Error 2
>
> Like your Qt build issue: Sounds like a host compiler/library issue. Ask
> your BSP vendor about the host requirements to be able to build their
> PTXdist based project.
Ups, sorry. Forget this answer. (I need more caffeine first...)
"kobs-ng" isn't a package from PTXdist. Its seems it comes from your BSP. Ask
your BSP vendor about an update for this specific package to be able to build
it with a more recent toolchain.
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-02-10 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 11:17 bilal.tas
2014-02-10 8:40 ` Juergen Beisert
2014-02-10 8:59 ` Juergen Beisert [this message]
2014-02-10 9:05 ` [ptxdist] ptxdist-2014.01.0 with OSELAS.Toolchain-2013.12.1kobs-ng.compile Bilal TAŞ
-- strict thread matches above, loose matches on Subject: below --
2014-02-07 10:01 [ptxdist] ptxdist-2014.01.0 with OSELAS.Toolchain-2013.12.1 kobs-ng.compile bilal.tas
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=201402100959.55622.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=bilal.tas@dcl.com.tr \
--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