search for: pkgversions

Hi Everyone. Asterisk is one of those applications that need to be built from cvs on a regular basis to keep up with the changes. I have always used package management tools like apt. How does everyone manage their Asterisk servers? Geoff

Hi, I am trying to cross compile LLVM-3.0 for Arm target i.e. I would like to run the LLVM tools on ARM platform and generate the code for the ARM platform. I configured the build with ../src/configure --build=i686-pc-linux-gnu --host=arm-linux-gnueabi --target=arm-linux-gnueabi --enable-optimized=no --prefix=/home/user/Acads/Compiler/LLVM/llvm-3.0/bin --with-as=/usr/bin/arm-linux-gnueabi-as

Hi. Ive used git for some time to download an update wine sources. However, Ive notices a couple of things i dont understand quite much. My general procedure to download sources and compile is this: git clone git://source.winehq.org/git/wine.git ~/wine-git cd ~/wine-git ./configure --prefix=/usr make sudo checkinstall --fstrans=no --pkgversion=1.1.12 Here I've noticed that I have to

On Sat, Feb 27, 2016 at 1:41 PM, Sanjoy Das <sanjoy at playingwithpointers.com> wrote: > Just as a reality check, I wrote up a demonstration where one link > order causes a SIGFPE and another doesn't (and the program is well > defined, as far as I can tell). All TUs are compiled with -O3. This is also > an instance where we don't actually speculate an inline function,

On Wed, Jul 18, 2012 at 4:15 PM, Renato Golin <rengolin at systemcall.org> wrote: > On 18 July 2012 14:57, salvatore benedetto > <salvatore.benedetto at gmail.com> wrote: >> $ clang -march=armv7-m -mfloat-abi=soft -ccc-host-triple >> armv7m-none-gnueabi testReference.cpp -c >> fatal error: error in backend: CPU: 'cortex-m3' does not support ARM >>

Hi Eric, here is my -emit-llvm -S -v output: Using built-in specs. COLLECT_GCC=gcc-4.5 COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.5.1/lto-wrapper Target: i686-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.5.1-7ubuntu2' --with-bugurl=file:///usr/share/doc/gcc-4.5/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr

I'm attempting to build a native build of clang from the 3.2 source distribution tarballs, but I ran into this build error that's got me really puzzled. My platform is Linux - 32-bit Ubuntu (12.04) running on a PC. Here's the (abbreviated) output from make: *************************************** ... make[3]: Entering directory

On 18 July 2012 14:57, salvatore benedetto <salvatore.benedetto at gmail.com> wrote: > $ clang -march=armv7-m -mfloat-abi=soft -ccc-host-triple > armv7m-none-gnueabi testReference.cpp -c > fatal error: error in backend: CPU: 'cortex-m3' does not support ARM > mode execution! Ah, yes! Try: $ clang -ccc-host-triple thumbv7m-none-gnueabi testReference.cpp -c Cross

Dear list-members, I have observed quite a strange problem with the date package. You will find below what I get on my machine (Ubuntu). I have been able to reproduce the error on Red Hat too. But it seems not to happen on Windows (and on some other Linux distros?). > require(date) Loading required package: date > sessionInfo() R version 2.15.2 (2012-10-26) Platform: x86_64-pc-linux-gnu

On Sun, Jul 3, 2011 at 11:32 PM, Karel Gardas <karel.gardas at centrum.cz> wrote: > Hello, > > I asked here for kind of reference GCC version which LLVM development > team is using for *native* testing on ARM hardware. (no cross > compilation!) last week or so. I've been curious myself how the > situation looks and so I tested LLVM 2.9 as a reference point and LLVM >

Looks like something wonky with DragonEgg. Duncan? -eric On Mar 21, 2011, at 7:05 PM, stackunderflow wrote: > > Hi Eric, > > here is my -emit-llvm -S -v output: > > Using built-in specs. > COLLECT_GCC=gcc-4.5 > COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.5.1/lto-wrapper > Target: i686-linux-gnu > Configured with: ../src/configure -v

Hi all, I'm trying to build clang on Ubuntu 17.10 - the build succeeds, but testing fails: ~/wk/LLVM/build_release$ svn info ../llvm/ Path: /home/csabaraduly/wk/LLVM/llvm Working Copy Root Path: /home/csabaraduly/wk/LLVM/llvm URL: https://llvm.org/svn/llvm-project/llvm/trunk Relative URL: ^/llvm/trunk Repository Root: https://llvm.org/svn/llvm-project Repository UUID:

Hi Michael, you don't need compiler-rt to use clang. If you don't need it, I suggest you don't bother building it. Ciao, Duncan. On 21/02/13 01:15, Michael Young wrote: > > I'm attempting to build a native build of clang from the 3.2 source > distribution tarballs, but I ran into this build error that's got me > really puzzled. My platform is Linux - 32-bit

On Tue, Nov 28, 2017 at 12:16 AM, Kostya Serebryany <kcc at google.com> wrote: > +dvyukov > > On Mon, Nov 27, 2017 at 4:56 AM, Csaba Raduly via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> >> Hi all, >> >> I'm trying to build clang on Ubuntu 17.10 - the build succeeds, but >> testing fails: >> >> ~/wk/LLVM/build_release$

On Wed, Jul 18, 2012 at 4:31 PM, Renato Golin <rengolin at systemcall.org> wrote: > On 18 July 2012 15:24, salvatore benedetto > <salvatore.benedetto at gmail.com> wrote: >> I'm not sure how to interpret the above output, but I don't understand >> why if say -triple armv4t-none--gnueabi . > > Ok, we're getting there... ;) Glad you are confident.

On 18 July 2012 15:24, salvatore benedetto <salvatore.benedetto at gmail.com> wrote: > I'm not sure how to interpret the above output, but I don't understand > why if say -triple armv4t-none--gnueabi . Ok, we're getting there... ;) I think these errors are due to Clang not finding the libraries/includes/etc for the target you're building. If you have

Nice repro. It looks well-defined to me too. Is there a PR open yet? > On 2016-Feb-29, at 08:21, Sanjoy Das via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On Sat, Feb 27, 2016 at 1:41 PM, Sanjoy Das > <sanjoy at playingwithpointers.com> wrote: >> Just as a reality check, I wrote up a demonstration where one link >> order causes a SIGFPE and another

I'd like to install NagiosQL on CentOS, but I don't see a yum package for it, so I'm going to download the source code. If I download it, where in CentOS's file system (i.e. in which directory) is the best place to untar, compile, and run it? (Sorry, I've been spoiled by packages!)

Hi, It would be great if the spec file could be updated to remove the dependency on python-ctypes for sles 11 since this seems to be included as part of the python package. Also, there are lot of pragma warnings. It doesn't look like those pragma's work with the gcc on suse 11p2: ../../../../rpc/xdr/src/cli1-xdr.h:25: warning: unknown option after '#pragma GCC diagnostic' kind

Hi Eric, > Looks like something wonky with DragonEgg. you need to use -fplugin-arg-dragonegg-emit-ir or -flto with dragonegg, not -emit-llvm. Also, you currently have to use -S (getting human readable IR) rather than -c because with -c gcc will run cc1 with -S (getting human readable IR) then pass the result to the system assembler which of course barfs. This is documented on the web-page