|
|
|
|
Snort Forums Archive
Archive Home » Other » Creating Mac OSX Binaries
Please note that the categories listed below represent an archived version of our forums pages. To view the current version and be able to post and reply to threads, please register and login here to go to the full forums pages.
[ Notice: Full Version of This Topic ]
Creating Mac OSX Binaries
Posted by mlzusel on October 16, 2006 11:36:56
H,
In the binaries download section, the last update for OSX binaries is very out of date. Could someone please help me with how I would go about creating OSX Binaries?
Thank you. |
|
Posted by brianjking on October 11, 2007 00:39:20
I'm also in need of some assistance here. Thanks! |
|
Posted by iana on October 18, 2007 03:55:52
OSX binaries seem not be updated for a long time.
--------------
latest [url=http://www.softsea.com]shareware & freeware[/url] |
|
Posted by mwfong_sri on November 21, 2007 10:23:27
Under Mac OS X 10.5 (Leopard), I was able to successfully build snort
2.8.0. However, to properly deal with the dynamic preprocessor
libraries, I had to execute the following (courtesy the 'Net):
aclocal -I m4
autoheader
automake --add-missing --copy
autoconf
setenv LD_TWOLEVEL_NAMESPACE 1
./configure --enable-dynamicplugin
and I also had to create the following symlink in
src/dynamic-plugins/sf_engine/.libs:
ln -s libsf_engine.dylib libsf_engine
Unfortunately, the resultant snort image crashes. When I added
"--enable-debug" to the configure invocation, "make clean all", and
ran the image in gdb, I got
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
0x00000000 in ?? ()
(gdb) where
#0 0x00000000 in ?? ()
Cannot access memory at address 0x0
Cannot access memory at address 0x0
Cannot access memory at address 0x0
Cannot access memory at address 0x0
Cannot access memory at address 0x0
#1 0x00e013f0 in SetupSSH () at spp_ssh.c:122
Cannot access memory at address 0x0
Cannot access memory at address 0x0
Cannot access memory at address 0x0
Cannot access memory at address 0x0
Cannot access memory at address 0x0
Cannot access memory at address 0x0
Cannot access memory at address 0x0
#2 0x00e03900 in InitializePreprocessor (dpd=Cannot access memory at address 0x0
0xbffff80c) at sf_dynamic_preproc_lib.c:116
Cannot access memory at address 0x0
Cannot access memory at address 0x0
#3 0x00072204 in InitDynamicPreprocessorPlugins (info=0xbffff80c) at sf_dynamic_plugins.c:920
#4 0x000728b4 in InitDynamicPreprocessors () at sf_dynamic_plugins.c:1077
#5 0x000295e8 in SnortMain (argc=9, argv=0xbffff9d0) at snort.c:909
#6 0x00028a70 in main (argc=9, argv=0xbffff9d0) at snort.c:388
Any insight would be appreciated.
|
|
Posted by mwfong_sri on November 21, 2007 13:29:19
Given that I have been able to successfuly build and run snort-2.6.1.5
under 10.4/Xcode 2.4.1, I built snort-2.6.1.5 on 10.5/Xcode 3.0.
Unfortunately, under 10.5, it too, segfaulted in the same fashion as
described above. Although this implies that the problem is
10.5-specific, any insight would be appreciated.
|
|
Posted by p2409 on January 26, 2008 19:23:53
Can't help with OS X 10.5, but this may help people who can't avoid getting a bus error on
the dynamicplugins, despite following the INSTALL instructions.
My problem in this case was ./configure not setting the allow_undefined_flag properly. There
were two reasons for this:
First was my iTerm shell wasn't picking up the environment variable
LD_TWOLEVEL_NAMESPACE. Don't know why, but it started working again (!!!)
Second was MACOSX_DEPLOYMENT_TARGET was not set. I read this can be a problem in
10.4. If it's not on yours, you need to
export MACOSX_DEPLOYMENT_TARGET=10.4
before you ./configure.
In summary, your ./configure must be setting
allow_undefined_flag='undefined dynamic_lookup' (around line 8128)
No probs with dynamic libraries after this!
Also - in another posting, I got HenWen going native 10.4, new snort etc. See separate
posting in this site and check sourceforge HenWen discussion for instructions.
Hope this helps somebody out there!
|
|
Posted by p2409 on January 26, 2008 19:24:55
umm.that line number should be 8128 |
|
|
|
|
|
