Re: issues compiling 2.1.69 on FreeBSD 5.4

[Dmitri A. Sergatskov]

Joan Picanyol i Puig wrote:
> Hi,
>
> The octave port has been marked as broken, since it does not build on
> FreeBSD. I've tried it myself and had no luck (long lines):
>
> g++ -I/usr/local/include -I/usr/include -I. -I.. -I../liboctave -I../src 
> -I../libcruft/misc  -I../glob -I../glob -DHAVE_CONFIG_H -mieee-fp -Wall -W 
> -Wshadow -g -O2 -rdynamic \
> -L..  -fPIC -L/usr/local/lib -o octave \
> main.o  \
> -L../liboctave -L../libcruft -L../src  \
> -loctinterp -loctave  -lcruft  ../glob/glob.o ../glob/fnmatch.o  \
>  /usr/local/lib/libalapack_r.so -lcblas -lf77blas -latlas  -lreadline  
> -lncurses -lm  -L/usr/local/lib -L/usr/lib -lg2c -lm
> ../liboctave/liboctave.so: warning: warning: tempnam() possibly used unsafely; 
> consider using mkstemp()
> ../liboctave/liboctave.so: undefined reference to `fnmatch(char const*, char 
> const*, int)'
>
> Any ideas?

Octave used to have its own versions of fnmatch and glob. Those have been 
removed since
both of them are part of the POSIX. But perhaps FreeBSD does not have them
for some reason?
What do "man glob" and "man fnmatch" return on your computer?
Do you have glob.h and fnmatch.h?
Here is what I get on Linux:

man fnmatch:

NAME
       fnmatch - match filename or pathname

SYNOPSIS
       #include <fnmatch.h>

       int fnmatch(const char *pattern, const char *string, int flags);

...
CONFORMING TO
       ISO/IEC 9945-2: 1993 (POSIX.2).  The  FNM_FILE_NAME,  FNM_LEADING_DIR,
       and FNM_CASEFOLD flags are GNU extensions.


> qvb

Sincerely,

Dmitri.
--



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------