Re: [Rd] Matrix does not build with R trunk since Oct.
Hin-Tak Leung htl10 at users.sourceforge.net writes: --- On Fri, 15/2/13, Simon Urbanek simon.urbanek at r-project.org wrote: On Feb 15, 2013, at 1:55 PM, Hin-Tak Leung wrote: Look. I don't see this as my problem - as far as I am concerned, I have donated my time - and over and over - to testing pre-released code. I am not using pre-released code for production work. If the released code in 3.0 does not work correctly in 6 weeks' time, I just don't upgrade. No loss for me there. It works - confirmed by several people. You have a problem, but you didn't tell us the specifics of the problem so there's nothing we can do. I do not have a problem. I do not need to spend time regularly testing pre-release code, and I think I should stop. The probably unknown now, for today's comfortable people, simple procedure has always been: svn up tools/rsync-recommended # R only ./configure ... make distclean ./configure ... make make check # R or relevant software only make install which always works even when building in the source tree. This whole thread is unnecessary if you remember to run make distclean, as all files that might appear to be fresh (but are not because of indirect dependencies, such as changes in the methods package), are rebuilt. When in doubt, use make distclean. It's as easy as that, nothing to get excited about. Section 7.2.6 of http://www.gnu.org/prep/standards/html_node/index.html. Roger I don't know why it is degenerating into another distraction about some people's egos. I don't either - it's not productive. Cheers, Simon __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Matrix does not build with R trunk since Oct.
On Feb 16, 2013, at 8:03 AM, Roger Bivand wrote: Hin-Tak Leung htl10 at users.sourceforge.net writes: --- On Fri, 15/2/13, Simon Urbanek simon.urbanek at r-project.org wrote: On Feb 15, 2013, at 1:55 PM, Hin-Tak Leung wrote: Look. I don't see this as my problem - as far as I am concerned, I have donated my time - and over and over - to testing pre-released code. I am not using pre-released code for production work. If the released code in 3.0 does not work correctly in 6 weeks' time, I just don't upgrade. No loss for me there. It works - confirmed by several people. You have a problem, but you didn't tell us the specifics of the problem so there's nothing we can do. I do not have a problem. I do not need to spend time regularly testing pre-release code, and I think I should stop. The probably unknown now, for today's comfortable people, simple procedure has always been: svn up tools/rsync-recommended # R only ./configure ... make distclean ./configure ... make make check # R or relevant software only make install which always works even when building in the source tree. Although it goes a long way, it doesn't always work -- it assumes that the directory structure did not change in the project between the revisions - distclean may not clean things that have changed since you updated the SVN (note that to address that you should run distclean *before* the update). Also note that R-devel is unstable for a reason -- as you are tracking it you may encounter bugs in the build which will make your in-source build (including distclean) break -- even if that bug is then fixed in next update the damage has been done already so you cannot recover. This has happened before, so in such cases you have to blow away everything and start from scratch (from svn co ..). That's why we are suggesting building outside sources, because it's easier to blow away just the build (there are still cases where even that won't work - e.g. when sources files are accidentally modified by the build). Before claiming that something doesn't work, you have to do a clean build.! In a majority of cases you will get away with in-sources build, but if you don't, you have to know what to do. This whole thread is unnecessary Period. It is indeed. The thread was about alleged issue with Matrix in R-devel which could not be confirmed (I even checked on Fedora 18 now and it builds just fine). We were not able to reproduce it and the reporter was unwilling to follow any suggestions hence we have no way to follow it up as it's not reproducible so I see the case as closed. Cheers, Simon if you remember to run make distclean, as all files that might appear to be fresh (but are not because of indirect dependencies, such as changes in the methods package), are rebuilt. When in doubt, use make distclean. It's as easy as that, nothing to get excited about. Section 7.2.6 of http://www.gnu.org/prep/standards/html_node/index.html. Roger I don't know why it is degenerating into another distraction about some people's egos. I don't either - it's not productive. Cheers, Simon __ 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
Re: [Rd] Matrix does not build with R trunk since Oct.
Although it goes a long way, it doesn't always work -- it assumes that the directory structure did not change in the project between the revisions - distclean may not clean things that have changed since you updated the SVN (note that to address that you should run distclean *before* the update). Also note that R-devel is unstable for a reason -- as you are tracking it you may encounter bugs in the build which will make your in-source build (including distclean) break -- even if that bug is then fixed in next update the damage has been done already so you cannot recover. This has happened before, so in such cases you have to blow away everything and start from scratch (from svn co ..). One of the cool things about git is git clean - that allows you to remove all non-git files from the repo without having to do checkout from scratch. Hadley -- Chief Scientist, RStudio http://had.co.nz/ __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Matrix does not build with R trunk since Oct.
On Feb 15, 2013, at 6:13 PM, Hin-Tak Leung wrote: FWIW, extracting snapshot source elsewhere outside svn, run tools/rsync-recommended then just plain ./configure make doesn't work either. Nothing to do with building inside checkout nor extra configure options. Can you define extracting snapshot source elsewhere outside svn? That is likely the crucial point. If you mean that you used svn checkout on one machine, copied the content to another machine which does *not* have svn and then built there -- then this is unsupported and it has never been supported (depending on the R version it would either break or report invalid svn rev in R.version). You can *only* build from the svn sources if you have svn installed on the machine (equally, you cannot use svn export - see R-admin 1.2.1). You can only proceed on a machine without svn if you first create a distribution tar ball (e.g., via make dist) on the machine with svn and then use that tar ball on another machine (this is how R snapshots work). This is fedora 18, x86_64. I checked on Fedora 18 and it works just fine using svn co https://svn.r-project.org/R/trunk R-devel cd R-devel/ tools/rsync-recommended ./configure make Cheers, Simon --- On Fri, 15/2/13, Hin-Tak Leung ht...@users.sourceforge.net wrote: Somebody else had written separately about this before, and so have I a couple of months ago. I assumed this will be fixed before the next R. Since R 3.0 is supposedly only 6 weeks away, even if it is fixed now it doesn't leave much room for testing. Anyway neither Matrix 1.0-11 (current) nor 1.0-9 (sept 2012) build with current R trunk. The last time it did was 1. 0-9 on 3rd october over 4 months ago. So it appears to be due to change inside r trunk in sept or early oct. Loading required package: Matrix Error in namespaceExport(ns, exports) : undefined exports: .M.classEnv Error : require(Matrix) is not TRUE ERROR: installing package indices failed * removing ‘/svn-loc/R/library/Matrix’ * restoring previous ‘/svn-loc/R/library/Matrix’ make[2]: *** [Matrix.ts] Error 1 make[2]: Leaving directory `/svn-loc/R/src/library/Recommended' make[1]: *** [recommended-packages] Error 2 make[1]: Leaving directory `/svn-loc/R/src/library/Recommended' make: *** [stamp-recommended] Error 2 If it matters, here is what r trunk built with: ./configure --enable-memory-profiling --enable-strict-barrier --enable-byte-compiled-packages --with-valgrind-instrumentation=2 --enable-lto __ 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
Re: [Rd] Matrix does not build with R trunk since Oct.
On Feb 15, 2013, at 9:11 AM, Hin-Tak Leung wrote: Somebody else had written separately about this before, and so have I a couple of months ago. I assumed this will be fixed before the next R. Since R 3.0 is supposedly only 6 weeks away, even if it is fixed now it doesn't leave much room for testing. Anyway neither Matrix 1.0-11 (current) nor 1.0-9 (sept 2012) build with current R trunk. The last time it did was 1. 0-9 on 3rd october over 4 months ago. So it appears to be due to change inside r trunk in sept or early oct. No problem here - Matrix 1.0-11 and R-devel build just fine with your flags (tested on Ubuntu 12.10, x86_64). If in doubt, please remove R-devel and checkout a fresh copy. Also FWIW it's a bad practice to build inside the sources - it often causes all sorts of problems when you try to track the sources and stale files are probably what's hitting you. FWIW: This is likely not the problem you're mentioning, but some recent gcc versions break and LTO is also known to cause issues depending on the compiler version, so tread lightly on the cutting edge. Cheers, Simon Loading required package: Matrix Error in namespaceExport(ns, exports) : undefined exports: .M.classEnv Error : require(Matrix) is not TRUE ERROR: installing package indices failed * removing ‘/svn-loc/R/library/Matrix’ * restoring previous ‘/svn-loc/R/library/Matrix’ make[2]: *** [Matrix.ts] Error 1 make[2]: Leaving directory `/svn-loc/R/src/library/Recommended' make[1]: *** [recommended-packages] Error 2 make[1]: Leaving directory `/svn-loc/R/src/library/Recommended' make: *** [stamp-recommended] Error 2 If it matters, here is what r trunk built with: ./configure --enable-memory-profiling --enable-strict-barrier --enable-byte-compiled-packages --with-valgrind-instrumentation=2 --enable-lto __ 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
Re: [Rd] Matrix does not build with R trunk since Oct.
--- On Fri, 15/2/13, Simon Urbanek simon.urba...@r-project.org wrote: On Feb 15, 2013, at 9:11 AM, Hin-Tak Leung wrote: Somebody else had written separately about this before, and so have I a couple of months ago. I assumed this will be fixed before the next R. Since R 3.0 is supposedly only 6 weeks away, even if it is fixed now it doesn't leave much room for testing. Anyway neither Matrix 1.0-11 (current) nor 1.0-9 (sept 2012) build with current R trunk. The last time it did was 1. 0-9 on 3rd october over 4 months ago. So it appears to be due to change inside r trunk in sept or early oct. No problem here - Matrix 1.0-11 and R-devel build just fine with your flags (tested on Ubuntu 12.10, x86_64). If in doubt, please remove R-devel and checkout a fresh copy. Also FWIW it's a bad practice to build inside the sources - it often causes all sorts of problems when you try to track the sources and stale files are probably what's hitting you. FWIW: This is likely not the problem you're mentioning, but some recent gcc versions break and LTO is also known to cause issues depending on the compiler version, so tread lightly on the cutting edge. Here is a fairly similar post: http://r.789695.n4.nabble.com/Build-from-Source-fails-on-Loading-required-package-Matrix-td4640371.html The eventual solution of that thread seems to be building from tar ball, which is quite beside the whole point of building from svn trunk. FWIW, it is very unproductive to talk about bad practice - in a hand-waving undocumented/unsubstantiated manner - and options that might or might not work. If --enable-lto (or any other options, or build within the dev directory) does not work reliably, it should be either disabled/removed, or documented, or both. Anyway, it has not been working for over 4 months. You have about 6 weeks before this becomes a big problem - big as in wide-spread. Cheers, Simon Loading required package: Matrix Error in namespaceExport(ns, exports) : undefined exports: .M.classEnv Error : require(Matrix) is not TRUE ERROR: installing package indices failed * removing ‘/svn-loc/R/library/Matrix’ * restoring previous ‘/svn-loc/R/library/Matrix’ make[2]: *** [Matrix.ts] Error 1 make[2]: Leaving directory `/svn-loc/R/src/library/Recommended' make[1]: *** [recommended-packages] Error 2 make[1]: Leaving directory `/svn-loc/R/src/library/Recommended' make: *** [stamp-recommended] Error 2 If it matters, here is what r trunk built with: ./configure --enable-memory-profiling --enable-strict-barrier --enable-byte-compiled-packages --with-valgrind-instrumentation=2 --enable-lto __ 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
Re: [Rd] Matrix does not build with R trunk since Oct.
On Feb 15, 2013, at 11:36 AM, Hin-Tak Leung wrote: --- On Fri, 15/2/13, Simon Urbanek simon.urba...@r-project.org wrote: On Feb 15, 2013, at 9:11 AM, Hin-Tak Leung wrote: Somebody else had written separately about this before, and so have I a couple of months ago. I assumed this will be fixed before the next R. Since R 3.0 is supposedly only 6 weeks away, even if it is fixed now it doesn't leave much room for testing. Anyway neither Matrix 1.0-11 (current) nor 1.0-9 (sept 2012) build with current R trunk. The last time it did was 1. 0-9 on 3rd october over 4 months ago. So it appears to be due to change inside r trunk in sept or early oct. No problem here - Matrix 1.0-11 and R-devel build just fine with your flags (tested on Ubuntu 12.10, x86_64). If in doubt, please remove R-devel and checkout a fresh copy. Also FWIW it's a bad practice to build inside the sources - it often causes all sorts of problems when you try to track the sources and stale files are probably what's hitting you. FWIW: This is likely not the problem you're mentioning, but some recent gcc versions break and LTO is also known to cause issues depending on the compiler version, so tread lightly on the cutting edge. Here is a fairly similar post: http://r.789695.n4.nabble.com/Build-from-Source-fails-on-Loading-required-package-Matrix-td4640371.html The eventual solution of that thread seems to be building from tar ball, which is quite beside the whole point of building from svn trunk. And how is that relevant to what I said? Did you follow the advice I sent? If you did and still have an issue, post *exact* details on what you did, what system and tools you are using. FWIW, it is very unproductive to talk about bad practice - in a hand-waving undocumented/unsubstantiated manner Building in sources has two problems: a) the content of the source tree can change so subsequent builds can be different from the clean one - you cannot undo that and b) if you update the sources stale files from previous builds can break the build. If solving your problems is unproductive then I'm not surprised you have them for 4 moths now. - and options that might or might not work. If --enable-lto (or any other options, or build within the dev directory) does not work reliably, it should be either disabled/removed, or documented, or both. R cannot test all aspects of a compiler and detect all its bugs. It is *your* responsibility to provide a working compiler - if you are unwilling to do that, R cannot do anything about that. Anyway, it has not been working for over 4 months. That is not true, obviously, and I have presented a counter-example. It may not have been working for *you* and it's likely a problem in your setup (given your lack of cooperation there is no way to tell for sure). We cannot prevent user errors. We can try to point people in the right direction, but if they refuse to listen it's on their head. You have about 6 weeks before this becomes a big problem - big as in wide-spread. You are yet to show that this is a problem in R at all. You failed to follow the basic instructions in the FAQ. Cheers, Simon Cheers, Simon Loading required package: Matrix Error in namespaceExport(ns, exports) : undefined exports: .M.classEnv Error : require(Matrix) is not TRUE ERROR: installing package indices failed * removing ‘/svn-loc/R/library/Matrix’ * restoring previous ‘/svn-loc/R/library/Matrix’ make[2]: *** [Matrix.ts] Error 1 make[2]: Leaving directory `/svn-loc/R/src/library/Recommended' make[1]: *** [recommended-packages] Error 2 make[1]: Leaving directory `/svn-loc/R/src/library/Recommended' make: *** [stamp-recommended] Error 2 If it matters, here is what r trunk built with: ./configure --enable-memory-profiling --enable-strict-barrier --enable-byte-compiled-packages --with-valgrind-instrumentation=2 --enable-lto __ 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
Re: [Rd] Matrix does not build with R trunk since Oct.
I build from svn daily and I have not had this problem. I build in a tree separate from the source tree. I do think Hin-Tak has a point about clearly specifying that this is how you should do it, in the manual (if that has not already happened). As a casual user, I would expect make clean to clean out any stale files, but perhaps that is not happening. Anyway, seems more to be a possible documentation problem. Kasper On Fri, Feb 15, 2013 at 1:08 PM, Simon Urbanek simon.urba...@r-project.org wrote: On Feb 15, 2013, at 11:36 AM, Hin-Tak Leung wrote: --- On Fri, 15/2/13, Simon Urbanek simon.urba...@r-project.org wrote: On Feb 15, 2013, at 9:11 AM, Hin-Tak Leung wrote: Somebody else had written separately about this before, and so have I a couple of months ago. I assumed this will be fixed before the next R. Since R 3.0 is supposedly only 6 weeks away, even if it is fixed now it doesn't leave much room for testing. Anyway neither Matrix 1.0-11 (current) nor 1.0-9 (sept 2012) build with current R trunk. The last time it did was 1. 0-9 on 3rd october over 4 months ago. So it appears to be due to change inside r trunk in sept or early oct. No problem here - Matrix 1.0-11 and R-devel build just fine with your flags (tested on Ubuntu 12.10, x86_64). If in doubt, please remove R-devel and checkout a fresh copy. Also FWIW it's a bad practice to build inside the sources - it often causes all sorts of problems when you try to track the sources and stale files are probably what's hitting you. FWIW: This is likely not the problem you're mentioning, but some recent gcc versions break and LTO is also known to cause issues depending on the compiler version, so tread lightly on the cutting edge. Here is a fairly similar post: http://r.789695.n4.nabble.com/Build-from-Source-fails-on-Loading-required-package-Matrix-td4640371.html The eventual solution of that thread seems to be building from tar ball, which is quite beside the whole point of building from svn trunk. And how is that relevant to what I said? Did you follow the advice I sent? If you did and still have an issue, post *exact* details on what you did, what system and tools you are using. FWIW, it is very unproductive to talk about bad practice - in a hand-waving undocumented/unsubstantiated manner Building in sources has two problems: a) the content of the source tree can change so subsequent builds can be different from the clean one - you cannot undo that and b) if you update the sources stale files from previous builds can break the build. If solving your problems is unproductive then I'm not surprised you have them for 4 moths now. - and options that might or might not work. If --enable-lto (or any other options, or build within the dev directory) does not work reliably, it should be either disabled/removed, or documented, or both. R cannot test all aspects of a compiler and detect all its bugs. It is *your* responsibility to provide a working compiler - if you are unwilling to do that, R cannot do anything about that. Anyway, it has not been working for over 4 months. That is not true, obviously, and I have presented a counter-example. It may not have been working for *you* and it's likely a problem in your setup (given your lack of cooperation there is no way to tell for sure). We cannot prevent user errors. We can try to point people in the right direction, but if they refuse to listen it's on their head. You have about 6 weeks before this becomes a big problem - big as in wide-spread. You are yet to show that this is a problem in R at all. You failed to follow the basic instructions in the FAQ. Cheers, Simon Cheers, Simon Loading required package: Matrix Error in namespaceExport(ns, exports) : undefined exports: .M.classEnv Error : require(Matrix) is not TRUE ERROR: installing package indices failed * removing ‘/svn-loc/R/library/Matrix’ * restoring previous ‘/svn-loc/R/library/Matrix’ make[2]: *** [Matrix.ts] Error 1 make[2]: Leaving directory `/svn-loc/R/src/library/Recommended' make[1]: *** [recommended-packages] Error 2 make[1]: Leaving directory `/svn-loc/R/src/library/Recommended' make: *** [stamp-recommended] Error 2 If it matters, here is what r trunk built with: ./configure --enable-memory-profiling --enable-strict-barrier --enable-byte-compiled-packages --with-valgrind-instrumentation=2 --enable-lto __ 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 __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
Re: [Rd] Matrix does not build with R trunk since Oct.
Look. I don't see this as my problem - as far as I am concerned, I have donated my time - and over and over - to testing pre-released code. I am not using pre-released code for production work. If the released code in 3.0 does not work correctly in 6 weeks' time, I just don't upgrade. No loss for me there. I don't know why it is degenerating into another distraction about some people's egos. --- On Fri, 15/2/13, Simon Urbanek simon.urba...@r-project.org wrote: On Feb 15, 2013, at 11:36 AM, Hin-Tak Leung wrote: --- On Fri, 15/2/13, Simon Urbanek simon.urba...@r-project.org wrote: On Feb 15, 2013, at 9:11 AM, Hin-Tak Leung wrote: Somebody else had written separately about this before, and so have I a couple of months ago. I assumed this will be fixed before the next R. Since R 3.0 is supposedly only 6 weeks away, even if it is fixed now it doesn't leave much room for testing. Anyway neither Matrix 1.0-11 (current) nor 1.0-9 (sept 2012) build with current R trunk. The last time it did was 1. 0-9 on 3rd october over 4 months ago. So it appears to be due to change inside r trunk in sept or early oct. No problem here - Matrix 1.0-11 and R-devel build just fine with your flags (tested on Ubuntu 12.10, x86_64). If in doubt, please remove R-devel and checkout a fresh copy. Also FWIW it's a bad practice to build inside the sources - it often causes all sorts of problems when you try to track the sources and stale files are probably what's hitting you. FWIW: This is likely not the problem you're mentioning, but some recent gcc versions break and LTO is also known to cause issues depending on the compiler version, so tread lightly on the cutting edge. Here is a fairly similar post: http://r.789695.n4.nabble.com/Build-from-Source-fails-on-Loading-required-package-Matrix-td4640371.html The eventual solution of that thread seems to be building from tar ball, which is quite beside the whole point of building from svn trunk. And how is that relevant to what I said? Did you follow the advice I sent? If you did and still have an issue, post *exact* details on what you did, what system and tools you are using. FWIW, it is very unproductive to talk about bad practice - in a hand-waving undocumented/unsubstantiated manner Building in sources has two problems: a) the content of the source tree can change so subsequent builds can be different from the clean one - you cannot undo that and b) if you update the sources stale files from previous builds can break the build. If solving your problems is unproductive then I'm not surprised you have them for 4 moths now. - and options that might or might not work. If --enable-lto (or any other options, or build within the dev directory) does not work reliably, it should be either disabled/removed, or documented, or both. R cannot test all aspects of a compiler and detect all its bugs. It is *your* responsibility to provide a working compiler - if you are unwilling to do that, R cannot do anything about that. Anyway, it has not been working for over 4 months. That is not true, obviously, and I have presented a counter-example. It may not have been working for *you* and it's likely a problem in your setup (given your lack of cooperation there is no way to tell for sure). We cannot prevent user errors. We can try to point people in the right direction, but if they refuse to listen it's on their head. You have about 6 weeks before this becomes a big problem - big as in wide-spread. You are yet to show that this is a problem in R at all. You failed to follow the basic instructions in the FAQ. Cheers, Simon Cheers, Simon Loading required package: Matrix Error in namespaceExport(ns, exports) : undefined exports: .M.classEnv Error : require(Matrix) is not TRUE ERROR: installing package indices failed * removing ‘/svn-loc/R/library/Matrix’ * restoring previous ‘/svn-loc/R/library/Matrix’ make[2]: *** [Matrix.ts] Error 1 make[2]: Leaving directory `/svn-loc/R/src/library/Recommended' make[1]: *** [recommended-packages] Error 2 make[1]: Leaving directory `/svn-loc/R/src/library/Recommended' make: *** [stamp-recommended] Error 2 If it matters, here is what r trunk built with: ./configure --enable-memory-profiling --enable-strict-barrier --enable-byte-compiled-packages --with-valgrind-instrumentation=2 --enable-lto __ 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
Re: [Rd] Matrix does not build with R trunk since Oct.
On Feb 15, 2013, at 1:55 PM, Hin-Tak Leung wrote: Look. I don't see this as my problem - as far as I am concerned, I have donated my time - and over and over - to testing pre-released code. I am not using pre-released code for production work. If the released code in 3.0 does not work correctly in 6 weeks' time, I just don't upgrade. No loss for me there. It works - confirmed by several people. You have a problem, but you didn't tell us the specifics of the problem so there's nothing we can do. I don't know why it is degenerating into another distraction about some people's egos. I don't either - it's not productive. Cheers, Simon --- On Fri, 15/2/13, Simon Urbanek simon.urba...@r-project.org wrote: On Feb 15, 2013, at 11:36 AM, Hin-Tak Leung wrote: --- On Fri, 15/2/13, Simon Urbanek simon.urba...@r-project.org wrote: On Feb 15, 2013, at 9:11 AM, Hin-Tak Leung wrote: Somebody else had written separately about this before, and so have I a couple of months ago. I assumed this will be fixed before the next R. Since R 3.0 is supposedly only 6 weeks away, even if it is fixed now it doesn't leave much room for testing. Anyway neither Matrix 1.0-11 (current) nor 1.0-9 (sept 2012) build with current R trunk. The last time it did was 1. 0-9 on 3rd october over 4 months ago. So it appears to be due to change inside r trunk in sept or early oct. No problem here - Matrix 1.0-11 and R-devel build just fine with your flags (tested on Ubuntu 12.10, x86_64). If in doubt, please remove R-devel and checkout a fresh copy. Also FWIW it's a bad practice to build inside the sources - it often causes all sorts of problems when you try to track the sources and stale files are probably what's hitting you. FWIW: This is likely not the problem you're mentioning, but some recent gcc versions break and LTO is also known to cause issues depending on the compiler version, so tread lightly on the cutting edge. Here is a fairly similar post: http://r.789695.n4.nabble.com/Build-from-Source-fails-on-Loading-required-package-Matrix-td4640371.html The eventual solution of that thread seems to be building from tar ball, which is quite beside the whole point of building from svn trunk. And how is that relevant to what I said? Did you follow the advice I sent? If you did and still have an issue, post *exact* details on what you did, what system and tools you are using. FWIW, it is very unproductive to talk about bad practice - in a hand-waving undocumented/unsubstantiated manner Building in sources has two problems: a) the content of the source tree can change so subsequent builds can be different from the clean one - you cannot undo that and b) if you update the sources stale files from previous builds can break the build. If solving your problems is unproductive then I'm not surprised you have them for 4 moths now. - and options that might or might not work. If --enable-lto (or any other options, or build within the dev directory) does not work reliably, it should be either disabled/removed, or documented, or both. R cannot test all aspects of a compiler and detect all its bugs. It is *your* responsibility to provide a working compiler - if you are unwilling to do that, R cannot do anything about that. Anyway, it has not been working for over 4 months. That is not true, obviously, and I have presented a counter-example. It may not have been working for *you* and it's likely a problem in your setup (given your lack of cooperation there is no way to tell for sure). We cannot prevent user errors. We can try to point people in the right direction, but if they refuse to listen it's on their head. You have about 6 weeks before this becomes a big problem - big as in wide-spread. You are yet to show that this is a problem in R at all. You failed to follow the basic instructions in the FAQ. Cheers, Simon Cheers, Simon Loading required package: Matrix Error in namespaceExport(ns, exports) : undefined exports: .M.classEnv Error : require(Matrix) is not TRUE ERROR: installing package indices failed * removing ‘/svn-loc/R/library/Matrix’ * restoring previous ‘/svn-loc/R/library/Matrix’ make[2]: *** [Matrix.ts] Error 1 make[2]: Leaving directory `/svn-loc/R/src/library/Recommended' make[1]: *** [recommended-packages] Error 2 make[1]: Leaving directory `/svn-loc/R/src/library/Recommended' make: *** [stamp-recommended] Error 2 If it matters, here is what r trunk built with: ./configure --enable-memory-profiling --enable-strict-barrier --enable-byte-compiled-packages --with-valgrind-instrumentation=2 --enable-lto __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel __
Re: [Rd] Matrix does not build with R trunk since Oct.
--- On Fri, 15/2/13, Simon Urbanek simon.urba...@r-project.org wrote: On Feb 15, 2013, at 1:55 PM, Hin-Tak Leung wrote: Look. I don't see this as my problem - as far as I am concerned, I have donated my time - and over and over - to testing pre-released code. I am not using pre-released code for production work. If the released code in 3.0 does not work correctly in 6 weeks' time, I just don't upgrade. No loss for me there. It works - confirmed by several people. You have a problem, but you didn't tell us the specifics of the problem so there's nothing we can do. I do not have a problem. I do not need to spend time regularly testing pre-release code, and I think I should stop. I don't know why it is degenerating into another distraction about some people's egos. I don't either - it's not productive. Cheers, Simon --- On Fri, 15/2/13, Simon Urbanek simon.urba...@r-project.org wrote: On Feb 15, 2013, at 11:36 AM, Hin-Tak Leung wrote: --- On Fri, 15/2/13, Simon Urbanek simon.urba...@r-project.org wrote: On Feb 15, 2013, at 9:11 AM, Hin-Tak Leung wrote: Somebody else had written separately about this before, and so have I a couple of months ago. I assumed this will be fixed before the next R. Since R 3.0 is supposedly only 6 weeks away, even if it is fixed now it doesn't leave much room for testing. Anyway neither Matrix 1.0-11 (current) nor 1.0-9 (sept 2012) build with current R trunk. The last time it did was 1. 0-9 on 3rd october over 4 months ago. So it appears to be due to change inside r trunk in sept or early oct. No problem here - Matrix 1.0-11 and R-devel build just fine with your flags (tested on Ubuntu 12.10, x86_64). If in doubt, please remove R-devel and checkout a fresh copy. Also FWIW it's a bad practice to build inside the sources - it often causes all sorts of problems when you try to track the sources and stale files are probably what's hitting you. FWIW: This is likely not the problem you're mentioning, but some recent gcc versions break and LTO is also known to cause issues depending on the compiler version, so tread lightly on the cutting edge. Here is a fairly similar post: http://r.789695.n4.nabble.com/Build-from-Source-fails-on-Loading-required-package-Matrix-td4640371.html The eventual solution of that thread seems to be building from tar ball, which is quite beside the whole point of building from svn trunk. And how is that relevant to what I said? Did you follow the advice I sent? If you did and still have an issue, post *exact* details on what you did, what system and tools you are using. FWIW, it is very unproductive to talk about bad practice - in a hand-waving undocumented/unsubstantiated manner Building in sources has two problems: a) the content of the source tree can change so subsequent builds can be different from the clean one - you cannot undo that and b) if you update the sources stale files from previous builds can break the build. If solving your problems is unproductive then I'm not surprised you have them for 4 moths now. - and options that might or might not work. If --enable-lto (or any other options, or build within the dev directory) does not work reliably, it should be either disabled/removed, or documented, or both. R cannot test all aspects of a compiler and detect all its bugs. It is *your* responsibility to provide a working compiler - if you are unwilling to do that, R cannot do anything about that. Anyway, it has not been working for over 4 months. That is not true, obviously, and I have presented a counter-example. It may not have been working for *you* and it's likely a problem in your setup (given your lack of cooperation there is no way to tell for sure). We cannot prevent user errors. We can try to point people in the right direction, but if they refuse to listen it's on their head. You have about 6 weeks before this becomes a big problem - big as in wide-spread. You are yet to show that this is a problem in R at all. You failed to follow the basic instructions in the FAQ. Cheers, Simon Cheers, Simon Loading required package: Matrix Error in namespaceExport(ns, exports) : undefined exports: .M.classEnv Error : require(Matrix) is not TRUE ERROR: installing package indices failed * removing ‘/svn-loc/R/library/Matrix’ * restoring previous ‘/svn-loc/R/library/Matrix’ make[2]: *** [Matrix.ts] Error 1 make[2]: Leaving directory `/svn-loc/R/src/library/Recommended' make[1]: *** [recommended-packages] Error 2 make[1]: Leaving directory `/svn-loc/R/src/library/Recommended' make: *** [stamp-recommended] Error 2 If it
Re: [Rd] Matrix does not build with R trunk since Oct.
FWIW, extracting snapshot source elsewhere outside svn, run tools/rsync-recommended then just plain ./configure make doesn't work either. Nothing to do with building inside checkout nor extra configure options. This is fedora 18, x86_64. --- On Fri, 15/2/13, Hin-Tak Leung ht...@users.sourceforge.net wrote: Somebody else had written separately about this before, and so have I a couple of months ago. I assumed this will be fixed before the next R. Since R 3.0 is supposedly only 6 weeks away, even if it is fixed now it doesn't leave much room for testing. Anyway neither Matrix 1.0-11 (current) nor 1.0-9 (sept 2012) build with current R trunk. The last time it did was 1. 0-9 on 3rd october over 4 months ago. So it appears to be due to change inside r trunk in sept or early oct. Loading required package: Matrix Error in namespaceExport(ns, exports) : undefined exports: .M.classEnv Error : require(Matrix) is not TRUE ERROR: installing package indices failed * removing ‘/svn-loc/R/library/Matrix’ * restoring previous ‘/svn-loc/R/library/Matrix’ make[2]: *** [Matrix.ts] Error 1 make[2]: Leaving directory `/svn-loc/R/src/library/Recommended' make[1]: *** [recommended-packages] Error 2 make[1]: Leaving directory `/svn-loc/R/src/library/Recommended' make: *** [stamp-recommended] Error 2 If it matters, here is what r trunk built with: ./configure --enable-memory-profiling --enable-strict-barrier --enable-byte-compiled-packages --with-valgrind-instrumentation=2 --enable-lto __ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
