mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Patrick Murray <Patrick.Murray@daktronics.com>
To: Michael Olbrich <m.olbrich@pengutronix.de>,
	"ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] migrating a BSP from 2012.03.0 to 2019.03.1 ,
Date: Fri, 12 Apr 2019 15:27:20 +0000	[thread overview]
Message-ID: <DM6PR02MB5977E7EBDD5AD5C9AADD5A9BFD280@DM6PR02MB5977.namprd02.prod.outlook.com> (raw)
In-Reply-To: <20190412141234.tcdwjyy7fsw4e3hi@pengutronix.de>

That was a path problem.

I am now getting an error "git binary diffs"

applying '0053-ENGR00141654-Mx53-SMD-Add-audio-support-for-upgradin.patch'
patching file arch/arm/mach-mx5/board-mx53_loco.c
patching file arch/arm/mach-mx5/board-mx53_smd.c
applying '0054-ENGR00141732-SDMA-Fix-bootup-stop-at-sdma-firmware-l.patch'
patching file drivers/dma/imx-sdma.c
patching file firmware/Makefile
File firmware/imx/sdma/sdma-imx25-to1.bin: git binary diffs are not supported.
File firmware/imx/sdma/sdma-imx31-to1.bin: git binary diffs are not supported.
File firmware/imx/sdma/sdma-imx31-to2.bin: git binary diffs are not supported.
File firmware/imx/sdma/sdma-imx35-to1.bin: git binary diffs are not supported.
File firmware/imx/sdma/sdma-imx35-to2.bin: git binary diffs are not supported.
File firmware/imx/sdma/sdma-imx50-to1.bin: git binary diffs are not supported.
File firmware/imx/sdma/sdma-imx51-to3.bin: git binary diffs are not supported.
File firmware/imx/sdma/sdma-imx53-to1.bin: git binary diffs are not supported.
make: *** [/opt/lib/ptxdist-2019.03.1/rules/post/ptxd_make_world_extract.make:34: /opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/state/kernel-header.extract] Error 1
make: Target '/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/state/prolink6_driver.compile' not remade because of errors.

-----Original Message-----
From: Michael Olbrich <m.olbrich@pengutronix.de>
Sent: Friday, April 12, 2019 3:13 PM
To: ptxdist@pengutronix.de
Cc: Patrick Murray <Patrick.Murray@daktronics.com>
Subject: Re: [ptxdist] migrating a BSP from 2012.03.0 to 2019.03.1 ,


This email originated outside of Daktronics. Use caution when opening links or attachments. Report questionable emails to ITHelp.




On Fri, Apr 12, 2019 at 02:33:34PM +0100, Ian Abbott wrote:
> On 12/04/2019 13:33, Patrick Murray wrote:
> > I have installed ptxdist version 2019.03.1 onto a new Ubuntu host
> > and I have tried to migrate my i.MX6 BSP (last used with version
> > 2012.03.0 ) to 2019.03.1  , but
> >
> > I am getting this build-host error  with gcc and pkg-configure
> >
> > gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
> >
> > configure:3445: $? = 0
> >
> > configure:3434: gcc -V >&5
> >
> > gcc: error: unrecognized command line option '-V'
> >
> > gcc: fatal error: no input files
> >
> > compilation terminated.
>
> Comparing with my own config.log for build-host/pkg-conf-g-0.29.2, the
> problem seems to be here:
>
> > configure:3465: checking whether the C compiler works
> > configure:3487: gcc    conftest.c  >&5
> > as: unrecognized option '--64'
>
> Is there something wrong with your host's binutils installation?  What
> does `as --version` report?

Also, run ptxdist with '-v' and take a look at platform-xxxx/logfile.
Any call to 'gcc' will be logged here with all arguments. It will probably be the last 'wrapper: gcc ...' line in that file.

Michael

--
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.pengutronix.de%2F&amp;data=02%7C01%7Cpatrick.murray%40daktronics.com%7C34c582cdfc9749ff536308d6bf50e9c5%7Cbe88af81094542aaa3d2b122777351a2%7C0%7C0%7C636906751577852295&amp;sdata=7Z3xPhCgsZIfWSYmzYdzWV%2BhoNXHU%2FqS%2FHyne8r7bBE%3D&amp;reserved=0  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

This email and any attachments may be confidential and/or legally privileged. It has been sent for the sole use of the intended recipient(s). If the reader of this message is not an intended recipient, you are hereby notified that any unauthorized review, use, disclosure, dissemination, distribution, or copying of this communication or any of its contents is strictly prohibited. If you are not the named recipient, or have otherwise received this communication in error, please delete it from your inbox, notify the sender immediately, and do not disclose the contents to any other person or use them for any purpose, or store them in any medium. Thank you for your cooperation.

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2019-04-12 15:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 12:33 Patrick Murray
2019-04-12 13:33 ` Ian Abbott
2019-04-12 14:12   ` Michael Olbrich
2019-04-12 15:27     ` Patrick Murray [this message]
2019-04-18 14:19       ` Michael Olbrich

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=DM6PR02MB5977E7EBDD5AD5C9AADD5A9BFD280@DM6PR02MB5977.namprd02.prod.outlook.com \
    --to=patrick.murray@daktronics.com \
    --cc=m.olbrich@pengutronix.de \
    --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