From: Ojas Kulkarni <Ojas.Kulkarni@minelab.com.au>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: [ptxdist] Failure in using OSELAS 2016.06.1 toolchain with PTXdist 2017.03.0
Date: Mon, 27 Mar 2017 23:17:30 +0000 [thread overview]
Message-ID: <ME1PR01MB0692FC670F8D6B51523C8D14DB330@ME1PR01MB0692.ausprd01.prod.outlook.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1169 bytes --]
Hello,
I am trying to build 2016.06.1 toolchain with PTXdist 2017.03.0 version. I am getting error in glib package while building toolchain shown below,
My questions are,
1) Is any compatibility issues observed with specified versions?
2) Which version of OSELAS toolchain is best suitable to use with PTXdist 2017.03.0 version?
Below is the snap of error,
[cid:image003.png@01D2A7A8.5059EA60]
Regards,
Ojas
Disclaimer
The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.
[-- Attachment #1.1.2: Type: text/html, Size: 6088 bytes --]
[-- Attachment #1.2: image003.png --]
[-- Type: image/png, Size: 83639 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2017-03-27 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 23:17 Ojas Kulkarni [this message]
2017-03-28 7:34 ` Juergen Borleis
2017-03-28 12:24 ` Clemens Gruber
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=ME1PR01MB0692FC670F8D6B51523C8D14DB330@ME1PR01MB0692.ausprd01.prod.outlook.com \
--to=ojas.kulkarni@minelab.com.au \
--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