similar to: Static linking

Hi all, I just upgraded a production server to asterisk 1.4.25, compiling with the following: [*] 1. DONT_OPTIMIZE [*] 2. DEBUG_CHANNEL_LOCKS [*] 3. DEBUG_THREADS [*] 4. DEBUG_FD_LEAKS [ ] 5. LOW_MEMORY [*] 6.

gcc 3.4.x builds LLVM incorrectly on x86_64. gcc 4.0 will get you much farther, but the llvm-test regression tests still have massive problems. Zhongxing Xu wrote: > The machine is a Dell workstation with xeon processors. The OS is RHEL > 4 AS x86_64 > gcc version is 3.4.6 > > I checked out the llvm-gcc from svn, configured with > ../llvm-gcc/configure

Chris Lattner wrote: > On Thu, 2 Mar 2006, Vladimir Prus wrote: >>>> The instructions seem to have one path wrong. It says to get: >>> >>> I'll put together a tarball today. That will be easier than dealing >>> with a patch, and it will include a bunch of bugfixes since the previous >>> email. >> Further into process, I get this error:

The machine is a Dell workstation with xeon processors. The OS is RHEL 4 AS x86_64 gcc version is 3.4.6 I checked out the llvm-gcc from svn, configured with ../llvm-gcc/configure --prefix=$HOME/llvm-gcc-install --enable-llvm=$HOME/llvmobj/ --enable-languages=c,c++ --enable-checking --disable-shared --disable-multilib and get the following error message: make

Already have concerning gcc 3.4: http://llvm.org/bugs/show_bug.cgi?id=1056 As for llvm-test issues, quite frankly I don't know how well they're expected to work on x86_64. No one has jumped in and said they run fine on their x86_64 system. Maybe they're code generator bugs, or maybe they're portability issues for FreeBSD (though I never saw such massive problems with 32-bit

On Jan 9, 2007, at 9:48 PM, Jeff Cohen wrote: > gcc 3.4.x builds LLVM incorrectly on x86_64. > > gcc 4.0 will get you much farther, but the llvm-test regression tests > still have massive problems. Please file bug reports on these. Thanks! Evan > > Zhongxing Xu wrote: >> The machine is a Dell workstation with xeon processors. The OS is >> RHEL >> 4 AS

Is there any flash based players out that can be embedded into a webpage and stream a icecast feed? -=-=-=-=-=-=-=Ottawa Valley Weather-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Weather @ 5:50pm - Temp: 31.1?C - Humidity 23% - Wind: W @ 0 km/h Baro: 1001kPa Falling - Vis: 24km - Sky: Few Clouds - Weather: --- Hourly Rain: 0.00mm - Daily Rain: 0.00mm - Total Rain(May 28th): 1.00mm =-=-=-=

hello, James FitzGibbon: thank you for your help. i am very new to arm-linux and embedded linux. i think what you said is right. i am not very sure the steps i taken are correct. i post it here and please give me some help. it might be help other arm-linux users too. i installed all necessary libraries in my linux. if i just install asterisk under my linux. there is no problem. but when i

Could you provide a list of all tests failing for you? You can just grep the output from make for 'FAILED!'. I've fixed 5 of them so far... 275 to go... Chandler Carruth wrote: > I do all my LLVM stuff on x86_64 without trouble... I have a nightly > tester up, and its only getting a few regressions currently, and I > think some of those have to do with the radical

I do all my LLVM stuff on x86_64 without trouble... I have a nightly tester up, and its only getting a few regressions currently, and I think some of those have to do with the radical changes going on in LLVM-land currently, and others with no one having done support for x86-64 in debugging output. (this is at least most of what I've seen, ymmv). Also, for the record, I have found both gcc

2016-09-06 17:48 GMT+02:00 Tzafrir Cohen <tzafrir.cohen at xorcom.com>: > On Tue, Sep 06, 2016 at 06:37:52AM -0600, George Joseph wrote: > > On Tue, Sep 6, 2016 at 1:55 AM, Olivier <oza.4h07 at gmail.com> wrote: > > > > Where should core file be created when Asterisk is run as a daemon by > > > asterisk user and group ? > > > Is there a setting I

> > ./configure in the llvm package will work on my amd64 machine > with this command line: > > ./configure --prefix=$HOME --enable-optimized \ > --build=i686-pc-linux-gnu CC=gcc-4.2 CXX=g++-4.2 > > Note that the CC and CXX flags are set on the command line, not as > environment variables - trying to submit them via the environment got me > all kinds of

Just a quick heads-up: The ./configure in the llvm 2.2 package will work on my amd64 machine with this command line: ./configure --prefix=$HOME --enable-optimized \ --build=i686-pc-linux-gnu CC=gcc-4.2 CXX=g++-4.2 Note that the CC and CXX flags are set on the command line, not as environment variables - trying to submit them via the environment got me all kinds of breakage. Also not that this

> Okay, I took a closer look at your output. > > I was correct in that gccas is attempting to assemble a native PPC > assembly language file. However, this appears to be happening because > the assembly file is generated by the GCC Makefiles for libgcc2 (in > llvm-gcc/gcc/config/rs6000/t-ppccomm, I think). > > The first thing I would try is Marco's suggestion: add

Server is PII-350MHz/256 MB RAM, hardware mirrored high speed SCSI disks. Installed is SuSE 8.2 with Samba 2.2.8a RPM, XFS filesystems and LPRng as printservices. Server acts as PDC and WINS server. Clients are W2K SP2 (a few with SP3). There are +/- 100 clients. We see a server that is 100% busy and we see during a long time a very high CPU load (60- 95%) related to one W2K client. When

Steps to reproduce: - Enable CLucene FTS in Dovecot; - Open mailbox with MUA; - Search for message with any text; - IMAP session crash. OS: Gentoo Base System release 2.6 Version: FTS: dev-cpp/clucene-2.3.3.4-r6 IMAP: net-mail/dovecot-2.3.2.1 LIBC: sys-libs/musl-1.1.21 Dovecot FTS config: plugin { fts = lucene fts_lucene = whitespace_chars=@. normalize no_snowball fts_autoindex=yes

(Apologies if this appears twice, it seems to not have made it into the list. I added an update for SVN trunk.) Just a quick heads-up for 2.2 and SVN trunk: ./configure in the llvm package will work on my amd64 machine with this command line: ./configure --prefix=$HOME --enable-optimized \ --build=i686-pc-linux-gnu CC=gcc-4.2 CXX=g++-4.2 Note that the CC and CXX flags are set on the command

I think were getting closer: I did: - I edited /etc/default/asterisk to include : AST_USER="root" AST_GROUP="root" # systemctl daemon-reload # systemctl start asterisk # ps aux | grep asterisk root 3602 7.1 2.5 60332 26012 ? Ssl 16:00 0:03 /usr/sbin/asterisk -U root -G root -g # rasterisk # pkill -SEGV asterisk Then console showed: Segmentation error (core

Full_Name: Jean-Pierre Müller Version: 162 OS: Mac OS (carbon) Submission from: (NULL) (130.223.101.43) Encodings valid only in rwading files? The following give identical output files. "ascii" <- c( "\040","\041","\042","\043","\044","\045","\046","\047", # 040-047

http://bugs.freedesktop.org/show_bug.cgi?id=24555 Summary: X server crash Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy: dwmw2 at