On Jun 26, 2011, at 9:36 PM, Guy Harris wrote:

> 
> On Jun 26, 2011, at 8:10 AM, Joerg Mayer wrote:
> 
>> Thanks to everyone who responded! I've just finished my first build and
>> run of Wireshark (took me about 3 hours).
>> 
>> The result of your instructions, hints and remarks is included below. Maybe 
>> we
>> can include it after some reviewing/ testing/ tweaking into the 
>> documentation.
> 
> Hmm.
> 
> In the Windows VC nmake file, we have rules to download the binary packages 
> of the support libraries.
> 
> Should we supply your setup script, and perhaps a setup rule in Makefile.am, 
> for OS X?
Isn't the first step to run
./autogen.sh
./configure
before you can use make? These steps require the libraries to be there...

Best regards
Michael
> 
> (Any other UN*Xes for which we should do that?  For most Linux distributions 
> you can probably just install packages for the various required and optional 
> support libraries, including the developer packages, but I suspect trying to 
> enumerate the right packages for particular releases of particular 
> distributions would be too much work.  *BSD might be similar, with their 
> various ports/packages databases.  That leaves the usual commercial-UNIX 
> suspects - Solaris, HP-UX, AIX, and various end-of-lifed UN*Xes such as Tru64 
> UNIX.)
> ___________________________________________________________________________
> Sent via:    Wireshark-dev mailing list <[email protected]>
> Archives:    http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
>             mailto:[email protected]?subject=unsubscribe
> 

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

Reply via email to