Re: [Rd] Encoding errors in Rd files

[steven mosher]

Thank Dr. Ripley.

 When I read the instructions
" If the DESCRIPTION file is not entirely in ASCII it should contain an ‘
Encoding’ field specifying an encoding. This is used as the encoding of the
DESCRIPTION file itself and of the R and NAMESPACE files, and as the
default encoding of .Rd files.  "

I assumed that I should specify an encoding of UTF-8 in the description
file to handle the specific Rd files that were having problems.

After I removed  the encoding field (UTF-8)  I had added to the DESCRIPTION
file, the following error no longer occurred

"  Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `utf8'. "

however the rd files still had errors.

   looking at the latex versions of the Rd files I was able to spot which
characters in the Rd files
were offending. In my normal editor they were simply not showing up, so I
had no idea what characters were
causing the problem.

The only thing I am left with is the entries in the data frame. The package
came with some predefined  .rda files
in its data subdirectory.  Using encoding() on  the column of the data
frame that contains the following items

 checking data for non-ASCII characters ... WARNING
   Warning: found non-ASCII string(s)
   'Tourbihre de la Rivihre-aux-Feu' in object 'modpoll'
   'Lac ` la Fourche' in object 'modpoll'
   'Lac ` la Loutre' in object 'modpoll'
   'Lac Kinogami' in object 'modpoll'

I get "unknown"  for all the items.  So, If I understand you I should take
this dataframe, change the encoding
to UTF-8

Sorry for being so dense

On Tue, Jul 24, 2012 at 1:46 PM, Prof Brian Ripley wrote:

> On 24/07/2012 21:08, steven mosher wrote:
>
>> Well, I'm working on project trying to bring back an old package last
>> published on R 1.9 back to life.
>> I'm almost there but I am getting killed by an encoding error in the Rd
>> files
>>
>> After reading the manual, I decided to try UTF-8.  Mostly because I could
>> spell it. ha.
>>
>> That got me a bit closer but I still have these warnings
>>
>> * checking data for non-ASCII characters ... WARNING
>>Warning: found non-ASCII string(s)
>>'Tourbihre de la Rivihre-aux-Feu' in object 'modpoll'
>>'Lac ` la Fourche' in object 'modpoll'
>>'Lac ` la Loutre' in object 'modpoll'
>>'Lac Kinogami' in object 'modpoll'
>>
>
> How to handle those is in 'Writing R Extensions': basically convert to
> UTF-8 and mark them as UTF-8.
>
>
>  * checking data for ASCII and uncompressed saves ... OK
>> * checking examples ... OK
>> * checking PDF version of manual ... WARNING
>> LaTeX errors when creating PDF version.
>> This typically indicates Rd problems.
>> LaTeX errors found:
>>   ! Package inputenc Error: Keyboard character used is undefined
>> (inputenc)in inputencoding `utf8'.
>>
>> I'll keep searching the help list archives for a clue, but If somebody
>> could point me at educational material it's really time
>> that I learn this aspect.
>>
>
> Without the actual file we can do little.  The message means that
> something in the manual inputs (and it could be the DESCRIPTION file or an
> Rd file) contains a character not known to LaTeX.  Most likely it is simply
> not a UTF-8 character, but it could also be outside LaTeX's gamut.
>
> Normally the LaTeX log (which is in the check output) is more revealing:
> you can also try this part alone with R CMD Rd2pdf (and R CMD Rd2pdf
> --no-description often points the finger at the DESCRIPTION file).
>
>
>
>> I've read
>> http://developer.r-project.**org/Encodings_and_R.html
>>
>> How do I figure out which encoding to use with the error seen above
>>
>
> Assuming this is not something esoteric, UTF-8 is the most comprehensive
> choice, but LaTeX's UTF-8 coverage (and that of the fonts used) is heavily
> biased to Western European scripts.  So for example for Lithuanian you may
> want to choose something else (Latin-7?).
>
>
>
>
> --
> Brian D. Ripley,  rip...@stats.ox.ac.uk
> Professor of Applied Statistics,  
> http://www.stats.ox.ac.uk/~**ripley/
> University of Oxford, Tel:  +44 1865 272861 (self)
> 1 South Parks Road, +44 1865 272866 (PA)
> Oxford OX1 3TG, UKFax:  +44 1865 272595
>

[[alternative HTML version deleted]]

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] Encoding errors in Rd files

[Duncan Murdoch]

On 12-07-25 3:24 AM, steven mosher wrote:

Thank Dr. Ripley.

  When I read the instructions
" If the DESCRIPTION file is not entirely in ASCII it should contain an ‘
Encoding’ field specifying an encoding. This is used as the encoding of the
DESCRIPTION file itself and of the R and NAMESPACE files, and as the
default encoding of .Rd files.  "

I assumed that I should specify an encoding of UTF-8 in the description
file to handle the specific Rd files that were having problems.

After I removed  the encoding field (UTF-8)  I had added to the DESCRIPTION
file, the following error no longer occurred

"  Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `utf8'. "

