search for: watcom

The attached set of patches adds support for OS/2 using Watcom compiler (tested with Open Watcom 1.9). My only interest was building a working dll (the last patch in the set adds a makefile for it), therefore I did not touch other places: If there is interest, I can do so. Regards. -- O.S. -------------- next part -------------- A non-text attachment was scr...

...1/22/17, Dave Yeo <dave.r.yeo at gmail.com> wrote: > On 01/22/17 09:57 AM, Ozkan Sezer wrote: >> On 1/22/17, Dave Yeo <dave.r.yeo at gmail.com> wrote: >>> On 01/22/17 05:35 AM, Ozkan Sezer wrote: >>>> The attached set of patches adds support for OS/2 using Watcom compiler >>>> (tested with Open Watcom 1.9). My only interest was building a working >>>> dll (the last patch in the set adds a makefile for it), therefore I did >>>> not touch other places: If there is interest, I can do so. >>> >> >> Discl...

Hello, as usual for me with precompiled libraries, the ones of the vorbis- sdk didn't work for me in WATCOM/Win32, so i compiled them on my own (vorbis_static.lib / vorbisfile_static.lib - it was possible after some slight changes like slightly modifiyng the typedef types that Watcom didn't know) The libraries work fine so far (like getting the file info), but when calling ov_read the program ha...

A colleague is using Watcom F77 version 11 in Windows NT, and wants to create DLLs callable from R. (He was previously able to do external calls from S-PLUS). Does anyone know what magic is necessary so that it uses the right calling convention? In a debugger, it appears it's using a register-based calling convention,...

On 01/22/17 05:35 AM, Ozkan Sezer wrote: > The attached set of patches adds support for OS/2 using Watcom compiler > (tested with Open Watcom 1.9). My only interest was building a working > dll (the last patch in the set adds a makefile for it), therefore I did > not touch other places: If there is interest, I can do so. Most of the patches can have s/__EMX__/__OS2__/ excepting the nasm.h on...

Hello. I am trying to use a FORTRAN subroutine from within R (Windows version). This fortran subroutine is compiled using the Open Watcom Fortran compiler and the compiled object file is called ritscale.obj. Following the explanation on pages 193-194 of "The New S language" I use the dyn.load command: > dyn.load("f:/maxent/ritscale.obj") Error in dyn.load(x, as.logical(local), as.logical(now)) : unab...

...perhaps, diff --git a/include/FLAC/export.h b/include/FLAC/export.h index d52f0bb..5d40421 100644 --- a/include/FLAC/export.h +++ b/include/FLAC/export.h @@ -66,6 +66,13 @@ #define FLAC_API __declspec(dllimport) #endif +#elif defined(__OS2__) +#if defined(FLAC_API_EXPORTS) && defined(__WATCOMC__) && defined(__SW_BD) +#define FLAC_API __declspec(__cdecl) __declspec(dllexport) +#else +#define FLAC_API __declspec(dllexport) +#endif + #elif defined(FLAC__USE_VISIBILITY_ATTR) #define FLAC_API __attribute__ ((visibility ("default"))) Another option is for the caller to de...

This adds checks for Watcom C DOS cross-compiler in a manner analogous to mingw compiler for Windows. The compiler is not commonly present in Linux distributions due to a non-free license. Signed-off-by: Lubomir Rintel <lkundrak at v3.sk> --- dosutil/Makefile | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a...

Ozkan Sezer wrote: > Anyways, with the changed exports.h patch, every need should > be met now.. Sorry, which patch is that? Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

