Skip to content

Build error with last R-devel tarball

4 messages · Brian Ripley, Hervé Pagès

Original
Hervé Pagès
# 
Hi,


On Windows, with last R-devel tarball (r40647) from
  ftp://ftp.stat.math.ethz.ch/Software/R/R-devel_2007-02-04.tar.gz
I get the following build error:

E:\biocbld\bbs-2.0-bioc\R\src\gnuwin32> make
...
...
---------- Making package utils ------------
  adding build stamp to DESCRIPTION
  installing NAMESPACE file and metadata
  installing R files
Error in namespaceExport(ns, exports) : undefined exports :?, CRAN.packages,
Rprof, Rprofmem, RShowDo
c, RSiteSearch, URLdecode, URLencode, alarm, apropos, argsAnywhere,
assignInNamespace, as.roman, as.p
erson, as.personList, available.packages, browseEnv, browseURL, bug.report,
capture.output, checkCRAN
, chooseCRANmirror, citation, citEntry, citHeader, citFooter, close.socket,
combn, compareVersion, co
ntrib.url, count.fields, data, data.entry, dataentry, de, de.ncols, de.restore,
de.setup, debugger, d
emo, download.file, download.packages, dump.frames, edit, emacs, example,
file_test, file.edit, find,
 fix, fixInNamespace, flush.console, formatOL, formatUL, getAnywhere,
getFromNamespace, getS3method,
glob2rx, head, head.matrix, help, help.search, help.start, history,
index.search, install.packages, i
nstalled.packages, limitedLabels, loadhistory, localeToCharset, ls.str, lsf.str,
make.packages.html,
make.socket, memory.limit, memory.size, menu, methods, mirror2html, modifyList,
new.packag
In addition: Warning message:
S3 methods '[.getAnywhere', '[.roman', 'as.character.person',
'as.character.personList', 'as.characte
r.roman', 'as.person.default', 'as.personList.default', 'as.personList.person',
'edit.data.frame', 'e
dit.default', 'edit.matrix', 'edit.vignette', 'format.roman', 'head.data.frame',
'head.default', 'hea
d.function', 'head.matrix', 'head.ftable', 'head.table', 'print.citation',
'print.Bibtex', 'print.cit
ationList', 'print.getAnywhere', 'print.hsearch', 'print.help_files_with_topic',
'print.Latex', 'prin
t.ls_str', 'print.MethodsFunction', 'print.packageDescription',
'print.packageIQR', 'print.packageSta
tus', 'print.roman', 'print.sessionInfo', 'print.socket', 'print.vignette',
'prompt.data.frame', 'pro
mpt.default', 'stack.data.frame', 'stack.default', 'str.POSIXt',
'str.data.frame', 'str.default', 'su
mmary.packageStatus', 'tail.data.frame', 'tail.default', 'tail.function',
'tail.matrix', 'tail.ftable
', 'tail.table', 'toBibtex.citation', 'toBibtex.citationList',
'toBibtex.person', 'toBibtex [... trun
cated]
Execution halted
make[4]: *** [E:/biocbld/bbs-2.0-bioc/R/library/utils/R/utils] Error 1
make[3]: *** [all] Error 2
make[2]: *** [pkg-utils] Error 2
make[1]: *** [rpackage] Error 1
make: *** [all] Error 2

Cheers,
H.
Brian Ripley
# 
This was fixed in SVN within a few hours.  Tarballs are snapshots, please 
check SVN before reporting problems.

As I have said several times, please do not expect R-devel to build on all 
platforms at all times.
On Mon, 5 Feb 2007, hpages at fhcrc.org wrote:

            

      
      
      
    

        

      
      
    

        

  
    

      
      
    

  


  


      

    

    

      
      

        


  

        

      Hervé Pagès
    

    

      
      #
    

  


  

      
Quoting Prof Brian Ripley <ripley at stats.ox.ac.uk>:

            

      
      
      
    

        
Thanks! I will check SVN before reporting problems with a tarball.
Just hope that nobody will get too upset if I'm reporting a problem
that just got fixed during the time I did 'svn up' and 'Send Message'
though ;-)

            

      
      
      
    

        
Of course. But please, let us know if reporting problems when they occur
is still the right thing to do or not.

Thanks,
H.

            

      
      
      
    

        

      
      
    

            

      
      
      
    

  
  


  


      

    

    

      
      

        


  

        

      Brian Ripley
    

    

      
      #
    

  


  

      
On Tue, 6 Feb 2007, hpages at fhcrc.org wrote:

        

            

      
      
      
    

        
It's often a good idea to check 24-48 hours later and then report.
Autobuilders are running on about that frequency.