Sponsored Content
Full Discussion: Compiling Pcap.c
Top Forums Programming Compiling Pcap.c Post 13682 by thalex on Tuesday 22nd of January 2002 09:51:05 AM
Old 01-22-2002
i believe the -x directives are now wrong. The -xO3 i presume it is the optimization. Remove it completeley or try simply -O3. To see the options of gcc simply type #man gcc. If it is not listed, it is not supported. If #man gcc doesnt work try this:

#cd /usr/local/bin/man/man1
#nroff -man gcc.1 |more

Note it is a difficult matter if there is no config file
 

10 More Discussions You Might Find Interesting

1. Programming

pcap.h

I cant use pcap.h include file. How can I do so? :confused: (8 Replies)
Discussion started by: Pervez Sajjad
8 Replies

2. Programming

Filtering paquets with pcap.h

Hello everybody!! I am currently doing my intership and I need some tips for Pcap.h. I search some tips tp filter my paquets in a C program with the Pcap.h librairy. The onlys thing I have found is thaht I can filter low level protocol with their name like (tcp/udp..). But for the higher... (3 Replies)
Discussion started by: danathane
3 Replies

3. Programming

Pcap.h Sniffing

Can someone please help me figure out how to use pcap.h to sniff packets between only 2 computers whose mac addresses are know? Thanks (0 Replies)
Discussion started by: papabearcares
0 Replies

4. Shell Programming and Scripting

Pcap.h Sniffing

Can someone please help me figure out how to use pcap.h to sniff packets between only 2 computers whose mac addresses are know? Thanks (0 Replies)
Discussion started by: papabearcares
0 Replies

5. UNIX for Dummies Questions & Answers

Filtering pcap files

Hi, I am new at UNIX and programing in general and only have a basic knowledge of C++. I am helping out with some research at a college and was given the task to sort through captured packets via IP addresses. I was wondering if anyone could help me with writing a code which filters through pcap... (1 Reply)
Discussion started by: hershey101
1 Replies

6. Programming

searching through pcap files

Hi, I am new at UNIX and programing in general and only have a basic knowledge of C++. I am helping out with some research at a college and was given the task to sort through captured packets via IP addresses. I was wondering if anyone could help me with writing a code which filters through pcap... (4 Replies)
Discussion started by: hershey101
4 Replies

7. Programming

Packet capturing using pcap

Hi, i am using a linux CentOS machine. I have 2 real network interfaces eth0, eth1 and 2 virtual interfaces tap0 and tap1. I am using PCAP library to capture the packets on theses interfaces. If i specify the interface as "any", i cannot find a way to know from which interface the packet... (1 Reply)
Discussion started by: rahulnitk2004
1 Replies

8. Shell Programming and Scripting

Sampling pcap file

Hi, I have a standard pcap file created using tcpdump. The file looks like 06:49:36.487629 IP 202.1.175.252 > 71.126.222.64: ICMP echo request, id 52765, seq 1280, length 40 06:49:36.489552 IP 192.120.148.227 > 71.126.222.64: ICMP echo request, id 512, seq 1280, length 40 06:49:36.491812 IP... (8 Replies)
Discussion started by: sajal.bhatia
8 Replies

9. Programming

Ascii vs Pcap tracing

Dear All, Which is better to use ? Ascii or Pcap tracing ? Or are they complementary ? (1 Reply)
Discussion started by: knowledgeSeeker
1 Replies

10. Programming

PCAP -> PFRING

Hi I have a program that captures packets with the libpcap library by calling the pcap-functions, e.g. pcap_next(...). I would like to use PF_RING for the program and therefore I would have to adjust the calling functions to pfring_open(...) pfring_recv(...) I'm pretty knew in network... (0 Replies)
Discussion started by: Freaky123
0 Replies
WINEGCC(1)						      Wine Developers Manual							WINEGCC(1)

NAME
winegcc - Wine C and C++ MinGW Compatible Compiler SYNOPSIS
winegcc [options] infile... DESCRIPTION
winegcc is a gcc wrapper which tries to provide a MinGW compatible compiler under Linux. This is most useful to Win32 developers who can simply take their MinGW code from Windows, and recompile it without modifications under Winelib on Linux. wineg++ accepts mostly the same options as winegcc. The goal of winegcc is to be able to simply replace gcc/g++/windres with winegcc/wineg++/wrc in a MinGW Makefile, and just recompile the application using Winelib under Wine. While typically there are small adjustments that must be made to the application source code and/or Makefile, it is quite easy to do them in a fashion that is compatible between the MinGW and Wine environments. This manual will document only the differences from gcc; please consult the gcc manual for more information on those options. OPTIONS
gcc options: All gcc options are supported, and are passed along to the backend compiler. -Bprefix This option specifies where to find the executables, libraries, include files, and data files of the compiler itself. This is a standard gcc option that has been extended to recognize a prefix ending with '/tools/winebuild', in which case winegcc enters a spe- cial mode for building Wine itself. Developers should avoid prefixes ending with the magic suffix, or if that is not possible, sim- ply express it differently, such as '/tools/winebuild/', to avoid the special behaviour. -fno-short-wchar Override the underlying type for wchar_t to be the default for the target, instead of using short unsigned int, which is the default for Win32. -mconsole This option passes '--subsystem console' to winebuild, to build console applications. It is the default. -mno-cygwin Use Wine's implementation of MSVCRT, instead of linking against the host system's libc. This is necessary for the vast majority of Win32 applications, as they typically depend on various features of MSVCRT. This switch is also used by the MinGW compiler to link against MSVCRT on Windows, instead of linking against Cygwin's libc. Sharing the syntax with MinGW makes it very easy to write Make- files that work under Wine, MinGW+MSYS, or MinGW+Cygwin. -municode Set the default entry point of the application to be the Unicode wmain() instead of the standard main(). -mwindows This option adds -lgdi32, -lcomdlg32, and -lshell32 to the list of default libraries, and passes '--subsystem windows' to winebuild to build graphical applications. -nodefaultlibs Do not use the standard system libraries when linking. These include at a minimum -lkernel32, -luser32, -ladvapi32, and any default libraries used by the backend compiler. The -mwindows option augments the list of default libraries as described above. -nostartfiles Do not add the winecrt0 library when linking. -Wb,option Pass option as an option to winebuild. If option contains commas, it is split into multiple options at the commas. DEFINES
winegcc defines __WINE__, for code that needs to know when it is being compiled under Wine. It also defines WIN32, _WIN32, __WIN32, __WIN32__, __WINNT, and __WINNT__ for compatibility with MinGW. BUGS
The dllimport/dllexport attributes are not supported at the moment, due to lack of support for these features in the ELF version of gcc. Static linking is not currently supported against Wine's DLL. As a result, the -static, --static, and -Wl,-static options will generate an error. AUTHORS
winegcc was written by Dimitrie O. Paun. SEE ALSO
gcc(1), winebuild(1), wrc(1), wine(1), Winelib User Guide, Wine Developers Guide. Wine 1.2-rc6 October 2005 WINEGCC(1)
All times are GMT -4. The time now is 01:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy