Coke, These are not intended to be applied. But, I doubt whether it is something else. Here is the output of the Configure.pl, and a diff against the output I get when I use gcc.
Also, here are some reasons to what might cause these errors. 1. these are either misuse of names 2. or due to __cplusplus define missing 3. or due to inline/readline 4. or may be my tweaks Regards, Senaka On Tue, Apr 15, 2008 at 1:45 AM, Will Coleda <[EMAIL PROTECTED]> wrote: > On Mon, Apr 14, 2008 at 4:00 PM, Senaka Fernando <[EMAIL PROTECTED]> > wrote: > > Hi all, > > > > C++ build succeeded, but with some tests failed. There were two issues > that > > I couldn't formally sorted, and thus I had to tweak it. I have opened > > tickets for all other build related issues which have a formal fix. The > > tweaks used along with the make test report are attached herewith. Thus, > I > > believe that you should be able to get Parrot to build with g++ on > Ubuntu > > Gutsy once my tickets are closed and the given diff of tweaks are > applied. > > > > Regards, > > Senaka > > > > Note that one of the failures is in t/codingstd/c_indent.pl - but this > failure is a result of your local changes. (If someone applies this, > please make sure the formatting is fixed.) > > Regards. > -- > Will "Coke" Coleda >
Checking MANIFEST.....................................................done. Setting up Configure's default values.................................done. Setting up installation paths.........................................done. Tweaking settings for miniparrot...................................skipped. Loading platform and local hints files................................done. Finding header files distributed with Parrot..........................done. Determining what C compiler and linker to use.........................done. Determining whether make is installed..................................yes. Determining whether lex is installed...............................skipped. Determining whether yacc is installed..............................skipped. Determining if your C compiler is actually gcc.........................yes. Seeing if GNU libc is installed........................................yes. Determining whether libc has the backtrace* functions (glibc only).....yes. Determining Fink location on Darwin................................skipped. Determining Macports location on Darwin............................skipped. Determining if your C compiler is actually Visual C++...................no. Detecting compiler attributes (-DHASATTRIBUTE_xxx)....................done. Detecting supported compiler warnings (-Wxxx)..................set for gcc. Enabling optimization...................................................no. Determining flags for building shared libraries......................-fPIC. Determine if parrot should be linked against a shared library..........yes. Determining what charset files should be compiled in..................done. Determining what encoding files should be compiled in.................done. Determining what types Parrot should use..............................done. Determining what opcode files should be compiled in...................done. Determining what pmc files should be compiled in......................done. Determining your minimum pointer alignment......................... 1 byte. Probing for C headers.................................................done. Determining some sizes................................................done. Computing native byteorder for Parrot's wordsize.............little-endian. Test the type of va_ptr (this test is likely to segfault)............stack. Figuring out how to pack() Parrot's types.............................done. Figuring out what formats should be used for sprintf..................done. Determining if your C library has a working S_ISREG....................yes. Determining CPU architecture and OS...................................done. Determining architecture, OS and JIT capability.......................done. Generating CPU specific stuff.........................................done. Verifying that the compiler supports function pointer casts............yes. Determining whether your compiler supports computed goto...............yes. Determining if your compiler supports inline............................no. Determining what allocator to use.....................................done. Determining if your C library supports memalign........................yes. Determining some signal stuff.........................................done. Determining whether there is socklen_t.................................yes. Determining if your C library has setenv / unsetenv...................both. Determining if your platform supports AIO..............................yes. Determining if your platform supports GMP..............................yes. Determining if your platform supports readline..........................no. Determining if your platform supports gdbm..............................no. Determining if your platform supports crypto...................yes, 0.9.8e. Seeing if your configuration includes gettext..........................yes. Testing snprintf......................................................done. Determining whether perldoc is installed...............................yes. Determining whether python is installed.........................yes, 2.5.1. Determining whether GNU m4 is installed................................yes. Determining whether (exuberant) ctags is installed......................no. Determining Parrot's revision.......................................r26966. Determining whether ICU is installed...................................yes. Generating C headers..................................................done. Generating core pmc list..............................................done. Generating runtime/parrot/include.....................................done. Configuring languages.................................................done. Generating makefiles and other build files............................done. Moving platform files into place......................................done. Recording configuration data for later retrieval......................done. Okay, we're done!
40c40 < Determining if your compiler supports inline...........................yes. --- > Determining if your compiler supports inline............................no. 48c48 < Determining if your platform supports readline.........................yes. --- > Determining if your platform supports readline..........................no.
