Hi,

Use this command line:
WIRESHARK_RUN_FROM_BUILD_DIRECTORY=1 ./wireshark

Thanx,
Jaap

divya kothapally wrote:
>     Hi,
> 
>    I did launch wireshark with just a make on it.
>    But now iam facing a problem when I am placing two wireshark single 
> binary compile on the server.  One already existed on the server is 
> working fine but the second single wireshark binary is taking the 
> respective libraries of the linux machines from which it is launched 
> than its complied libraries.
>  
> Correct if I have done something wrong in placing the binary: 
> 1. Built the second wireshark version in a random directory of 
> the server (just did a make)
> 2. Renamed the wireshark binary to wireshark2
> 3. Copied the single wireshark binary to directory of the server where 
> everybody can access 
>  
>      Is there any way I could make both the wireshark single compile 
> binaries work on the server.
>  
> Thanks
> Divya
> 
> 
> 
>     ------------------------------
> 
>     Message: 2
>     Date: Wed, 12 Aug 2009 12:42:30 -0700
>     From: Guy Harris <g...@alum.mit.edu <mailto:g...@alum.mit.edu>>
>     Subject: Re: [Wireshark-dev] Help
>     To: Developer support list for Wireshark
>     <wireshark-dev@wireshark.org <mailto:wireshark-dev@wireshark.org>>
>     Message-ID: <00d79753-843b-422f-806b-048ee88eb...@alum.mit.edu
>     <mailto:00d79753-843b-422f-806b-048ee88eb...@alum.mit.edu>>
>     Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
> 
> 
>     On Aug 12, 2009, at 9:15 AM, divya kothapally wrote:
> 
>      > Iam trying to launch wireshark by just doing a make on it. It is
>      > giving me following errors:
>      > gcc: sync_pipe_write.o: No such file or directory
>      > gcc: util.o: No such file or directory
>      > gcc: tap-rtp-common.o: No such file or directory
>      > gcc: capture_info.o: No such file or directory
>      > gcc: epan/.libs/libwireshark.so: No such file or directory
> 
> 
> -- 
> Best,
> Divya Kothapally
> 
> 

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe

Reply via email to