This is a discussion on Re: [Snort-users] --enable-sourcefire within the Snort forums, part of the System Security and Security Related category; Geffrey Vel=E1squez wrote: > With 2.3.2: > > ./configure --help > ... > --enable-sourcefire Enable Sourcefire specific ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Geffrey Vel=E1squez wrote:
> With 2.3.2: > > ./configure --help > ... > --enable-sourcefire Enable Sourcefire specific build options It actually does nothing. It adds -DSOURCEFIRE to the cflags passed to the c compiler. This=20 creates a defined preprocessor symbol SOURCEFIRE, but nothing in the=20 source code uses that define. Having flags like this is pretty common in=20 development. I suspect it's an artifact of some testing flags that one=20 of the developers uses. I even did a recursive grep, and found no reference the the SOURCEFIRE=20 directive anywhere other than configure and configure.in, proving it=20 really does nothing. grep -r SOURCEFIRE * File configure: CFLAGS=3D"$CFLAGS -DSOURCEFIRE" File configure.in: CFLAGS=3D"$CFLAGS -DSOURCEFIRE",) ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Snort-users mailing list Snort-users@lists.sourceforge.net Go to this URL to change user options or unsubscribe: https://lists.sourceforge.net/lists/...fo/snort-users Snort-users list archive: http://www.geocrawler.com/redir-sf.p...st=snort-users |