Displaying 20 results from an estimated 1000 matches similar to: "scary messages from autoconf"
2009 Mar 12
0
Re: program wont run problem with nethasp protection
if anyone ever serches here for using responsa in linux then you should know that:
it works!
for more info look here:
http://www.whatsup.org.il/index.php?name=PNphpBB2&file=viewtopic&t=31072&start=30&postdays=0&postorder=asc&highlight=
2003 Aug 19
0
Re: Open source IP phone, maybe?
I concur with Jose. The Atmel AVR series packs a lot of bang for the buck. They
also come in a 3.3v low power version for use in battery powered systems.
Gene
-----Original Message-----
From: Leo Ann Boon [mailto:leo@innovax.com.sg]
Sent: Tuesday, August 19, 2003 7:21 PM
To: asterisk-users@lists.digium.com
Subject: Re: [Asterisk-Users] Re: Open source IP phone, maybe?
Ubicom's Scenix IP2K.
2003 Aug 19
2
Re: Open source IP phone, maybe?
Hi!
I think it is a great idea.
The DS80C400 needs external memory, and/or flash.  It have the Ethernet 
integrated, but it is really slow (it is 8051 architecture), and yes, I 
know it can go up ti 75Mhz, but only gives 18MIPS max.  I would use 
ATmega128 from atmel (16MIPS at only 16Mhz), take a look at: 
http://www.ethernut.de (project using mega128 with Ethernet, includes 
schematics).
It
2011 Jan 05
0
[LLVMdev] Building LLVM-GCC on Linux/PowerPC failed
Hi, folks
  I am "stll" trying to build LLVM-GCC 4.2 on a Linux/PS3 machine, which
has a 64-bit OS.
  Here is my system information and configuration options:
-----------------------------------------------------------------
$ uname -a
Linux ps3 2.6.32-rc2-00995-g96ebbe6-dirty #2 SMP Fri Oct 2 15:12:28 CST
2009 ppc64 Cell Broadband Engine, altivec supported GNU/Linux
$ gcc --version
2009 Apr 03
2
[LLVMdev] Trouble Building llvm-gcc-4.2
I'm still trying to debug the validator buildbot. 
I'm getting this error when building some variants of llvm-gcc-4.2:
/bin/sh ../../src/gcc/mkconfig.sh bconfig.h
gcc -c   -g -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes 
-Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros 
-Wno-overlength-strings -Wold-style-definition -Wmissing-format-attribute 
-fno-common  
2009 Apr 03
0
[LLVMdev] Trouble Building llvm-gcc-4.2
On 2009-04-03 18:39, David Greene wrote:
> I'm still trying to debug the validator buildbot. 
>
> I'm getting this error when building some variants of llvm-gcc-4.2:
>
> /bin/sh ../../src/gcc/mkconfig.sh bconfig.h
> gcc -c   -g -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes 
> -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros 
>
2010 Sep 26
3
[LLVMdev] Issue compiling llvm-gcc frontend on sparc
Hi all,
I have successfully built LLVM itself, as all the tools (llc et al) are working fine. I built the latest release version (2.7). I have been trying to build the llvm-gcc frontend on a sparc machine. I encountered the following issues :
1) During configuration, the default assembler (installed at /usr/ccs/bin) is chosen to be used, but I want to use the GNU assembler (installed at
2005 Jun 13
2
Can't maintain a connection to the Server 2003 ADS on a subdomain
Hello to every Samba expert out there,
We've been having a hard time figuring out a particular problem with Samba.
After joining the Server 2003 ADS, which is on a different subnet - just
going through a router, the membership would drop all of a sudden.
Everything works great when the Samba server is on the same subnet as the
Server 2003 ADS. I have posted some details on forums, here is a
2011 Jul 08
1
[LLVMdev] as: unrecognized option '-meabi=4'
Hi
In my install directory under bin , I had
llvm-c++,llvm-g++,llvm-gconv
I tested one sample program
#llvm-c++ addu.c -o addu-arm
as: unrecognized option '-meabi=4'
How do i solve this issue
Thanks
Yuvi R
On Fri, Jul 8, 2011 at 9:21 AM, raj raja <yuvaraj.addu at gmail.com> wrote:
> Thanks for your reply
>
> I got error
>
> */bin/sh: build/genmodes: not
2009 May 04
0
[LLVMdev] llvm-gcc-4.2 Build Problems
Still working on the validator buildbot as I can.
Now I'm tackling what appears to be a configure problem for llvm-gcc-4.2.
Here's the configure log:
../src/configure 
--prefix=/ptmp/dag/buildbot/slaves/llvm-validate/llvm-validate-release-kentsfield-linux/build/install
--program-prefix=llvm-
2011 Jul 08
0
[LLVMdev] as: unrecognized option '-meabi=4'
Hi
Thanks your info
On 7/8/11, James Molloy <james.molloy at arm.com> wrote:
> Hi,
>
>
>
> It sounds like you're using an incorrect version of binutils (one that
> targets x86 instead of ARM, for example).
>
>
>
> You require an ARM-targetting assembler and linker.
>
>
>
> James
>
>
>
> From: llvmdev-bounces at cs.uiuc.edu
2010 Dec 30
8
[LLVMdev] Building LLVM-GCC on Linux/PowerPC failed
Hi, folks
    I am trying to build LLVM-GCC 4.2 on a Linux/PowerPC machine.
