Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i always feel like a dickhead when i have problems installing from source, so here i go: i downloaded the source tarball for tripwire 2.3.1-2 and tried following the instructions (post untarring) that said to look at the contents of the makefile in the src/ directory and edit it to fit your system architecture.
i read through the makefile and read that i must set the SYSPRE variable to specify what architecture i was compiling for. once i had checked that the appropriate SYSPRE variable was uncommented i issued the "make release" command that should compile the binaries, but i got an error message. here's how the section of my makefile with the SYSPRE variable looks:
#-----------------------------------------------------------------------------
# SYSPRE makefile variable
#
# System prefix convention is to use a single character to designate the
# operating system and a single character to designate the architecture.
#
# Uncomment the appropriate SYSPRE definition below for your architecture.
# Note that if you uncomment more than one, gmake will use the last one.
#
# Prefix for various OS/Architectures:
#
# i686-pc-linux == Linux Intel x86
# sparc-linux == Linux Sparc (not fully implemented)
#
i think this is right, as i have a dual-athlon architecture (i think the 686 designation is fine...), but then i get an error during compilation:
c++ -I../stlport -Wall -W -Wno-sign-compare -Wno-unused -Wno-uninitialized -ftemplate-depth-32 -O2 complex.cpp -c -o obj/GCC/Release/complex.o
In file included from ../stlport/complex:40,
from complex.cpp:21:
../stlport/wrap_std/complex:16:39: ../g++-include/complex: No such file or directory
complex.cpp:26: parse error before `&' token
complex.cpp: In function `float abs(...)':
complex.cpp:28: `__z' undeclared (first use this function)
...
complex.cpp:262: parse error before `if'
complex.cpp:266: syntax error before `.' token
complex.cpp:271: syntax error before `.' token
gmake[4]: *** [obj/GCC/Release/complex.o] Error 1
gmake[4]: Leaving directory `/home/dick/security/tripwire-2.3.1-2/src/STLport-4.0/src'
gmake[3]: *** [lib/libstlport_gcc.a] Error 2
gmake[3]: Leaving directory `/home/dick/security/tripwire-2.3.1-2/src/STLport-4.0'
gmake[2]: *** [../../lib/i686-pc-linux_r/libstlport_gcc.a] Error 2
gmake[2]: Leaving directory `/home/dick/security/tripwire-2.3.1-2/src/STLport-4.0'
gmake[1]: *** [STLport_r] Error 2
gmake[1]: Leaving directory `/home/dick/security/tripwire-2.3.1-2/src'
date >> release.i686-pc-linux.out
what gives? normally i can make sense of error outputs and modify my instructions/resident programs to suit, but i'm at a loss here. any suggestions are welcome.
The problem is that tripwire is including the C++ STL (Standard Template Library) which was needed for gcc 2.9x. Slackware 9 has gcc 3.2 which already includes the STL.
Hope that helps,
chris
PS If slackware already has a package for it, you may want to use that because it probably already has most of the file lists setup for you.
thx a lot, i figured it was something i wasn't privy to, as the error message made no sense to me. i'll try to find the slack package, as it's easier than remembering to apply a patch if i install it again later.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.