> (I'm running on a fresh install of fc11.)
OK - which snapshot of fltk are you using, by the way?
> Running ./configure shows no errors as such but I get some negatives:
>
> checking sys/stdtypes.h usability... no
> checking sys/stdtypes.h presence... no
> checking for sys/stdtypes.h... no
> .
> checking for strlcat... no
> .
> checking libpng/png.h usability... no
> checking libpng/png.h presence... no
> checking for libpng/png.h... no
> .
> checking for pthread_create using -lpthreads... no
> .
> checking for X overlay visuals... no
>
> Everything else is a yes. Do these nos constitute warnings
> bad enough to affect make?
Thise things are all OK. That's the configure script testing your
machine to see what things it supports.
At the end of the configure you should get a summary of the results -
those are really all that matters. You could post just the summary here
if you are still worried about it.
However, it might be interesting to us to see what configure reported
when checking for "scandir" when checking your machine, based on what
happens later...
> When I then make, I get this:
> Fl.cxx: In static member function 'static int Fl::handle(int,
> Fl_Window*)':
> Fl.cxx:959: warning: suggest parentheses around '&&' within '||'
>
> A few of these liberally sprinkled about:
> ..warning: suggest parentheses around '&&' within '||'
OK - this is because you are using a more recent version of gcc (I guess
4.3?) and it is much more picky about code layout than earlier versions.
We'll probably fix that sometime, but it is not harmful for now.
> and then:
> Compiling Fl_Text_Buffer.cxx...
> Fl_Text_Buffer.cxx: In member function 'int
> Fl_Text_Buffer::undo(int*)':
> Fl_Text_Buffer.cxx:344: warning: suggest parentheses around
> '&&' within '||'
> Fl_Text_Buffer.cxx: In function 'char chooseNullSubsChar(char*)':
> Fl_Text_Buffer.cxx:1346: warning: array subscript has type 'char'
Ditto, this is just a newer version of gcc being picky about syntax.
However, this next is more serious - this looks like a real problem:
> and lastly:
> Compiling filename_list.cxx...
> filename_list.cxx: In function 'int fl_filename_list(const
> char*, dirent***, int (*)(dirent**, dirent**))':
> filename_list.cxx:93: error: invalid conversion from 'int
> (*)(const void*, const void*)' to 'int (*)(const dirent**,
> const dirent**)'
> filename_list.cxx:93: error: initializing argument 4 of
> 'int scandir(const char*, dirent***, int (*)(const dirent*),
> int (*)(const dirent**, const dirent**))'
> make[1]: *** [filename_list.o] Error 1
> make: *** [all] Error 1
>
> ..Which doesn't look too good at all. Any further suggestions?.
This is a bit of a show-stopper.
Is anybody else out there using F11, and if so what are they seeing?
By default, we assume that the signature of scandir is:
scandir(d, list, 0, (int(*)(const void*,const void*))sort);
And this has always worked for Linux builds in the past.
But it now looks like F11 has scandir defined as
scandir(d, list, 0, (int(*)(const dirent **, const dirent
**))sort);
Which previously we only really expected with HP-UX and Cygwin.
I guess this might just be the gcc version being more picky about
casting the sort function to the correct type?
It would be interesting to know what the signature of the scandir
function is actually defined as on a F11 system - can you look that up
for us, it will be defined somewhere in the file /usr/include/dirent.h
(I think!)
Also, what does "man scandir" say the function signature is for your
system?
Either way, this looks like a problem with how scandir is defined - can
you let us know what it is that you find?
--
Ian
SELEX Sensors and Airborne Systems Limited
Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14
3EL
A company registered in England & Wales. Company no. 02426132
********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
