From: Juergen Borleis <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Patrick Murray <Patrick.Murray@daktronics.com>
Subject: Re: [ptxdist] Autoconf directives not invoking g++ compiler
Date: Mon, 13 May 2019 11:58:12 +0200 [thread overview]
Message-ID: <201905131158.13037.jbe@pengutronix.de> (raw)
In-Reply-To: <DM6PR02MB5977ABE2F9801C61230BFBE6FD0F0@DM6PR02MB5977.namprd02.prod.outlook.com>
On Monday 13 May 2019 11:45:09 Patrick Murray wrote:
> 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 ?
You can have as much source file languages like you want.
> dak@CNU35294ZR:/opt/PHYTEC_BSPs/BSP-Phytec-phyFLEX-i.MX6-PD13.2.4/local_s
>rc/libpsc$ ./configure configure: error: cannot find sources (libpsc.c) in
Did you adapt the line AC_CONFIG_SRCDIR(...) line? This entry must point to
an existing file (no matter what file).
Regards,
Jürgen
--
Pengutronix e.K. | Juergen Borleis |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2019-05-13 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 9:45 Patrick Murray
2019-05-13 9:58 ` Juergen Borleis [this message]
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=201905131158.13037.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=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