similar to: added check/define for int64_t

Displaying 20 results from an estimated 500 matches similar to: "added check/define for int64_t"

2012 May 01
8
VGABIOS patches
Couple of patches to fix an overflow, optimize a bit and support bigger resolutions using Windows 8.
2004 Jun 10
4
patches for xiph build setup
Hi, I offered some time ago to do some build cleanup. Today I did so and here's my slew of patches. Basically, they - touch ogg, vorbis, vorbis-tools and theora - fix a bunch of autotools issues - uniformize the use of them across the four - fix compile/link flags - use pkgconfig if it's available to detect flags - for vorbis-tools, generate and use config.h - add -uninstalled .pc stuff
2004 Jun 10
4
patches for xiph build setup
Hi, I offered some time ago to do some build cleanup. Today I did so and here's my slew of patches. Basically, they - touch ogg, vorbis, vorbis-tools and theora - fix a bunch of autotools issues - uniformize the use of them across the four - fix compile/link flags - use pkgconfig if it's available to detect flags - for vorbis-tools, generate and use config.h - add -uninstalled .pc stuff
2009 Jul 06
8
[LLVMdev] switching to llvm-g++ as the host compiler
IANACE (I Am Not A Configury Expert :-), but I've been asked to reconfigure LLVM and LLVM-GCC to build with LLVM-GCC (perhaps more accurately, LLVM-G++). The patches to do this are short. In the LLVM tree, this suffices; it looks for LLVM-GCC first, and if that fails, falls back to GCC: Index: llvm.test/autoconf/configure.ac
2009 Jul 07
0
[LLVMdev] switching to llvm-g++ as the host compiler
Please make sure when we are running the llvm test suite the "native" executables are still built with gcc (or another compiler) unless it's explicitly specified to be llvm-gcc. Thanks. Evan On Jul 6, 2009, at 3:47 PM, Stuart Hastings wrote: > IANACE (I Am Not A Configury Expert :-), but I've been asked to > reconfigure LLVM and LLVM-GCC to build with LLVM-GCC
2004 Aug 06
2
libspeex/SSE Intrinsics with GCC 3.3.x
On Fri, Apr 02, 2004 at 12:08:52AM -0500, Jean-Marc Valin wrote: > I'm aware of the problem, but I don't know how to get autoconf to handle > that properly. If someone knows how to make that work with autoconf even > with non-gcc compilers and with default CFLAGS, I'm interested. It's easy enough to test whether gcc will accept -msse and ifdef out the intrinsics code
2001 Jan 29
2
Mac OS X / Darwin patch for vorbis-tools
This patch (along with all the previous patches) gets oggenc and ogg123 working. This does not get vorbiscomment working, although I assume that would be trivial -- just add the getopt stuff to the project just like I did in ogg123. In addition to this patch, as I just mentioned, getopt1.c getopt.h and getopt.c need to be copied from oggenc to ogg123 and added. The host check in
2019 Jan 21
18
[PATCH xf86-video-nouveau 00/17] autotools configuration cleanups
Series of cleanups to autotools build config files to utilize the available xorg-server macros, defaults and more closely match other modern Xorg drivers. Notable improvements: - gitignore fully covers potential build artifacts - Simplify logic given stated minimum required version of xorg-server 1.8 - Remove use of deprecated, outdated or no longer required macros - Utilize xorg macros where
2008 Dec 18
1
Tip for removing -c99 when compiling with icc
Dear developeRs, As of icc 10, the -c99 option is deprecated, and generates a lot of warnings when compiling R or R packages. If you use CC="icc -std=c99" instead of just CC="icc", R's configure will not add the -c99 option, and the code seems to compile and run just fine. (Please don't hesitate to let me know if this is a bad idea. :-) -- Regards, Bj?rn-Helge
2007 Apr 26
1
requiring array indices be int64_t
With dtrace, I can use function arguments in the form of arg0, arg1, etc, as indices into an "associative" array. If all that an array takes as an index is an int64_t, is there any reason for dtrace to require me to have an explicit type conversion in there rather than having it do it for me automatically? At present I need to do: mblks[arg0] or mblks[(int64_t)((mblk_t
2003 Sep 19
1
int64_t compile problem
I run Linux 2.2.21 w/ gcc version 2.7.2.3 and it does not even configure. I am interested in a workaround on this. OpenSSH 3.61p1 configures and compiles but not 3.7.1p1. Here is a "tail" of the configure below. Thx, Brad checking for mode_t... yes checking for struct sockaddr_storage... no checking for struct sockaddr_in6... no checking for struct in6_addr... no checking
2008 Dec 16
3
liboggz: use ogg_int64_t instead of C99 int64_t for the benefit of you-can-guess-who
A widely used platform doesn't bother to have C99 integer types, so this allows building with it. Reported by sirlemonhead on IRC. Index: src/tools/oggz_tools.c =================================================================== --- src/tools/oggz_tools.c (revision 3827) +++ src/tools/oggz_tools.c (working copy) @@ -450,7 +450,7 @@ dg->pt = (iframe + pframe) >> 9;
2008 Dec 16
1
liboggz: use ogg_int64_t instead of C99 int64_t for the benefit of you-can-guess-who
> Since these are the only two uses of int64_t instead of ogg_int64_t in > liboggz, please commit. In svn. Didn't get the OK from Conrad from committing to his software, hope it's OK kfish ^_^
2015 Oct 05
0
Compiling v2.2.19 - internal compiler error: segmentation fault (test-timing.c -> int64_t issue?)
Hi, I am trying to compile a 64-build of the latest dovecot v2.2.19 on my SuSE Linux Enterprise Server 10 (x64) system. I've run ./configure with two parameters, the --prefix one and the --with-ssldir one. During the make stage, I am getting the following 'internal compiler error' message : --------------------------------------------- [...] gcc -DHAVE_CONFIG_H -I. -I../..
2000 May 17
0
Re: CVS changes
Forwarded, so the list knows about it. I'm making the changes now. Monty > Hey Monty, I have a few fixes that need to get made to the CVS tree to > fix a couple of broken things. None are worth sending you a diff. > > vorbisfile.o needs to be removed from the lib/Makefile in LFILES since > vorbisfile.a is a seperate lib now. As it stands I get unresolved > symbol errors
2012 Jun 14
5
Opus and WebM support have landed
Hi, quick info. Yesterday Rillian landed Oneman's patches adding ogg/opus and WebM support on Icecast trunk. Big thanks for all the work that has gone into this! Please use trunk for your testing and development in this area from now. If you run into problems please send mails/patches/bitch'n'moan-on-IRC/... It's important to find any problems by testing it in every possible
2010 Apr 19
1
[PATCH matahari] Replaces the existing HAL code for ProcessorAgent with udev.
Stripped out the HAL support code and replaced with calls to udev. The remainder of the code to extract CPU details parses through the /proc/cpuinfo file since udev/sysfs will not return such information. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- configure.ac | 3 +- src/Makefile.am | 4 +- src/processors.cpp | 94
2001 Jan 18
4
GNU autoconf/automake in OpenSSH
I make changes in open source tree to implement autoconf/automake. What's new ? - new acinclude.m4 ( based on old aclocal.m4 + new macros OSSH_EXPAND_PATHS and OSSH_SHOW_OPTIONS - new configure option --with-askpass=PATH - updated acconfig.h ( based on old acconfig.h with removed USE_EXTERNAL_ASKPASS and new ASKPASS_PATH + new config.h.top and config.h.bot ) !!! in this file has two lines
2009 Jun 11
1
help installing Rmpi
Hello R users and developers, I would like to install Rmpi so that I may take advantage of all of the CPUs in my computer, but I cannot get it to install and I am not very good with linux so it is adding to the headache. I have looked through the help archive, but I have not been successful at getting Rmpi to work. I am not sure if I am even installing openMPI correctly in linux. I would really
2017 Jan 15
4
Updated CFLAGS patches and make test compilation conditional
Hi Erik, I've found a middleground for the problem of setting default CFLAGS. I've gone back to setting them if {C,CXX,CPP,LD}FLAGS are unset at the onset of the configure script (i.e., the user hasn't specified anything) and then proceed to set them to the defaults as before. This has been suggested before: https://lists.gnu.org/archive/html/autoconf/2006-04/msg00022.html In