Re: [Rd] Issue tracking in packages [was: Re: [R] change in read.spss, package foreign?]

2005-09-11 Thread Friedrich . Leisch
> On Sat, 10 Sep 2005 19:06:51 +0200,
> Martin Maechler (MM) wrote:

> "TL" == Thomas Lumley <[EMAIL PROTECTED]>
> on Sat, 10 Sep 2005 09:32:29 -0700 (PDT) writes:

  >>> Standard location or a mechachanism like the one you
  >>> describe are both similar amount of work (and not much at
  >>> all), the HTML pages are generated by perl and I have the
  >>> parsed DESCRIPTION file there, i.e., using a fixed name
  >>> or the value of the Changelog field is basically the
  >>> same.
  >>> 

  TL> In which case a Changlog entry in DESCRIPTION would be a
  TL> very nice addition, and would have the advantage of not
  TL> requiring changes to packages.

  > yes *and* does allow slightly more flexibility with almost
  > no cost, as Fritz confirmed.

Well, as Kurt pointed out in another (?) thread "CRAN is not the R
universe", and, e.g., Seth might have another opinion when it comes to
BioC administration. But I don't think you can (or should) do too much
sensible computations on packages without having parsed the
DESCRIPTION file, so the "almost no cost" statement should be pretty
safe.


  > And, BTW, Gabor,  NEWS and ChangeLog are not at all the same
  > thing and it would be silly to urge users to one of them.
  > At least 'ChangeLog' is a well defined format for emacs users
  > that can very quickly be updated semi-automagically
  > ("C-x 4 a" when you're in file  foo.R with function myfun(.)
  >  autogenerates a neat entry in a ChangeLog file);
  > but then really people should be allowed to use other formats
  > for good reasons.

I fully agree.

.f

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


[Rd] dyn.load error -- undefined symbol: ...

2005-09-11 Thread nwew
Dear R-developers,

I am working on an C interface to some c functions.
I compiled the c file using R CMD SHLIB without any compilation errors. All 
libs used are added to the LD_LIBRARY_PATH.

However dyn.load("interface.so")
produces  undefined symbol: N_VNew_Serial;

which is defined in one of the libs I link against.
Where, and how to start searching for the error?

Eryk

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


Re: [Rd] dyn.load error -- undefined symbol: ...

2005-09-11 Thread Duncan Temple Lang


You should tell us what operating system you are working on.

If it is a Unix variant, you can use the command ldd:

ldd interface.so

and see if and where it finds all the libraries against which you link.

(otool -L  on Mac OS X will give you similar information.)

Then make certain that the symbol N_VNew_Serial is defined in
one of those. You can find which symbols are available from
a library, etc. using the command nm -g


If you don't find your problem, you should post the
output from R CMD SHLIB ...  so that we can see
the link command and give you some suggestions as
to where to look.

   D.

nwew wrote:
> Dear R-developers,
> 
> I am working on an C interface to some c functions.
> I compiled the c file using R CMD SHLIB without any compilation errors. All 
> libs used are added to the LD_LIBRARY_PATH.
> 
> However dyn.load("interface.so")
> produces  undefined symbol: N_VNew_Serial;
> 
> which is defined in one of the libs I link against.
> Where, and how to start searching for the error?
> 
> Eryk
> 
> __
> R-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

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