Actually, the PowerPC is a PS3. The source was downloaded from
http://llvm.org/releases/2.8/llvm-gcc-4.2-2.8.source.tgz
  Here is my system information and configuration options:
----------------------------------------------------------------------
$ uname -a
Linux ps3 2.6.32-rc2-00995-g96ebbe6-dirty #2 SMP Fri Oct 2
2008 Sep 09
1
Genmod in SAS vs. glm in R
Hello,
I have different results from these two softwares for a simple binomial GLM
problem. 
>From Genmod in SAS: LogLikelihood=-4.75, coeff(intercept)=-3.59,
coeff(x)=0.95
>From glm in R: LogLikelihood=-0.94, coeff(intercept)=-3.99, coeff(x)=1.36
Is there anyone tell me what I did wrong?
Here are the code and results,
1) SAS Genmod:
% r: # of failure
% k: size of a risk set
data
2009 Aug 19
0
zfs+nfs: scary nfs log entries?
I have a zfs dataset that I use for network home directories.  The box is running 2008.11 with the auto-snapshot service enabled.  To help debug some mysterious file deletion issues, I''ve enabled nfs logging (all my clients are NFSv3 Linux boxes).
I keep seeing lines like this in the nfslog:
<br>
<br>
<pre>
Wed Aug 19 10:20:48 2009 0 host.name.domain.com 1168
2009 Jul 08
1
scary fill_share_mode_lock failed message
I'm still working on figuring out why some accesses to profile data  
are failing.
We are running 3.3.2-0.33.fc11 (the latest release for FC11).
I saw this in the log file
   stat_cache_lookup: lookup succeeded for name [USER/STARTMENU] ->  
[user/StartMenu]
[2009/07/08 17:39:59,  3] locking/locking.c:fetch_share_mode_unlocked(857)
   fill_share_mode_lock failed
I saw Volker had a fix
2002 Aug 06
2
Fwd: this is scary
i got this link from another list.
does this affect applications running in wine?
http://security.tombom.co.uk/shatter.html
-- 
Oh, I have slipped the surly bonds of DOS,
and danced the skies on Linux silvered wings.
http://pfrostie.freeservers.com/cad-tastrafy/
http://www.freelists.org/list/cad-linux
2018 May 30
0
2.3.1 Replication is throwing scary errors
Hi,
Checking in - this is still an issue with 2.3-master as of today 
(2.3.devel (3a6537d59)).
I haven't been able to narrow the problem down to a specific commit. 
The best I have been able to get to is that this commit is relatively 
good (not perfect but good enough):
d9a1a7cbec19f4c6a47add47688351f8c3a0e372 (from Feb 19, 2018)
whereas this commit:
2018 May 31
0
2.3.1 Replication is throwing scary errors
> On 31 May 2018, at 17:52, Michael Grimm <trashcan at ellael.org> wrote:
> 
> Reuben Farrelly <reuben-dovecot at reub.net> wrote:
> 
>> Checking in - this is still an issue with 2.3-master as of today (2.3.devel (3a6537d59)).
> 
> That doesn't sound good, because I did hope that someone has been working on this issue ...
> 
>> I haven't been
2018 Jun 01
0
2.3.1 Replication is throwing scary errors
On 1/06/2018 2:47 AM, Michael Grimm wrote:
> On 31. May 2018, at 18:09, Remko Lodder <remko at FreeBSD.org> wrote:
>>> On 31 May 2018, at 17:52, Michael Grimm <trashcan at ellael.org> wrote:
>>> I would love to get some feedback from the developers regarding:
>>>
>>> #) are commercial customers of yours running 2.3 master-master replication
2018 Jun 06
0
2.3.1 Replication is throwing scary errors
Hi Timo,
Yes this seems to work fine so far. I?ll ask the people to add it to the current FreeBSD version..
Cheers
Remko
> On 6 Jun 2018, at 19:34, Timo Sirainen <tss at iki.fi> wrote:
> 
> Should be fixed by https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336 <https://github.com/dovecot/core/commit/a952e178943a5944255cb7c053d970f8e6d49336>
>