On 01/22/17 02:00 PM, Ozkan Sezer wrote: > Question: Does emx support __declspec(dllexport) so I can adjust > these changes? Because the emx build of the dll seems to have > exported_everything_ :( GCC supports __declspec(dllexport) though it still needs a def file, with no exports. Libtool doesn't currently and as flac uses libtool... Dave

I spotted recently that since we switched to git, commit notifications haven't been sent to the xapian-commits list. We can probably install a hook for git to get them flowing again, but given that none of the ~20 subscribers to the list has complained, I'm wondering if a list for commits is still useful. Perhaps with a decentralised version control system it isn't, though the

On Tue, Jun 30, 2015 at 12:30:35PM -0700, Eric Lindblad wrote: > I don't know if it would be of any use - and I know that > the configure script searches for gawk, sed and grep - > but Watcom has free 32 and 64 bit compilers, and > the msvc files for Xapian no longer appear to be > maintained, so perhaps Xapian build files written for > [Open] Watcom could be made, as such allocating also > for the zlib and libuuid dependencies. I would encourage anyone interested to try to...

...ure runs successfully on two other windows machines. For reference, the PATH environment variable is: C:\Program Files\SSH Communications Security\SSH Secure Shell;C:\cygwin\bin;C:\Program Files\R\R-2.7.1\bin The PATH System variable is: c:\Rtools\bin;c:\Rtools\perl\bin;c:\Rtools\MinGW\bin;C:\watcom-1.3\binnt;C:\watcom-1.3\binw; %GTK_BASEPATH%\bin;C:\Program Files\MiKTeX 2.5\miktex\bin;%systemroot%\system32;%systemroot%;%systemroot%\system32\wbem;c:\program files\ati technologies\ati control panel;C:\Program Files\MATLAB\R2006a\bin\win32;C:\Program Files\ggobi;C:\Program Files\R\R-2.7.1\bi...

...string may be usable if its length is passed separately. and I have been taking a look. The linkage sends char ** to Fortran. On the other hand, INTPR and DBLEPR assume Fortran character strings are char *. On all my systems DBLEPR works and .Fortran does not, but I do know of one compiler (Watcom Fortran for Windows NT) where the linkage really is equivalent to char **. Fortran in S takes the first string in a character vector and passes that as char * (except on the Watcom-compiled Windows version), as far as I can deduce without the source code. I think we should either ban character s...

On Thu, 14 Dec 2000 10:06:39 +1100, Michael Smith wrote: >>I've done a port for OS/2 using Watcom C++, including a simple command line >>player based on vorbisfile_example.c, which can be downloaded from >>http://silk.apana.org.au/utils.html >>It'd be nice if my changes could be commited to CVS, should I just post >>patches here? > >Yes, unless they're hug...

...ill hard code the menu in the code, and then somebody else can remove that restriction. May be we can add some kind of keyword to the config file which syslinux ignores and the comboot menu does something with it. I have one question about comboot: If I write a DOS program using C (compiled using watcom -3 -mt -osx flags) and use only BIOS interrupts and the DOS interrupts which comboot API supports, it should work in syslinux right? In that case, it will be easy to debug, since what I write will be a simple DOS .COM file. - Murali

...th the leaps library so I don't know what functions it uses. If it relies on internal R functions (I hope that you got the R version) then you need to get your fortran compiler to export those functions from the dll with the correct collection of underscores (in the correct places), for Watcom C to figure out how to link to them. I have only had luck using Watcom C linked to C so far (and even that has not been entirely successful as demonstrated by the state of survival4). Luke Tierney has been providing some very helpful info on this as he is currently working on dynamic loa...

...ion: -current Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: liug at mama.indstate.edu It seems the scanf format %[0-9] in Watcom doesn't work the same way as in gcc. Here is a note in the Watcom C/C++ reference: Note: A dash (-) in the scanset doesn't indicate a range of characters. For example, the string [0-9] matches the characters 0, -, and 9, not the characters 0 through 9. I have to make t...

http://bugzilla.mindrot.org/show_bug.cgi?id=258 ------- Additional Comments From liug at mama.indstate.edu 2002-05-28 02:53 ------- Here are some more info I gathered from the Watcom newsgroup: The C99 draft explicitly said that: "If a - character is in the scanlist and is not the first, nor the second where the first character is a ^, nor the last character, the behavior is implementation-defined." So (assuming the draft did not change in this respect) for...

Hello! Is it possible to make the sources a bit more portable? I'm on QNX4 with Watcom C v10.6B which has no support for int64. I'd like to be able to compile as many modules as do not depend on int64. (Currently I do not need SFTP that bad, the SSH is enough for me) -- Best regards, Anthony mailto:rz1a at mail.ru