From: Chris T. <zi...@ad...> - 2005-07-10 15:49:27
|
On Jul 10, 2005, at 6:02 AM, Guido Schimmels wrote: > On Sat, 9 Jul 2005 09:09:45 -0400 > Chris Turkel <zi...@ad...> wrote: > > >> >> On Jul 7, 2005, at 10:39 PM, Lars Hansson wrote: >> >> >>> On Thu, 7 Jul 2005 20:12:01 -0400 >>> Chris Turkel <zi...@ad...> wrote: >>> >>> >>> >>>> /root/OroboROX/src/main.c:188: error: elements of array >>>> `long_options' >>>> have incomplete type >>>> >>>> >>> >>> OroboROX thinks that you dont have long_options support. There's >>> an ifdef in main.c that you need to remove (I cant recall exactly >>> what it's called but it's fairly obvious when you look at it) >>> You could also search the archives for the patch I made for this >>> very issue. >>> >>> >> >> I searched the archives for this patch and couldn't find it. I tried >> commenting out the ifdefs that mention long options but to no avail, >> I dont know what I am looking for. >> > > Hmm. The configure script checks for long options support. If it is > not found, > OroboROX should compile just fine, only with long options disabled, > as the > respective code is wrapped inside: > > #ifdef HAVE_GETOPT_LONG > ... > #endif > > In your case HAVE_GETOPT_LONG seems to be set to "1" in config.h, but > the right header files are not imported in main.c. > > If you change (top of main.c) > > #ifdef HAVE_GETOPT_LONG > #include <getopt.h> > #endif > > to > > #undef HAVE_GETOPT_LONG > #ifdef HAVE_GETOPT_LONG > #include <getopt.h> > #endif > > OroboROX should compile. > > > > Could you please search for HAVE_GETOPT_LONG in =build/config.h an > report? > Does anybody know the right header file to import on fBSD? I have three HAVE_GETOPT_LONG entries in main.c, which one do I use? I posted the main.c in question (in case anyone needs it) at http:// homepage.mac.com/zizban/main.txt. I see HAVE_GETOPT_LONG in config.h.in. When I build OroboROX I'll look in the =build directory. |