From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: C++ code block not linked [SOLVED]
Date: Tue, 28 Nov 2017 16:07:44 -0500 [thread overview]
Message-ID: <87r2si3ye7.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: 5A1D9C99.80606@free.fr
Thierry Banel <tbanelwebmin@free.fr> writes:
> On 28/11/2017 18:08, Roger Mason wrote:
>
> Hello,
>
> Roger Mason <rmason@MUN.CA> writes:
>
> It compiles fine:
>
> c++ -std=c++11 -I/usr/local/include -L/usr/local/lib -lginac
> C-src-1053hn1.cpp
>
> Solved by setting:
>
> (setq org-babel-C++-compiler "c++")
>
> I don't recall having had to do this before.
>
> Phew! Very glad to have this working again. I'm not aware of any other tool
> that is as good as org-mode for literate programming and reproducible
> research. A big thank you to those who created and maintain it.
>
> Cheers,
> Roger
>
> Good to know it is solved.
> You can customize this variable:
> C-h v org-babel-C++-compiler
>
> In case someone else bump into a similar problem, the actual command launched by Babel can be obtained
> through the debugger:
> M-x debug-on-entry RET org-babel-eval RET
> evaluate the Babel block
> The debugger shows a line like this one:
> * org-babel-eval("g++ -o /tmp/babel-3110Zeg/C-bin-3110Fwh -std=c++11 ...
> This works for many languages supported by Babel.
>
All very good info, but why did the OP not have a g++? Using a
non-linux operating system? Using a non-GNU tool chain? Inquiring
minds want to know...
--
Nick
next prev parent reply other threads:[~2017-11-28 21:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-25 14:59 C++ code block not linked Roger Mason
2017-11-25 15:38 ` Thierry Banel
2017-11-26 11:42 ` Roger Mason
2017-11-27 7:33 ` Thierry Banel
2017-11-27 11:04 ` Roger Mason
2017-11-28 17:08 ` C++ code block not linked [SOLVED] Roger Mason
2017-11-28 17:27 ` Thierry Banel
2017-11-28 21:07 ` Nick Dokos [this message]
2017-11-29 15:38 ` Roger Mason
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r2si3ye7.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).