Sponsored Content
Top Forums Programming Need Help with g++ and/or codaLite Post 302384249 by henslewm on Monday 4th of January 2010 02:11:10 PM
Old 01-04-2010
Need Help with g++ and/or codaLite

I am running a linux-x86 machine with Ubuntu 9.10. Currently we are trying to re-build the data acquisition system in my lab, and to do this we must interface the linux machine with a VME crate via codaLite.

My question pertains to the compilation error I am receiving from g++. At the top of the file cMsgRoc.cc the header file exists as

#include <string>
etc etc

the string.h file exists in /usr/include and contains the corresponding function so that I'm assuming it is up to date.

I've hit a stand-still and would really appreciate any help! Thanks in advance!





g++ -I../libsrc++ -I. -I/usr/local/codaLite/coda/include -I/usr/local/codaLite/coda/include -I/usr/local/codaLite/coda/include -I/apps/expat/include -I/usr/local/codaLite/coda/include -Wall -fPIC -D_GNU_SOURCE -m32 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -c -o .Linux-i686/objects/cMsgRoc.o cMsgRoc.cc
cMsgRoc.cc: In member function ‘void cMsgRoc::evThread()':
cMsgRoc.cc:233: warning: ‘i' may be used uninitialized in this function
g++ -L/usr/local/codaLite/coda/Linux-i686/lib -m32 .Linux-i686/objects/cMsgRoc.o -L/usr/local/codaLite/coda/Linux-i686/lib -lcmsgxx -lcmsg -lcmsgRegex -L/usr/local/codaLite/coda/Linux-i686/lib -levioxx -levio -L/apps/expat/lib -lexpat -L/usr/local/codaLite/coda/Linux-i686/lib -lcodaObject -lieee -lrt -lpthread -lz -lm -lnsl -lresolv -ldl -o .Linux-i686/bin/cMsgRoc
g++ -I../libsrc++ -I. -I/usr/local/codaLite/coda/include -I/usr/local/codaLite/coda/include -I/usr/local/codaLite/coda/include -I/apps/expat/include -I/usr/local/codaLite/coda/include -Wall -fPIC -D_GNU_SOURCE -m32 -D_REENTRANT -D_POSIX_PTHREAD_SEMANTICS -c -o .Linux-i686/objects/cMsgRoc2.o cMsgRoc2.cc
cMsgRoc2.cc: In function ‘void decode_command_line(int, char**)':
cMsgRoc2.cc:376: error: ‘strncasecmp' was not declared in this scope
make[1]: *** [cMsgRoc2.o] Error 1
make[1]: Leaving directory `/usr/local/codaLite/codaObject/src/execsrc'
make: *** [install] Error 2
 
whereis(1B)					     SunOS/BSD Compatibility Package Commands					       whereis(1B)

NAME
whereis - locate the binary, source, and manual page files for a command SYNOPSIS
/usr/ucb/whereis [-bmsu] [ -BMS directory... -f] filename... DESCRIPTION
The whereis utility locates source/binary and manuals sections for specified files. The supplied names are first stripped of leading path- name components and any (single) trailing extension of the form .ext, for example, .c. Prefixes of s. resulting from use of source code control are also dealt with. whereis then attempts to locate the desired program in a list of standard places: etc /sbin /usr/bin /usr/ccs/bin /usr/ccs/lib /usr/lang /usr/lbin /usr/lib /usr/sbin /usr/ucb /usr/ucblib /usr/ucbinclude /usr/games /usr/local /usr/local/bin /usr/new /usr/old /usr/hosts /usr/include /usr/etc OPTIONS
The following options are supported: -b Searches only for binaries. -B Changes or otherwise limits the places where whereis searches for binaries. -f Terminates the last directory list and signals the start of file names, and must be used when any of the -B, -M, or -S options are used. -m Searches only for manual sections. -M Changes or otherwise limits the places where whereis searches for manual sections. -s Searches only for sources. -S Changes or otherwise limit the places where whereis searches for sources. -u Searches for unusual entries. A file is said to be unusual if it does not have one entry of each requested type. Thus `whereis -m -u *' asks for those files in the current directory which have no documentation. EXAMPLES
Example 1: Finding files Find all files in /usr/bin which are not documented in /usr/share/man/man1 with source in /usr/src/cmd: example% cd /usr/ucb example% whereis -u -M /usr/share/man/man1 -S /usr/src/cmd -f * FILES
/usr/src/* /usr/{doc,man}/* /etc, /usr/{lib,bin,ucb,old,new,local} ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWscpu | +-----------------------------+-----------------------------+ SEE ALSO
chdir(2), attributes(5) BUGS
Since whereis uses chdir(2) to run faster, pathnames given with the -M, -S, or -B must be full; that is, they must begin with a `/'. SunOS 5.10 10 Jan 2000 whereis(1B)
All times are GMT -4. The time now is 02:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy