similar to: testing

xapian-core-1.2.24 Unclear yet about any possible use of patches, either for MSYS/MINGW and/or MSYS2/MINGW, for xapian-core versions(?), but here are sections of the 'configure' and 'make check' logs I output from a MSYS/MINGW (g++ 5.3.0) compile on XP SP3 (32 bit) Home Edition (xapian-core-1.2.24). configure log checking for setenv... no checking for _putenv_s... yes

MS XP SP3 (32 bit) https://sourceforge.net/projects/msys2/files/REPOS/MINGW/i686/ mingw-w64-i686-xapian-core-1.4.1-1-any.pkg.tar.xz does not contain /mingw32/lib/libxapian.la. cf: http://nurmi-labs.blogspot.com/2016/11/git.html (for setup) https://sourceforge.net/projects/msys2/files/REPOS/MINGW/i686/ mingw-w64-i686-libtool-2.4.6-7-any.pkg.tar.xz (added)

Dear Olly Betts, same 32 bit compiler version hardware OS OS version as here (where remotetcp_chert passed and skipped 3) xapian-core-1.2.21.tar.xz http://nurmi-labs.blogspot.com/2015/10/xapian.html ./apitest backend remoteprog_brass: All 225 tests passed, 3 skipped. ./apitest backend remotetcp_brass: All 225 tests passed, 3 skipped. ./apitest backend remoteprog_chert: All 225 tests passed,

I recently wrote a post on installing "Git for Windows" on a legacy XP SP3 Home box. http://nurmi-labs.blogspot.com/2016/11/git.html I added some missing files from the MSYS2 packages which were removed for the downloadable "Git for Windows" installer and a compiler and some additional libraries. For other utilities (bison, flex, info, m4, make, and csh/tcsh), and code I

System: Microsoft Windows XP Home Edition CPUs: Intel(R) Atom(TM) CPU N270 @1.60GHz setup for the 'Git for Windows' with MSYS2 gcc-6.1.0 plus utilties and libraries were added http://nurmi-labs.blogspot.com/2016/11/git.html obviously, with Home Edition, no network was setup http://nurmi-labs.blogspot.com/p/xapian-ms.html System: Slackware Linux (version 14.0) CPUs: Intel(R) Atom(TM)

On 1/18/23 17:39, Dominick Samperi wrote: > Thanks, > > But this didn't work. It installs msys2 along with lots of other > stuff, and gdb would not start as before (missing DLL's). > > Then I tried to run the command you suggested again, and there was a > warning from the package manager about a cycle detected, but now gdb > starts with the following messages...

Thanks for the detailed feedback Tomas, I ran the command 'pacman -Syuu' again, just to be sure, and this time it says "there is nothing to do." It appears that gdb is working. I was spooked by the diagnostics that you say is a known (not serious) issue. My mistake was not setting a breakpoint on main, so I confused problems with gdb with problems with the program I'm

On 1/18/23 19:41, Dominick Samperi wrote: > Thanks for the detailed feedback Tomas, > > I ran the command 'pacman -Syuu' again, just to be sure, and this time > it says "there is nothing to do." > > It appears that gdb is working. I was spooked by the diagnostics that > you say is a known (not serious) issue. > > My mistake was not setting a

Thanks, But this didn't work. It installs msys2 along with lots of other stuff, and gdb would not start as before (missing DLL's). Then I tried to run the command you suggested again, and there was a warning from the package manager about a cycle detected, but now gdb starts with the following messages... Traceback (most recent call last): File "<string>", ine 3, in

On second thought, there is a lot of metapramming code in Rcpp that runs before main, so I was wrong to say nothing can happen before main() is called. Strategically placed print statements may be the best strategy. On Wed, Jan 18, 2023 at 8:17 PM Dominick Samperi <djsamperi at gmail.com> wrote: > Since these ?stray threads? were appearing before I installed gdb into > Rtools42, this

I believe that repo just follows the directions on my blog. Without seeing Dr. Hodges?s code, my initial concern is the many references to Cygwin. My method specifically does not use Cygwin but MSYS2 and Mingw64/Rtools35. That will likely change to solely Rtools40 once R3.6 is released due to the Msys system being built in to it. There may be some library conflicts between Cygwin and

On 07/01/2015 5:20 PM, Jeroen Ooms wrote: > On Wed, Jan 7, 2015 at 8:00 AM, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: >> >> This version includes only minor updates to the tools. I indicated last summer that I was hoping to update GCC from the current version 4.6.3 before the R 3.2.0 release, but this now looks unlikely, unless someone else with experience building

>>>>> Erin Hodgess >>>>> on Fri, 1 Mar 2019 12:30:35 -0700 writes: > Yay! I re-installed everything and got through "Make > distribution"! I have one more question, please: I am > running the make check-all. I have an error at reg-1d. > It stops the process. However, the mean difference (as > per the file) is

On 1/18/23 04:33, Dominick Samperi wrote: > Hello, > > I tried installing gdb into Rtools42 following the instructions here > https://cran.r-project.org/bin/windows/base/howto-R-4.2.html > > I ran 'pacman -Sy gdb', and the installation seemed to complete without > problems. > > But gdb could not be started because incorrect DLL versions were installed, > in

I've posted the results of 'make check' for xapian "oldstable" (xapian-core-1.2.24) compiled on Slackware-14.0 (32 bit) here: http://nurmi-labs.blogspot.com/p/xapian-linux-old-stable-sse.html xapian-linux-old-stable-sse Summary ./apitest backend none: All 58 tests passed. ./apitest backend inmemory: All 228 tests passed, 8 skipped. ./apitest backend brass: All 304 tests

Very timely, as this is how I got into the problem I posted about earlier; maybe some of the problems I ran into will mean more to the you and the experts on this thread, Dr. Murdoch.For reference, I run Windows 7 64bit, and I am trying to build a 64 bit version of R-3.1.2. As we discussed offline, Dr. Murdoch, I've been trying to build R using more recent tools than GCC4.6.3 prerelease.

Oh, I forgot to mention that besides setting AR, RANLIB and the stack probing fix, you also need a very up to date binutils. 2.25 was out in december. Even with that , if you linker's default is not what you are compiling for (i.e. a multiarch toolchain), you need to set GNUTARGET also, i.e. -m32/-m64 is not enough. Some fix to autodetect non-default targets went in after christmas before the

Hello! I'm not sure if this is the right place to post this, so apologies in advance if I'm not in the right list. I downloaded the OpenBLAS and am following Avraham Adler's great instructions. However, when I run make, things go well to a certain point, and then go bad: make [snip] touch cygopenblas_haswellp-r0.3.5.a make -j 1 -C test all make[1]: Entering directory

hi i?m trying to build the ruby bindings in xapian 1.1.2 on win xp. i?ve 1. pulled the tags/1.1.2 revision from svn 2. built SWIG from repo via MinGW and MSYS (swig -help works, so build seems ok to me) 3. built xapian-core following readme in ...\win32msvc, apitest doesn?t give errors now if i try to build: "...\ruby>nmake SWIGBUILD=1 Microsoft (R) Program

Answering a few questions: * Unclear why it's necessary to rename nbdkit-common.h -> nbdkit-compat.h - It's not a rename, but a new file. nbdkit-compat.h is included for PE DLL compatibility, and is included in nbdkit-common.h * Functions are indirected through struct nbdkit_functions _nbdkit_functions which I guess is necessary because of PE linking (we've had similar