however the rd files still had errors.

looking at the latex versions of the Rd files I was able to spot which
characters in the Rd files
were offending. In my normal editor they were simply not showing up, so I
had no idea what characters were
causing the problem.

The only thing I am left with is the entries in the data frame. The package
came with some predefined  .rda files
in its data subdirectory.  Using encoding() on  the column of the data
frame that contains the following items

  checking data for non-ASCII characters ... WARNING
Warning: found non-ASCII string(s)
'Tourbihre de la Rivihre-aux-Feu' in object 'modpoll'
'Lac ` la Fourche' in object 'modpoll'
'Lac ` la Loutre' in object 'modpoll'
'Lac Kinogami' in object 'modpoll'

I get "unknown"  for all the items.  So, If I understand you I should take
this dataframe, change the encoding
to UTF-8.


The issue is almost certainly with accented characters in the text.  For 
example, the 5th letter in Rivière is an e with a grave accent.  It is 
displayed as "h" in your error message, because R was not told how to 
interpret the way it is stored in the source file, or was told something 
that turned out to be incorrect.


You need to change the source file so that it is stored in the UTF-8 
encoding.  That means you should read the file into an editor that 
displays it correctly (and that's sometimes hard when you don't know the 
original encoding; you may need to do some manual editing), then save it 
again, specifying that it should be saved using the UTF-8 encoding.  How 
you do that depends on your editor.


Then when you tell R that it is encoded in UTF-8, R will read it 
properly and won't complain.


The tools::showNonASCIIfile() function can help to find characters that 
may need fixing.  R can recognize when things are not ASCII (those bytes 
have the high bit set), but it will be up to you to figure out what 
encoding was actually used.  For French, latin1 is a good guess but it 
is not necessarily right.


Duncan Murdoch



Sorry for being so dense

On Tue, Jul 24, 2012 at 1:46 PM, Prof Brian Ripley wrote:


On 24/07/2012 21:08, steven mosher wrote:


Well, I'm working on project trying to bring back an old package last
published on R 1.9 back to life.
I'm almost there but I am getting killed by an encoding error in the Rd
files

After reading the manual, I decided to try UTF-8.  Mostly because I could
spell it. ha.

That got me a bit closer but I still have these warnings

* checking data for non-ASCII characters ... WARNING
Warning: found non-ASCII string(s)
'Tourbihre de la Rivihre-aux-Feu' in object 'modpoll'
'Lac ` la Fourche' in object 'modpoll'
'Lac ` la Loutre' in object 'modpoll'
'Lac Kinogami' in object 'modpoll'



How to handle those is in 'Writing R Extensions': basically convert to
UTF-8 and mark them as UTF-8.


  * checking data for ASCII and uncompressed saves ... OK

* checking examples ... OK
* checking PDF version of manual ... WARNING
LaTeX errors when creating PDF version.
This typically indicates Rd problems.
LaTeX errors found:
   ! Package inputenc Error: Keyboard character used is undefined
(inputenc)in inputencoding `utf8'.

I'll keep searching the help list archives for a clue, but If somebody
could point me at educational material it's really time
that I learn this aspect.



Without the actual file we can do little.  The message means that
something in the manual inputs (and it could be the DESCRIPTION file or an
Rd file) contains a character not known to LaTeX.  Most likely it is simply
not a UTF-8 character, but it could also be outside LaTeX's gamut.

Normally the LaTeX log (which is in the check output) is more revealing:
you can also try this part alone with R CMD Rd2pdf (and R CMD Rd2pdf
--no-description often points the finger at the DESCRIPTION file).




I've read
http://developer.r-project.**org/Encodings_and_R.html

How do I figure out which encoding to use with the error seen above



Assuming this is not something esoteric, UTF-8 is the most comprehensive
choice, but LaTeX's UTF-8 coverage (and that of the fonts used) is heavily
biased to Western European scripts.  So for

Re: [Rd] Encoding errors in Rd files

[steven mosher]

Thanks Duncan I  was able to find the offending characters in the Rd files.
I'll try latin1 for the data.frame (UTF-8 was obviously not the right
answer for that.)

One thing I was very happy for was that the package  just works, not too
shabby since it was orginally built
under 1.9.

Thanks for your help!

Steve


On Wed, Jul 25, 2012 at 1:04 AM, Duncan Murdoch wrote:

> On 12-07-25 3:24 AM, steven mosher wrote:
>
>> Thank Dr. Ripley.
>>
>>   When I read the instructions
>> " If the DESCRIPTION file is not entirely in ASCII it should contain an ‘
>> Encoding’ field specifying an encoding. This is used as the encoding of
>> the
>> DESCRIPTION file itself and of the R and NAMESPACE files, and as the
>> default encoding of .Rd files.  "
>>
>> I assumed that I should specify an encoding of UTF-8 in the description
>> file to handle the specific Rd files that were having problems.
>>
>> After I removed  the encoding field (UTF-8)  I had added to the
>> DESCRIPTION
>> file, the following error no longer occurred
>>
>> "  Package inputenc Error: Keyboard character used is undefined
>> (inputenc)in inputencoding `utf8'. "
>>
>> however the rd files still had errors.
>>
>> looking at the latex versions of the Rd files I was able to spot which
>> characters in the Rd files
>> were offending. In my normal editor they were simply not showing up, so I
>> had no idea what characters were
>> causing the problem.
>>
>> The only thing I am left with is the entries in the data frame. The
>> package
>> came with some predefined  .rda files
>> in its data subdirectory.  Using encoding() on  the column of the data
>> frame that contains the following items
>>
>>   checking data for non-ASCII characters ... WARNING
>> Warning: found non-ASCII string(s)
>> 'Tourbihre de la Rivihre-aux-Feu' in object 'modpoll'
>> 'Lac ` la Fourche' in object 'modpoll'
>> 'Lac ` la Loutre' in object 'modpoll'
>> 'Lac Kinogami' in object 'modpoll'
>>
>> I get "unknown"  for all the items.  So, If I understand you I should take
>> this dataframe, change the encoding
>> to UTF-8.
>>
>
> The issue is almost certainly with accented characters in the text.  For
> example, the 5th letter in Rivière is an e with a grave accent.  It is
> displayed as "h" in your error message, because R was not told how to
> interpret the way it is stored in the source file, or was told something
> that turned out to be incorrect.
>
> You need to change the source file so that it is stored in the UTF-8
> encoding.  That means you should read the file into an editor that displays
> it correctly (and that's sometimes hard when you don't know the original
> encoding; you may need to do some manual editing), then save it again,
> specifying that it should be saved using the UTF-8 encoding.  How you do
> that depends on your editor.
>
> Then when you tell R that it is encoded in UTF-8, R will read it properly
> and won't complain.
>
> The tools::showNonASCIIfile() function can help to find characters that
> may need fixing.  R can recognize when things are not ASCII (those bytes
> have the high bit set), but it will be up to you to figure out what
> encoding was actually used.  For French, latin1 is a good guess but it is
> not necessarily right.
>
> Duncan Murdoch
>
>
>> Sorry for being so dense
>>
>> On Tue, Jul 24, 2012 at 1:46 PM, Prof Brian Ripley > >wrote:
>>
>>  On 24/07/2012 21:08, steven mosher wrote:
>>>
>>>  Well, I'm working on project trying to bring back an old package last
 published on R 1.9 back to life.
 I'm almost there but I am getting killed by an encoding error in the Rd
 files

 After reading the manual, I decided to try UTF-8.  Mostly because I
 could
 spell it. ha.

 That got me a bit closer but I still have these warnings

 * checking data for non-ASCII characters ... WARNING
 Warning: found non-ASCII string(s)
 'Tourbihre de la Rivihre-aux-Feu' in object 'modpoll'
 'Lac ` la Fourche' in object 'modpoll'
 'Lac ` la Loutre' in object 'modpoll'
 'Lac Kinogami' in object 'modpoll'


>>> How to handle those is in 'Writing R Extensions': basically convert to
>>> UTF-8 and mark them as UTF-8.
>>>
>>>
>>>   * checking data for ASCII and uncompressed saves ... OK
>>>
 * checking examples ... OK
 * checking PDF version of manual ... WARNING
 LaTeX errors when creating PDF version.
 This typically indicates Rd problems.
 LaTeX errors found:
