mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
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 10:25:39 +0000	[thread overview]
Message-ID: <DM6PR02MB597722ACB4BD34EB91A8C876FD0F0@DM6PR02MB5977.namprd02.prod.outlook.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2819 bytes --]

Hi,

Yes I did already change AC_CONFIG_SRCDIR in configure.ac , I have tried renaming the libpsc.c to libpsc.cxx and libpsc.cc ,
Still make no difference .

It seems the "default" is it expects a file called libpsc.c .

----------------------
target: libpsc.prepare
----------------------

configure: error: cannot find sources (libpsc.c) in ../libpsc or ..
make: *** [/opt/lib/ptxdist-2019.03.1/rules/post/ptxd_make_world_prepare.make:22: /opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/platform-phyFLEX-i.MX6/state/libpsc.prepare] Error 1

I still believe it hasn't found the C++ compiler .

dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/local_src/libpsc$ grep CONFIG_SRCDIR *.*
grep: autom4te.cache: Is a directory
configure.ac:#AC_CONFIG_SRCDIR([R3PSC.cpp])
configure.ac:#AC_CONFIG_SRCDIR([libpsc.cxx])
configure.ac:AC_CONFIG_SRCDIR([libpsc.cc])

dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/local_src/libpsc$ ls libpsc.*
libpsc.cc  libpsc.c_orig  libpsc.h


dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/local_src/libpsc$ ls *.cpp
accessors.cpp                   device_instance_master.cpp     device_instance_vcb2.cpp    device_type_mlc5.cpp       exception.cpp
debug.cpp                       device_instance_mlc5.cpp       device_instance_vfc2.cpp    device_type_mod.cpp        R3PSC.cpp
device_connections.cpp          device_instance_mod.cpp        device_sets.cpp             device_type_plc5.cpp       simpleXPath.cpp
device_instance_base.cpp        device_instance_plc5.cpp       device_type_base.cpp        device_type_plr.cpp        utils.cpp
device_instance_canmod.cpp      device_instance_plr.cpp        device_type_canmod.cpp      device_type_ppc5pixel.cpp  xml_processor.cpp
device_instance_collection.cpp  device_instance_ppc5pixel.cpp  device_type_collection.cpp  device_type_sc7mod.cpp
device_instance_lcd.cpp         device_instance_sc7mod.cpp     device_type_lcd.cpp         device_type_vcb2.cpp
device_instance_master5.cpp     device_instance_unknown.cpp    device_type_master.cpp      device_type_vfc2.cpp


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: 6808 bytes --]

[-- Attachment #2: Type: text/plain, Size: 91 bytes --]

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

             reply	other threads:[~2019-05-13 10:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13 10:25 Patrick Murray [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-05-13  9:45 Patrick Murray
2019-05-13  9:58 ` Juergen Borleis
2019-05-13 16:19   ` Patrick Murray
2019-05-15  8:29     ` Juergen Borleis
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=DM6PR02MB597722ACB4BD34EB91A8C876FD0F0@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