search for: fopen64

...tionally #defining _BSD_SOURCE doesn't feel right. I agree. I'll find a better way. > * #undefining libc symbols based on __ELCC__. This looks like a musl > issue rather than just elcc. I'm actually rarther suspicious of musl > here too: neither C99 nor C++11 reserve (e.g.) fopen64. That said, > we've put in worse hacks to support broken platforms (see > -fms-compatibility). I'll talk to the musl guys about this. I don't think they like the idea of being referred to as a "broken platform". > * sys/time.h: not sure this exists on all systems...

...if(!func) func = ( FILE * (*)(const char*, const char *))dlsym(RTLD_NEXT, "fopen"); if(strcmp(fpath,"/etc/nsswitch.conf")==0) fpath = "/etc/nsswitch_samba.conf"; printf(" calling fopen(%s, %s)\n", fpath, mode); return(func(fpath, mode)); } FILE* fopen64(const char *fpath, const char *mode ){ static FILE * (*func)(const char*, const char *); if(!func) func = ( FILE * (*)(const char*, const char *))dlsym(RTLD_NEXT, "fopen64"); if(strcmp(fpath,"/etc/nsswitch.conf")==0) fpath = "/etc/nsswitch_samba.conf"; p...

Hi All, I am doing some work to extend the target library information and ran across some function names in the old simplify-libcalls pass that are prefixed with \1. For example: \1__isoc99_scanf \1__isoc99_sscan \1fopen64 \1fseeko64 \1fstat64 \1fstatvfs64 Where do these \1 names come from? What target triples are they expected on? -- Meador Inge CodeSourcery / Mentor Embedded

...orking on this problem by first trying code without the Altivec intrinsics. I'm trying to use the cross compiler on the c code outputted by "llc -march c" and have run into this linker problem (spewed by the cross compiler): Command line : error: L0039: reference to undefined symbol .fopen64 in file /tmp/cc4tgLu5.o Command line : error: L0039: reference to undefined symbol ._IO_putc in file /tmp/cc4tgLu5.o Command line : error: L0039: reference to undefined symbol ._IO_getc in file /tmp/cc4tgLu5.o Command line : error: L0039: reference to undefined symbol .stat64 in file /tmp/cc4tgLu5....

ELLCC is a compilation tool chain based on clang/LLVM, libc++ and the musl standard C library for Linux. Recently I was asked if ELLCC pre-built binaries could be used to build clang/LLVM TOT. It turns out that it can with some simple patches. This is a simple way to bootstrap clang/LLVM on an arbitrary Linux system that either doesn't have GCC or has a version of GCC that is too old to

Hi, I was trying the wine esound output plugin but the sound is really choppy. On IRC it was noted that only the OSS output worked properly and that esound implementation was quite crappy. However I really need esound output since we use an LTSP setup. The sound if only available through esd. Are there any possibilities to further tweak the esound settings? The software in question is windows

On Apr 6, 2008, at 11:24 AM, Sunjae Park wrote: > On Sunday 06 April 2008 06:53:06 am Bill Wendling wrote: >> (snip) >> Hi Sunjae, >> >> You'll need to compile llvm-gcc as a cross-compiler to get it to >> accept altivec intrinsics and PPC-specific flags. >> >> -bw > > Thanks, Bill. I was afraid of that. > > Any pointers on how to do

On Sunday 06 April 2008 06:53:06 am Bill Wendling wrote: > (snip) > Hi Sunjae, > > You'll need to compile llvm-gcc as a cross-compiler to get it to > accept altivec intrinsics and PPC-specific flags. > > -bw Thanks, Bill. I was afraid of that. Any pointers on how to do this? I'm able to build llvm-gcc-4.2 x86 natively, but not the powerpc version. Using

I've got a file that's approximately 2.2GB and it seems to be foiling file.info(). When I run `stat' from the shell I get zooey:> stat data.csv File: `data.csv' Size: 2271197563 Blocks: 4440280 IO Block: 4096 regular file Device: 342h/834d Inode: 9994308 Links: 1 Access: (0644/-rw-r--r--) Uid: ( 500/ rpeng) Gid: ( 500/ rpeng) Access:

.../gcc/powerpc-ibm-aix5.3.0.0/4.7.4/include-fixed/sys/types.h" 3 4 typedef int time_t; @@ -258,9 +251,9 @@ - typedef long long off_t; + typedef long off_t; @@ -2785,8 +2778,8 @@ extern char *tmpnam(char *); extern int fclose(FILE *); extern int fflush(FILE *); - extern FILE * fopen64(const char *restrict, const char *restrict); - extern FILE * freopen64(const char *restrict, const char *restrict, FILE *restrict); + extern FILE * fopen(const char *restrict, const char *restrict); + extern FILE * freopen(const char *restrict, const char *restrict, FILE *restrict); extern voi...

...ecking for setuidx... no > checking for setgroups... no > checking for sysconf... no > checking for mktime... no > checking for rename... no > checking for ftruncate... no > checking for stat64... no > checking for fstat64... no > checking for lstat64... no > checking for fopen64... no > checking for atexit... no > checking for grantpt... no > checking for dup2... no > checking for lseek64... no > checking for ftruncate64... no > checking for readdir64... no > checking for fseek64... no > checking for fseeko64... no > checking for ftell64... no &g...

.... no checking for getgrnam... yes checking for pathconf... yes checking for setuidx... no checking for setgroups... yes checking for mktime... yes checking for rename... yes checking for ftruncate... yes checking for stat64... yes checking for fstat64... yes checking for lstat64... yes checking for fopen64... yes checking for atexit... yes checking for grantpt... yes checking for dup2... yes checking for lseek64... yes checking for ftruncate64... yes checking for fseek64... no checking for ftell64... no checking for setluid... no checking for yp_get_default_domain... yes checking for getpwanam... no...

...priv... no checking for setgidx... no checking for setuidx... no checking for setgroups... yes checking for sysconf... yes checking for mktime... yes checking for rename... yes checking for ftruncate... yes checking for stat64... no checking for fstat64... no checking for lstat64... no checking for fopen64... no checking for atexit... yes checking for grantpt... yes checking for dup2... yes checking for lseek64... no checking for ftruncate64... no checking for readdir64... no checking for fseek64... no checking for fseeko64... no checking for ftell64... no checking for ftello64... no checking for set...

...r setpriv... no checking for setgidx... no checking for setuidx... no checking for setgroups... no checking for sysconf... no checking for mktime... no checking for rename... no checking for ftruncate... no checking for stat64... no checking for fstat64... no checking for lstat64... no checking for fopen64... no checking for atexit... no checking for grantpt... no checking for dup2... no checking for lseek64... no checking for ftruncate64... no checking for readdir64... no checking for fseek64... no checking for fseeko64... no checking for ftell64... no checking for ftello64... no checking for setlui...

...r setpriv... no checking for setgidx... no checking for setuidx... no checking for setgroups... no checking for sysconf... no checking for mktime... no checking for rename... no checking for ftruncate... no checking for stat64... no checking for fstat64... no checking for lstat64... no checking for fopen64... no checking for atexit... no checking for grantpt... no checking for dup2... no checking for lseek64... no checking for ftruncate64... no checking for readdir64... no checking for fseek64... no checking for fseeko64... no checking for ftell64... no checking for ftello64... no checking for setlui...

...or setgroups configure:5644: checking for sysconf configure:5644: checking for mktime configure:5644: checking for rename configure:5644: checking for ftruncate configure:5644: checking for stat64 configure:5644: checking for fstat64 configure:5699: checking for lstat64 configure:5699: checking for fopen64 configure:5699: checking for atexit configure:5699: checking for grantpt configure:5699: checking for dup2 configure:5699: checking for lseek64 configure:5699: checking for ftruncate64 configure:5699: checking for readdir64 configure:5754: checking for fseek64 configure:5754: checking for fseeko64...

...v... no checking for setgidx... no checking for setuidx... no checking for setgroups... yes checking for sysconf... yes checking for mktime... yes checking for rename... yes checking for ftruncate... yes checking for stat64... yes checking for fstat64... yes checking for lstat64... yes checking for fopen64... yes checking for atexit... yes checking for grantpt... yes checking for dup2... yes checking for lseek64... yes checking for ftruncate64... yes checking for readdir64... no checking for fseek64... no checking for fseeko64... yes checking for ftell64... no checking for ftello64... yes checking fo...

On 2015-12-17 19:30, peter dalgaard wrote: > Presumably the file in question is one of > > Peter-Dalgaards-MacBook-Air:BUILD pd$ grep -r "^Package: tools" * > library/tools/DESCRIPTION:Package: tools > src/library/tools/DESCRIPTION:Package: tools > > so the first thing I'd do is to have a good look at those files and see if they got somehow corrupted. > >

Hello, I am running HP-UX 11 with Samba 2.2.5 binaries for HPUX and I keep getting the error that Samba can't find the unicode_map.xxx file. Well, I notice that all I have in /usr/local/samba/lib/codepages is codepage type files, not unicode. Why do the binaries not include a compiled make_unicodemap? I did download the source and found the .c file for the command. When I try to run

...g for setgroups... (cached) yes checking for sysconf... (cached) yes checking for mktime... (cached) yes checking for rename... (cached) yes checking for ftruncate... (cached) yes checking for stat64... (cached) no checking for fstat64... (cached) no checking for lstat64... (cached) no checking for fopen64... (cached) no checking for atexit... (cached) yes checking for grantpt... (cached) yes checking for dup2... (cached) yes checking for lseek64... (cached) no checking for ftruncate64... (cached) no checking for readdir64... (cached) no checking for fseek64... (cached) no checking for fseeko64... (c...