search for: linux6

It's undocumented FAQ, if you are using RHEL5 (or clone). - install gcc44-c++ - Build with CC=gcc44 CXX=g++44 - You may need "CC=clang -std=gnu89" to use clang with its glibc. Have fun! ps. AFAIK, clang can be built more easily on centos6. ...Takumi 2012/7/11 Sitvanit Ruah <RUAH at il.ibm.com>: > > Hello all, > I am new to this mailing list so I hope this is

...t/lib/asan/asan_posix.cc the line is preceded by the comment // Should not add dependency on libstdc++ Below are the gcc44 directories installed on the machine. Do you know what else is needed in order to resolve the problem? Thanks, Sitvanit /usr/bin/gcc44 /usr/bin/gcov44 /usr/bin/i386-redhat-linux6E-gcc44 /usr/lib/gcc /usr/lib/gcc/i386-redhat-linux6E /usr/lib/gcc/i386-redhat-linux6E/4.4.6 /usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtbegin.o /usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtbeginS.o /usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtbeginT.o /usr/lib/gcc/i386-redhat-linux6E/4.4.6/crtend.o /usr/li...

Hello all, I am new to this mailing list so I hope this is the right place to post the following question. We are considering using Clang front end for our tool. I tried to compile LLVM (using configure followed by make from the llvm top directory) on LINUX X86 with gcc 4.1.2. I got several compilation error messages of the form /usr/lib/gcc/i386-redhat-linux/4.1.2/../../../../include/c+

...tvanit/LLVM/build/tools' make: *** [all] Error 1 ======================================================== The shell I am using is tcsh (it doesn't recognize the command "export") The outputs to the gcc44 -v, g++44 -c: build> gcc44 -v Using built-in specs. Target: i386-redhat-linux6E Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exception...

...l] Error 1 > ======================================================== > > The shell I am using is tcsh (it doesn't recognize the command "export") > > The outputs to the gcc44 -v, g++44 -c: > > build> gcc44 -v > Using built-in specs. > Target: i386-redhat-linux6E > Configured with: ../configure --prefix=/usr --mandir=/usr/share/man > --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla > --enable-bootstrap --enable-shared --enable-threads=posix > --enable-checking=release --with-system-zlib --enable-__cxa_atexit > --di...

...;/usr/lib/x86_64-unknown-linux-gnu/gcc/x86_64-unknown-linux-gnu" "/usr/lib/x86_64-unknown-linux-gnu" "/usr/lib/gcc/x86_64-pc-linux-gnu" "/usr/lib/x86_64-pc-linux-gnu/gcc/x86_64-pc-linux-gnu" "/usr/lib/x86_64-pc-linux-gnu" "/usr/lib/gcc/x86_64-redhat-linux6E" "/usr/lib/x86_64-redhat-linux6E/gcc/x86_64-redhat-linux6E" "/usr/lib/x86_64-redhat-linux6E" "/usr/lib/gcc/x86_64-redhat-linux" "/usr/lib/x86_64-redhat-linux/gcc/x86_64-redhat-linux" "/usr/lib/x86_64-redhat-linux" "/usr/lib/gcc/x86_64-sus...

PS: Do you actually have gcc-4.4 installed and in your path? What do the commands gcc44 -v and g++44 -v output? On 15/07/12 10:59, Duncan Sands wrote: > Hi Sitvanit, > >> I tried >> >> CC=gcc44 CXX=g++44 ../llvm/configure >> >> and got >> >> CC=gcc44: Command not found >> >> So the syntax is indeed as wriiten in the help. >

Hi Sitvanit, > I tried > > CC=gcc44 CXX=g++44 ../llvm/configure > > and got > > CC=gcc44: Command not found > > So the syntax is indeed as wriiten in the help. actually, no, this just means that you are using a shell that doesn't support this syntax. What shell are you using? Try export CC=gcc44 export CXX=g++44 ../llvm/configure Ciao, Duncan. >

...we can reduce a triple to while guaranteeing compatibility. The concept is best explained by an example. All of the following triples reduce to the base triple of "x86_64-linux-gnu": x86_64-linux-gnu x86_64-pc-linux-gnu x86_64-unknown-linux-gnu x86_64-redhat-linux x86_64-redhat-linux6E ... A different ABI could be expressed much like ARM's is with the last element: "*-gnueabi". This would *not* reduce to the triple ending in '-gnu'. Due to the adhoc and poorly spec'ed nature of existing triples, this will largely be a fixed mapping much like already...

Hi  Samba team We  use  samba  on  redhat  linux6  and use  Samba  as  file  server.  We  connect  it  with  ms dos  client , and use application  develope on clipper  5.3D ( Application open about 120 file handles) . We meet  error  dos 55  network error  ,but  if  these application  running  on  ms  dos  promt  window 95, it didn't  have  th...

...aranteeing compatibility. The concept is best explained by an > example. All of the following triples reduce to the base triple of > "x86_64-linux-gnu": >   x86_64-linux-gnu >   x86_64-pc-linux-gnu >   x86_64-unknown-linux-gnu >   x86_64-redhat-linux >   x86_64-redhat-linux6E >   ... > A different ABI could be expressed much like ARM's is with the last element: > "*-gnueabi". This would *not* reduce to the triple ending in '-gnu'. Due to > the adhoc and poorly spec'ed nature of existing triples, this will largely > be a fixed ma...

...pt is best explained by an > > example. All of the following triples reduce to the base triple of > > "x86_64-linux-gnu": > > x86_64-linux-gnu > > x86_64-pc-linux-gnu > > x86_64-unknown-linux-gnu > > x86_64-redhat-linux > > x86_64-redhat-linux6E > > ... > > A different ABI could be expressed much like ARM's is with the last > element: > > "*-gnueabi". This would *not* reduce to the triple ending in '-gnu'. Due > to > > the adhoc and poorly spec'ed nature of existing triples, this w...

...aranteeing compatibility. The concept is best explained by an > example. All of the following triples reduce to the base triple of > "x86_64-linux-gnu": > x86_64-linux-gnu > x86_64-pc-linux-gnu > x86_64-unknown-linux-gnu > x86_64-redhat-linux > x86_64-redhat-linux6E > ... > > A different ABI could be expressed much like ARM's is with the last > element: "*-gnueabi". This would *not* reduce to the triple ending in > '-gnu'. Due to the adhoc and poorly spec'ed nature of existing triples, > this will largely be a fix...

Dear folks. I am using smbclient 4.2.10 version (the one packaged for OEL 6, samba4-client-4.2.10-15.el6.x86_64), and observing a weird behaviour of the tool. I've got a Linux local directorio, say /tmp/eraseme, with a couple of subdirectories in it, say a and b, each one containing a dummy file, say a/AM.xls and b/AT.xls If I run: smbclient -d 30 -l /var/log/samba -m SMB3 -W