On Wed, Jan 18, 2017 at 01:27:24PM -0600, Dirk Eddelbuettel wrote: > ... > | It turns out that in FreeBSD (possibly also in other BSD-derived > | environments), PF_UNSPEC is defined (in /usr/include/sys/socket.h), but > | only if "__BSD_VISIBLE" is true: > > [good detective work omitted]
:-) > | And it appears that the local sources are ephemeral, so I can't > | readily patch those sources to see if I can get it to work (as the > | patched sources wouldn't be used) -- unless I miss the mark.... > | > | Any suggestions for how I might proceed? > > I don't follow. Can you not use 'diff' and 'patch'? I am so old that I have > > tar xvzf foo_1.2.3.tar.gz > mv foo foo.orig > tar xvzf foo_1.2.3.tar.gz > cd foo > /* now do your work */ > cd .. && diff -ru foo.orig foo > foo.patch > > fairly deeply engrained in muscle memory. And R itself is in pretty tip-top > shape and will listen to 'configure; make; make install'. You probably can > even skip make install as you are "just" fighting a failure to build. > .... Oh, I can use the commands; I had been treating install.packages() as rather more of a "black box" -- once I discovered that on exiting R, the claimed location for the downloaded packages had vanished, I got a bit "gun-shy." :-} (I haven't actually created any packages in R....) Thanks! Peace, david -- David H. Wolfskill r...@catwhisker.org How could one possibly "respect" a misogynist, racist, bullying con-man??!? See http://www.catwhisker.org/~david/publickey.gpg for my public key.
signature.asc
Description: PGP signature
______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel