octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: error building GUI on Mac OS-X 10.6.8


From: Ben Abbott
Subject: Re: error building GUI on Mac OS-X 10.6.8
Date: Sun, 12 Aug 2012 17:48:20 -0400

On Aug 12, 2012, at 5:24 PM, Michael Goffioul wrote:

> On Sun, Aug 12, 2012 at 10:05 PM, Ben Abbott <address@hidden> wrote:
> On Aug 12, 2012, at 10:46 AM, John W. Eaton wrote:
> 
> > On 12-Aug-2012, Ben Abbott wrote:
> >
> > | You are correct, I've been building in my source tree.  How do I set up a 
> > build tree?
> >
> > Create a new directory and cd to it.  Then run
> >
> >  /your/octave/source/directory/configure
> >
> > in your build directory.  That will create all the subdirectories and
> > Makefiles in the build tree.
> >
> > jwe
> 
> 
> I'm  now seeing my build fail with a long sequence of errors like ....
> 
> ../libgnu/stdio.h:1252:18: error: expected constructor, destructor, or type 
> conversion before '(' token
> In file included from ../../gui/libcruft/misc/quit.h:33:0,
>                  from ../../gui/libcruft/misc/f77-fcn.h:26,
>                  from ../../gui/libcruft/misc/f77-extern.cc:28:
> 
> See the attached for more details.  I assume I've done something wrong.
> 
> I have a directory "./gui" that holds the sources for the gui branch, and a 
> second directory, "./gui_build" where I intended to build the sources.  From 
> the build directory, I tried "../gui/configure ..."
> 
> This looks like some pre-processor error, like a symbol being unexpectedly 
> defined, or not. I would advise to run compile command (just copy and paste 
> in a terminal) with the -E flag and inspect the pre-processed results at the 
> lines corresponding to the first error (../libgnu/signal.h, line 168). 
> According to the log file you attached, the command to run should look like 
> (not tested):
> 
> /opt/local/bin/gcc-mp-4.5 -DHAVE_CONFIG_H -I. -I../../gui/libcruft -I.. 
> -I../libgnu -I../../gui/libgnu -D_THREAD_SAFE -pthread -I/opt/local/include 
> -pipe -O0 -g -m64 -ggdb3 -gstabs -D_THREAD_SAFE -pthread -funroll-loops 
> -lstdc++ -D_THREAD_SAFE -pthread -Wall -W -Wshadow -Wformat -Wpointer-arith 
> -Wmissing-prototypes -Wstrict-prototypes -Wwrite-strings -Wcast-align 
> -Wcast-qual -pipe -O0 -g -m64 -ggdb3 -gstabs -D_THREAD_SAFE -pthread 
> -funroll-loops -lstdc++ -D_THREAD_SAFE -pthread -MT 
> misc/libcruft_la-lo-error.lo -MD -MP -MF misc/.deps/libcruft_la-lo-error.Tpo 
> -c ../../gui/libcruft/misc/lo-error.c  -fno-common -DPIC -E -o lo-error-cpp.c
> 
> the result being saved in lo-error-cpp.c.
> 
> Michael.

I ran that command above from the build-directory's libcruft subdirectory and 
obtained attached the lo-error-cpp.c

Ben

Attachment: lo-error-cpp.c
Description: Binary data





reply via email to

[Prev in Thread] Current Thread [Next in Thread]