On Fri, Sep 24, 2010 at 12:42:56PM +0200, Stig Bj?rlykke wrote:
> On Fri, Sep 24, 2010 at 12:33 PM, Joerg Mayer wrote:
> > That's the type of fix I was hoping for when I rejected the previous one!
> > Nicely spotted.
>
> I'm still having problems with --as-needed when building with Xcode,
> but n
On Fri, Sep 24, 2010 at 3:55 PM, Joerg Mayer wrote:
> Stig: you mentioned problems with XCODE?
Yes. CMake determines to use "-Wl,--as-needed", but the linker does
not like this option.
Any idea what to look for?
--
Stig Bjørlykke
On Sep 24, 2010, at 1:55 PM, john s wolter wrote:
> Gentlemen, is this discussion related to "Virtual WireShark Appliance". If
> not please move it to a new thread.
At minimum, if you're responding to one of the problems-with-CMake messages:
1) don't send them on to John Wolter
and
Gentlemen, is this discussion related to "Virtual WireShark Appliance". If
not please move it to a new thread.
2010/9/24 Stig Bjørlykke
> On Fri, Sep 24, 2010 at 3:55 PM, Joerg Mayer wrote:
> >Stig: you mentioned problems with XCODE?
>
> Yes. CMake determines to use "-Wl,--as-needed", bu
Le 24 sept. 2010 à 15:55, Joerg Mayer a écrit :
> Btw, can you please provide me with a log what and how things fail when
> you build with "set(LINK_MODE_MODULE MODULE)" instead of SHARED?
This is the log with LINK_MODE_MODULE set to MODULE :
Linking C shared module ../../lib/asn1.so
cd /Users/l
On Fri, Sep 24, 2010 at 12:47:27PM +0200, H Sivank wrote:
> > I have added a fix in revision 34233, does this work for you?
> >
>
> Work for me :) Thanks for the fix.
Btw, can you please provide me with a log what and how things fail when
you build with "set(LINK_MODE_MODULE MODULE)" instead of
2010/9/24 Stig Bjørlykke
> On Fri, Sep 24, 2010 at 11:28 AM, H Sivank wrote:
> > Hello,
> > My previous post was not clear.
> > It was a *standard* configure log, just to point that the linker does not
> > support "--as-needed".
> > if i do a cmake configure it will fail on big endian test :
>
>
On Fri, Sep 24, 2010 at 12:33 PM, Joerg Mayer wrote:
> That's the type of fix I was hoping for when I rejected the previous one!
> Nicely spotted.
I'm still having problems with --as-needed when building with Xcode,
but not when building with Makefiles.
CMake reports --as-needed is OK when buildi
On Fri, Sep 24, 2010 at 12:25:07PM +0200, Stig Bj?rlykke wrote:
> On Fri, Sep 24, 2010 at 11:28 AM, H Sivank wrote:
> > My previous post was not clear.
> > It was a *standard* configure log, just to point that the linker does not
> > support "--as-needed".
> > if i do a cmake configure it will fai
On Fri, Sep 24, 2010 at 11:28 AM, H Sivank wrote:
> Hello,
> My previous post was not clear.
> It was a *standard* configure log, just to point that the linker does not
> support "--as-needed".
> if i do a cmake configure it will fail on big endian test :
I have added a fix in revision 34233, doe
Hello,
My previous post was not clear.
It was a *standard* configure log, just to point that the linker does not
support "--as-needed".
if i do a cmake configure it will fail on big endian test :
"
CMake Error at /opt/local/share/cmake-2.8/Modules/TestBigEndian.cmake:44
(MESSAGE):
no suitable
On Sep 23, 2010, at 2:45 PM, john s wolter wrote:
> I'm not sure what 'push' means in this context.
"Push", in this context, means "a technology that was, at one point, hyped, but
didn't take over the world in the fashion that the hype predicted":
http://en.wikipedia.org/wiki/PointCast
Guy,
I hope I did not sound like I was saying they were against VA's.
I.e., if the virtual machine does not provide mechanisms by which a program
> running on one virtual machine can monitor on-the-wire traffic to another
> virtual machine, or traffic within another virtual machine, or between tw
On Sep 20, 2010, at 1:44 PM, john s wolter wrote:
> Sake and Marco,
>
> but
Nobody's arguing against the idea of a Wireshark virtual appliance, as far as I
can tell.
As Sake said:
> The problem is how to get
> packets to the virtual appliance. Most virtual switches that come
> with the v
Sake and Marco,
but the idea is to have a software only virtual appliance that could be
loaded on the likes of any Cloud service like Amazon's EC2 or HP's or IBM's
virtual Cloud machines. Doing EC2 for example, you would have a minimal
LINUX core setup virtual appliance.
Here's the virtual i
On 20-9-2010 21:34, Sake Blok wrote:
> wireshark installed, ready to deploy). The problem is how to get
> packets to the virtual appliance. Most virtual switches that come
> with the virtualization environment just don't do port mirroring and
> such (please correct me if I'm wrong here nowadays).
On 20 sep 2010, at 06:58, john s wolter wrote:
> WireShark needs to have software virtual appliances. This for the Cloud
> computing services and for the virtual environments like Xen. A minimal
> virtual WireShark appliance could be added as an observer as part of a cloud
> array or Xen envi
WireShark needs to have software virtual appliances. This for the Cloud
computing services and for the virtual environments like Xen. A minimal
virtual WireShark appliance could be added as an observer as part of a cloud
array or Xen environment. It's a perfect complement to the physical
applian
18 matches
Mail list logo
