From: Patrick Murray <Patrick.Murray@daktronics.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Autoconf directives not invoking g++ compiler
Date: Mon, 13 May 2019 09:45:09 +0000 [thread overview]
Message-ID: <DM6PR02MB5977ABE2F9801C61230BFBE6FD0F0@DM6PR02MB5977.namprd02.prod.outlook.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1960 bytes --]
Hi,
I tried renamed libpsc.c to libpsc.cpp ( and .ccx) , no difference in the outcome, running ./configure fails and so does the ptxdist libpsc compile.
Question , in a autotools library package are you only allowed either c file or c++ file ?
dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/local_src/libpsc$ ./configure
configure: error: cannot find sources (libpsc.c) in . or ..
ptxdist compile libpsc
----------------------
target: libpsc.compile
----------------------
make[1]: Entering directory '/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/build-target/libpsc-build'
make --no-print-directory all-am
make[2]: *** No rule to make target 'libpsc.c', needed by 'liblibpsc_la-libpsc.lo'. Stop.
make[1]: *** [Makefile:476: all] Error 2
make[1]: Leaving directory '/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/build-target/libpsc-build'
make: *** [/opt/lib/ptxdist-2019.03.1/rules/post/ptxd_make_world_compile.make:22: /opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/state/libpsc.compile] Error 2
dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4$<mailto:dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4$>
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.
[-- Attachment #1.2: Type: text/html, Size: 4543 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2019-05-13 9:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 9:45 Patrick Murray [this message]
2019-05-13 9:58 ` Juergen Borleis
2019-05-13 16:19 ` Patrick Murray
2019-05-15 8:29 ` Juergen Borleis
-- strict thread matches above, loose matches on Subject: below --
2019-05-13 10:25 Patrick Murray
2019-05-13 9:02 Patrick Murray
2019-05-13 9:17 ` Juergen Borleis
2019-05-13 9:38 ` Juergen Borleis
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=DM6PR02MB5977ABE2F9801C61230BFBE6FD0F0@DM6PR02MB5977.namprd02.prod.outlook.com \
--to=patrick.murray@daktronics.com \
--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