similar to: problems with ESS 16.10-1 and R version 3.3.2

Displaying 14 results from an estimated 14 matches similar to: "problems with ESS 16.10-1 and R version 3.3.2"

2007 Feb 01
1
3 PCI slot with exclusive IRQ ? please advice!
Hi, I'm looking for an hardware platform for an * installation that should have at least 3 PCI slot with no irq sharing whatsoever. Hardware raid 1 with hot swap is a premium, but not mandatory ... What would you choose? compaq/hp ? Dell ? Ibm ? Tnx for any advice on this matter! -- I migliori saluti, Scrivi a: Alessio afoc@interconnessioni.it
2002 May 18
0
Importante!
Vuoi Davvero Guadagnare con Internet? Bene, salva su disco questa pagina per averla a portata di mano anche se il tuo PC non ? connesso a Internet, poi copia quanto segue in Word o in Blocco Note e stampalo, cos? lo potrai leggere con pi? attenzione. Questo Sistema ? diverso da tutti gli altri, quindi non essere precipitoso nel valutarlo senza averlo compreso a fondo, ma ti assicuro che
2006 Mar 22
2
beronet & bristuff
Hi. I'm trying to get a Beronet QuadBRI card work with bristuff drivers. Though qozap module loads right, all card spans are in deactivated status. I'm quite sure my configuration is correct and using a single BRI card instead of the quadBRI the status is active and I can place and receive calls. On Beronet installation manual I read that Beronet and Junghanns cards are identical in
2016 Nov 12
0
Ubuntu 16.10 Yakkety Yak uses GCC 6 but -std=c++98 is missing
On 11 November 2016 at 23:48, Kirill M?ller wrote: | After upgrading to Ubuntu 16.10, which brings GCC 6, I've noticed that | packages are compiled in C++14 mode by default. Here's what a g++ | command for compiling one of Rcpp's modules look like on my system: | | g++ -I/usr/share/R/include -DNDEBUG -I../inst/include/ -fpic -g -O2 | -fstack-protector-strong -Wformat
2016 Nov 12
0
Ubuntu 16.10 Yakkety Yak uses GCC 6 but -std=c++98 is missing
On 13.11.2016 00:00, Dirk Eddelbuettel wrote: > On 12 November 2016 at 22:54, Kirill M?ller wrote: > > [... lots of stuff deleted ...] > > | I noticed this because plogr logging crashed in dplyr (compiled with gcc > | 6) right after upgrading to yakkety; I still had a gcc-5 built version > | of Rcpp installed. As soon as I added -std, everything worked as before. > | No
2020 May 12
2
i sided recordings in asterisk 16.10
Hi guys i upgraded to asterisk 16.10 and in most recordings you here only leg A in the recording sometimes you might hear a word of leg B Did any body hit this problem? Thanks, israel -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20200512/90ee8dc2/attachment.html>
2016 Nov 13
0
Ubuntu 16.10 Yakkety Yak uses GCC 6 but -std=c++98 is missing
On Sat, Nov 12, 2016 at 7:41 PM, Dirk Eddelbuettel <edd at debian.org> wrote: > > On 13 November 2016 at 00:13, Kirill M?ller wrote: > | On 13.11.2016 00:00, Dirk Eddelbuettel wrote: > | > On 12 November 2016 at 22:54, Kirill M?ller wrote: > | > > | > [... lots of stuff deleted ...] > | > > | > | I noticed this because plogr logging crashed in dplyr
2016 Nov 12
2
Ubuntu 16.10 Yakkety Yak uses GCC 6 but -std=c++98 is missing
On 12 November 2016 at 22:54, Kirill M?ller wrote: [... lots of stuff deleted ...] | I noticed this because plogr logging crashed in dplyr (compiled with gcc | 6) right after upgrading to yakkety; I still had a gcc-5 built version | of Rcpp installed. As soon as I added -std, everything worked as before. | No minimal example, sorry. Don't we need "-std=c++98" in Makevars |
2016 Nov 12
0
Ubuntu 16.10 Yakkety Yak uses GCC 6 but -std=c++98 is missing
On 12.11.2016 18:38, Dirk Eddelbuettel wrote: > On 12 November 2016 at 07:59, Dirk Eddelbuettel wrote: > | > | On 12 November 2016 at 14:23, Kirill M?ller wrote: > | | Thanks. I have now CXX = g++ -std=c++98 in my /etc/R/Makeconf, it's > | | picked up properly. I can only assume that the last -std= option wins if > | | more than one are given on the same command line [1].
2016 Nov 12
3
Ubuntu 16.10 Yakkety Yak uses GCC 6 but -std=c++98 is missing
Thanks. I have now CXX = g++ -std=c++98 in my /etc/R/Makeconf, it's picked up properly. I can only assume that the last -std= option wins if more than one are given on the same command line [1]. -Kirill [1] http://stackoverflow.com/q/40563269/946850 On 12.11.2016 03:01, Dirk Eddelbuettel wrote: > On 11 November 2016 at 23:48, Kirill M?ller wrote: > | After upgrading to Ubuntu
2016 Nov 12
2
Ubuntu 16.10 Yakkety Yak uses GCC 6 but -std=c++98 is missing
On 12 November 2016 at 07:59, Dirk Eddelbuettel wrote: | | On 12 November 2016 at 14:23, Kirill M?ller wrote: | | Thanks. I have now CXX = g++ -std=c++98 in my /etc/R/Makeconf, it's | | picked up properly. I can only assume that the last -std= option wins if | | more than one are given on the same command line [1]. | | Good to know it works. | | I am still a little puzzled why it was
2016 Nov 11
3
Ubuntu 16.10 Yakkety Yak uses GCC 6 but -std=c++98 is missing
After upgrading to Ubuntu 16.10, which brings GCC 6, I've noticed that packages are compiled in C++14 mode by default. Here's what a g++ command for compiling one of Rcpp's modules look like on my system: g++ -I/usr/share/R/include -DNDEBUG -I../inst/include/ -fpic -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -g -c
2016 Nov 12
2
Ubuntu 16.10 Yakkety Yak uses GCC 6 but -std=c++98 is missing
On 13 November 2016 at 00:13, Kirill M?ller wrote: | On 13.11.2016 00:00, Dirk Eddelbuettel wrote: | > On 12 November 2016 at 22:54, Kirill M?ller wrote: | > | > [... lots of stuff deleted ...] | > | > | I noticed this because plogr logging crashed in dplyr (compiled with gcc | > | 6) right after upgrading to yakkety; I still had a gcc-5 built version | > | of Rcpp installed.
2007 Dec 15
17
Upgrade to Asterisk 1.4 - it's one year's old!
Friends in the Asterisk community, I'm kind of interested in the slow uptake of Asterisk 1.4. Between 1.2 and 1.4 there's been a lot of important development. New code cleanups, optimization, new functions. I realize that 1.4 at release time wasn't ready for release, but we've spent one year polishing it, working hard with bug fixes. The 1.4 that is in distribution now is