! Package inputenc Error: Keyboard character used is undefined
 (inputenc)in inputencoding `utf8'.

 I'll keep searching the help list archives for a clue, but If somebody
 could point me at educational material it's really time
 that I learn this aspect.


>>> Without the actual file we can do little.  The message means that
>>> something in the manual inputs (and it could be the DESCRIPTION file or
>>> an
>>> Rd file) cont

[Rd] Convenience function to get unevaluated ... function arguments

[Bert Gunter]

Folks:

Herein is a suggestion for a little R convenience function mainly to
obtain unevaluated ... function arguments. It arose from a query on
R-help on how to get these arguments. The standard (I think) idiom to
do this is via

match.call(expand.dots=FALSE)$...

However, Bill Dunlap pointed out that this repeats the argument
matching of the function call and suggested a couple of alternatives
that do not, one of which I've adapted as the following function,fun
(I'll comment on naming in a second):

fun <- as.list(substitute((...), env = parent.frame()))[-1]

Typical usage would be:

f <- function(x, ...,y)fun()

e.g.

> f(x = 5,z=sin(a),y=3,stop("oh"),w=warning("Yikes"))
$z
sin(a)

[[2]]
stop("oh")

$w
warning("Yikes")

It turns out that (surprisingly to me) the substitute idiom is faster
than the match.call idiom, although the difference appears
unimportant, since both are so fast. And it is a little slower when
wrapped into a function, anyway -- I wasn't able to figure out a
convenient way to wrap the match.call version into a function.

The question is where -- if anywhere -- should this little one-liner
go? Seems to me that there are 3 possibilities:
1. Nowhere. Unnecessary and trivial.  An entirely reasonable response,
imho; I leave it to guRus to make this judgment.

2. In with match.call(); in which case a name like match.dots would
seem appropriate.

3. In with substitute(); in which case something like substituteDots
to make the relationship clear might be appropriate.

If R core or others do want to use this, I would be happy to write the
line or two of additional documentation required (if no one else wants
to).

And to repeat... I know this is trivial, so no explanation or response
is needed if it is decided to ignore it.

Best,
Bert




-- 

Bert Gunter
Genentech Nonclinical Biostatistics

Internal Contact Info:
Phone: 467-7374
Website:
http://pharmadevelopment.roche.com/index/pdb/pdb-functional-groups/pdb-biostatistics/pdb-ncb-home.htm

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[Rd] Rconfig.h & unsupported architectures

[Hadley Wickham]

Hi all,

Recently, when compiling R packages containing C code, I've started
getting the following error:

* installing to library ‘/Users/hadley/R’
* installing *source* package ‘appdirs’ ...
** Creating default NAMESPACE file
** libs
*** arch - i386
gcc -arch i386 -std=gnu99
-I/Library/Frameworks/R.framework/Resources/include
-I/Library/Frameworks/R.framework/Resources/include/i386 -DNDEBUG
-I/usr/local/include-fPIC  -g -O2  -c win-path.c -o win-path.o
In file included from /Library/Frameworks/R.framework/Resources/include/R.h:34,
 from win-path.c:1:
/Library/Frameworks/R.framework/Resources/include/Rconfig.h:13:2:
error: #error "Unsupported architecture."
In file included from
/Library/Frameworks/R.framework/Resources/include/R_ext/RS.h:27,
 from /Library/Frameworks/R.framework/Resources/include/R.h:44,
 from win-path.c:1:
/Library/Frameworks/R.framework/Resources/include/Rconfig.h:13:2:
error: #error "Unsupported architecture."

I'm on

> sessionInfo()
R version 2.15.1 (2012-06-22)
Platform: x86_64-apple-darwin9.8.0/x86_64 (64-bit)

And in case it helps:

gcc --version
i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc.
build 5658) (LLVM build 2336.9.00)

Any ideas about what I might have done to break this?

Thanks!

Hadley


-- 
Assistant Professor / Dobelman Family Junior Chair
Department of Statistics / Rice University
http://had.co.nz/

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] Convenience function to get unevaluated ... function arguments

[David Winsemius]

On Jul 24, 2012, at 4:39 PM, Bert Gunter wrote:


Folks:

Herein is a suggestion for a little R convenience function mainly to
obtain unevaluated ... function arguments. It arose from a query on
R-help on how to get these arguments. The standard (I think) idiom to
do this is via

match.call(expand.dots=FALSE)$...

However, Bill Dunlap pointed out that this repeats the argument
matching of the function call and suggested a couple of alternatives
that do not, one of which I've adapted as the following function,fun
(I'll comment on naming in a second):

fun <- as.list(substitute((...), env = parent.frame()))[-1]


I think instead:

fun <- function() as.list(substitute((...), env = parent.frame()))[-1]

--
David.


Typical usage would be:

f <- function(x, ...,y)fun()

e.g.


f(x = 5,z=sin(a),y=3,stop("oh"),w=warning("Yikes"))

$z
sin(a)

[[2]]
stop("oh")

$w
warning("Yikes")

It turns out that (surprisingly to me) the substitute idiom is faster
than the match.call idiom, although the difference appears
unimportant, since both are so fast. And it is a little slower when
wrapped into a function, anyway -- I wasn't able to figure out a
convenient way to wrap the match.call version into a function.

The question is where -- if anywhere -- should this little one-liner
go? Seems to me that there are 3 possibilities:
1. Nowhere. Unnecessary and trivial.  An entirely reasonable response,
imho; I leave it to guRus to make this judgment.

2. In with match.call(); in which case a name like match.dots would
seem appropriate.

3. In with substitute(); in which case something like substituteDots
to make the relationship clear might be appropriate.

If R core or others do want to use this, I would be happy to write the
line or two of additional documentation required (if no one else wants
to).

And to repeat... I know this is trivial, so no explanation or response
is needed if it is decided to ignore it.

Best,
Bert




--

Bert Gunter
Genentech Nonclinical Biostatistics

Internal Contact Info:
Phone: 467-7374
Website:
http://pharmadevelopment.roche.com/index/pdb/pdb-functional-groups/pdb-biostatistics/pdb-ncb-home.htm

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel


David Winsemius, MD
Heritage Laboratories
West Hartford, CT

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

[Rd] pie() bug in r59963

[Hiroyuki Kawakatsu]

hi,

there appears to be a bug in r-devel (r59963)
src/library/graphics/R/pie.R, line 62
P <- t2xy(seq.int(x[i], x[i + 1], n))
meant to be
P <- t2xy(seq.int(x[i], x[i + 1], length.out=n))
?
discovered when running demo(graphics). simpler example
is

pie(rep(1, 3), col=rainbow(3), radius=0.9)

h.
-- 
+---
| Hiroyuki Kawakatsu
| Business School, Dublin City University
| Dublin 9, Ireland. Tel +353 (0)1 700 7496

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] Rconfig.h & unsupported architectures

[Dirk Eddelbuettel]

On 25 July 2012 at 15:56, Hadley Wickham wrote:
| Hi all,
| 
| Recently, when compiling R packages containing C code, I've started
| getting the following error:
| 
| * installing to library ‘/Users/hadley/R’
| * installing *source* package ‘appdirs’ ...
| ** Creating default NAMESPACE file
| ** libs
| *** arch - i386
| gcc -arch i386 -std=gnu99
| -I/Library/Frameworks/R.framework/Resources/include
| -I/Library/Frameworks/R.framework/Resources/include/i386 -DNDEBUG
| -I/usr/local/include-fPIC  -g -O2  -c win-path.c -o win-path.o
| In file included from 
/Library/Frameworks/R.framework/Resources/include/R.h:34,
|  from win-path.c:1:
| /Library/Frameworks/R.framework/Resources/include/Rconfig.h:13:2:
| error: #error "Unsupported architecture."
| In file included from
| /Library/Frameworks/R.framework/Resources/include/R_ext/RS.h:27,
|  from 
/Library/Frameworks/R.framework/Resources/include/R.h:44,
|  from win-path.c:1:
| /Library/Frameworks/R.framework/Resources/include/Rconfig.h:13:2:
| error: #error "Unsupported architecture."
| 
| I'm on
| 
| > sessionInfo()
| R version 2.15.1 (2012-06-22)
| Platform: x86_64-apple-darwin9.8.0/x86_64 (64-bit)
| 
| And in case it helps:
| 
| gcc --version
| i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc.
| build 5658) (LLVM build 2336.9.00)
| 
| Any ideas about what I might have done to break this?

A quick grep for the string shows it pop up in pcre:

edd@max:~/src/debian/R/R-2.15.1/src$ grep "Unsupported arch" */*/*
extra/pcre/pcre_jit_compile.c:#error Unsupported architecture
edd@max:~/src/debian/R/R-2.15.1/src$ 

and it is the same in R-devel. Can you substitute a pre-built pcre library?

Dirk

 
| Thanks!
| 
| Hadley
| 
| 
| -- 
| Assistant Professor / Dobelman Family Junior Chair
| Department of Statistics / Rice University
| http://had.co.nz/
| 
| __
| R-devel@r-project.org mailing list
| https://stat.ethz.ch/mailman/listinfo/r-devel

-- 
Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com  

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] Rconfig.h & unsupported architectures

[Dirk Eddelbuettel]

On 25 July 2012 at 18:46, Dirk Eddelbuettel wrote:
| 
| On 25 July 2012 at 15:56, Hadley Wickham wrote:
| | Hi all,
| | 
| | Recently, when compiling R packages containing C code, I've started
| | getting the following error:
| | 
| | * installing to library ‘/Users/hadley/R’
| | * installing *source* package ‘appdirs’ ...
| | ** Creating default NAMESPACE file
| | ** libs
| | *** arch - i386
| | gcc -arch i386 -std=gnu99
| | -I/Library/Frameworks/R.framework/Resources/include
| | -I/Library/Frameworks/R.framework/Resources/include/i386 -DNDEBUG
| | -I/usr/local/include-fPIC  -g -O2  -c win-path.c -o win-path.o
| | In file included from 
/Library/Frameworks/R.framework/Resources/include/R.h:34,
| |  from win-path.c:1:
| | /Library/Frameworks/R.framework/Resources/include/Rconfig.h:13:2:
| | error: #error "Unsupported architecture."
| | In file included from
| | /Library/Frameworks/R.framework/Resources/include/R_ext/RS.h:27,
| |  from 
/Library/Frameworks/R.framework/Resources/include/R.h:44,
| |  from win-path.c:1:
| | /Library/Frameworks/R.framework/Resources/include/Rconfig.h:13:2:
| | error: #error "Unsupported architecture."
| | 
| | I'm on
| | 
| | > sessionInfo()
| | R version 2.15.1 (2012-06-22)
| | Platform: x86_64-apple-darwin9.8.0/x86_64 (64-bit)
| | 
| | And in case it helps:
| | 
| | gcc --version
| | i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc.
| | build 5658) (LLVM build 2336.9.00)
| | 
| | Any ideas about what I might have done to break this?
| 
| A quick grep for the string shows it pop up in pcre:
| 
| edd@max:~/src/debian/R/R-2.15.1/src$ grep "Unsupported arch" */*/*
| extra/pcre/pcre_jit_compile.c:#error Unsupported architecture
| edd@max:~/src/debian/R/R-2.15.1/src$ 
| 
| and it is the same in R-devel. Can you substitute a pre-built pcre library?

Actually, probably not the issue. You are getting it from one of R's headers
so it may have gotten there while you configured R on your machine. 

Dirk
 
| Dirk
| 
|  
| | Thanks!
| | 
| | Hadley
| | 
| | 
| | -- 
| | Assistant Professor / Dobelman Family Junior Chair
| | Department of Statistics / Rice University
| | http://had.co.nz/
| | 
| | __
| | R-devel@r-project.org mailing list
| | https://stat.ethz.ch/mailman/listinfo/r-devel
| 
| -- 
| Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com  
| 
| __
| R-devel@r-project.org mailing list
| https://stat.ethz.ch/mailman/listinfo/r-devel

-- 
Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com  

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Re: [Rd] pie() bug in r59963

[Prof Brian Ripley]

On 26/07/2012 00:37, Hiroyuki Kawakatsu wrote:

hi,

there appears to be a bug in r-devel (r59963)
src/library/graphics/R/pie.R, line 62
 P <- t2xy(seq.int(x[i], x[i + 1], n))
meant to be
 P <- t2xy(seq.int(x[i], x[i + 1], length.out=n))
?
discovered when running demo(graphics). simpler example
is

pie(rep(1, 3), col=rainbow(3), radius=0.9)

h.

Yes, that was an unintended change, but this is work in progress (on 
rep_ and it has gone again.


Thanks for commenting.

--
Brian D. Ripley,  rip...@stats.ox.ac.uk
Professor of Applied Statistics,  http://www.stats.ox.ac.uk/~ripley/
University of Oxford, Tel:  +44 1865 272861 (self)
1 South Parks Road, +44 1865 272866 (PA)
Oxford OX1 3TG, UKFax:  +44 1865 272595

__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel