On 18 June 2017 at 10:40, Iñaki Úcar wrote:
| 2017-06-17 18:00 GMT+02:00 Dirk Eddelbuettel :
| >
| > On 17 June 2017 at 17:30, Iñaki Úcar wrote:
| > | Hi all,
| > |
| > | After googling around for a while, I found that this is a common
| > | problem, but still it is not clear to me how I should ha
On 18 June 2017 at 09:22, Guillaume Chapron wrote:
| Thanks!
|
| In that file, I see:
|
| CC = clang
| CFLAGS = -Wall -mtune=core2 -g -O2 $(LTO)
|
| will having -O0 instead give me all the variables or is there a flag for
better debugging (I guess -g does it a little already)?
Right, -g is wh
2017-06-17 18:00 GMT+02:00 Dirk Eddelbuettel :
>
> On 17 June 2017 at 17:30, Iñaki Úcar wrote:
> | Hi all,
> |
> | After googling around for a while, I found that this is a common
> | problem, but still it is not clear to me how I should handle this.
> |
> | I have a package A, with C++ code via Rc
Thanks!
In that file, I see:
CC = clang
CFLAGS = -Wall -mtune=core2 -g -O2 $(LTO)
will having -O0 instead give me all the variables or is there a flag for better
debugging (I guess -g does it a little already)?
Thanks again
> On 17 Jun 2017, at 21:57, Dirk Eddelbuettel wrote:
>
>
> On 17
