Yes, I did this already and we ended up in:vishnu wrote: I got a good start on compiling dillo using MIPSPro 7.4.3 last fall, the big stumbling block is the authors use of variadic macros, I'll take another look at it tonight with the newer Dillo and we can compare notes. I'm subscribed to the Dillo development list, which is very active, you might want to point these issues out there...
I probably will do that, but there is a chance that this is a known problem other developers had solved in the past. And of course you are welcome to compare notes.corevid wrote: Well, I'm out of ideas for the moment. This is the point where I'd have to throw gdb at it or put in lots of MSG()s
So corevid was trying it with gcc as well? I usually use the ProDev Workshop debugger (cvd) for stuff I've compiled with MIPSPro...corevid wrote: Well, I'm out of ideas for the moment. This is the point where I'd have to throw gdb at it or put in lots of MSG()s
vishnu wrote: I got a good start on compiling dillo using MIPSPro 7.4.3 last fall, the big stumbling block is the authors use of variadic macros, I'll take another look at it tonight with the newer Dillo and we can compare notes.
man cc wrote: * The gcc compiler allows variadic macros; the MIPSpro 7.4 compilers
support these macros in c99 mode. If you have code that uses
ellipses (...) as part of a macro definition and you are not
compiling with c99, you will need to rewrite the macro. Two possible
approaches are to replace the macro with a new variadic function, or
to create a family of macros, each taking different (fixed) numbers
of arguments.
hamei wrote:
man cc wrote: * The gcc compiler allows variadic macros; the MIPSpro 7.4 compilers
support these macros in c99 mode. If you have code that uses
ellipses (...) as part of a macro definition and you are not
compiling with c99, you will need to rewrite the macro. Two possible
approaches are to replace the macro with a new variadic function, or
to create a family of macros, each taking different (fixed) numbers
of arguments.
Worth a try with c99 ?
Code: Select all
cc-1028 CC: ERROR File = dialog.cc, Line = 180
The expression used must have a constant value.
memset(pm, '\0', sizeof(Fl_Menu_Item[n_it+1]));
^
vishnu wrote: I did that and some other difficulty arose that can't remember just now.
True but what I've compiled so far has not been a problem for MIPSPro in CC (not c99) mode. The show stopper in dialog.cc is just plain bad code, and I think it's a bug that gcc doesn't see that...hamei wrote: I'm prob'ly teaching grandma to suck eggs here, but did you know that < man cc > has a ton of stuff about gcc-isms and how to get around them?
No replies because, with regard to what he's asking about doing, well to put it quite simply "you can't get there from here..."hamei wrote: This was a bit interesting ... at least we aren't the only people in the world with some unusual desires ...
http://stackoverflow.com/questions/1250 ... pplication
No replies, tho
Code: Select all
c99 -c -w findtext.cc -o findtext.o
Code: Select all
thoweh@species8472 $>uname -a
IRIX64 species8472 6.5 07202013 IP27
thoweh@species8472 $>c99 -version
MIPSpro Compilers: Version 7.4.4m
thoweh@species8472 $>ls
dillo-3.0.2 dillo-3.0.2.tar
thoweh@species8472 $>cd dillo-3.0.2
thoweh@species8472 $>ls
aclocal.m4 config.h.in doc d_size.h Makefile.in
AUTHORS config.sub Doxyfile INSTALL missing
ChangeLog COPYING dpi install-dpi-local NEWS
configure depcomp dpid install-sh README
configure.in dillorc dpip lout src
config.guess dlib dw Makefile.am test
thoweh@species8472 $>cd dw
thoweh@species8472 $>c99 -c -w findtext.cc -o findtext.o
cc-1040 c99: ERROR File = ../lout/msg.h, Line = 14
An identifier is expected.
#define _MSG(...)
^
cc-1040 c99: ERROR File = ../lout/msg.h, Line = 15
An identifier is expected.
#define _MSG_WARN(...)
^
cc-1040 c99: ERROR File = ../lout/msg.h, Line = 16
An identifier is expected.
#define _MSG_ERR(...)
^
cc-1040 c99: ERROR File = ../lout/msg.h, Line = 19
An identifier is expected.
#define MSG(...) \
^
cc-1040 c99: ERROR File = ../lout/msg.h, Line = 27
An identifier is expected.
#define MSG_WARN(...) \
^
cc-1040 c99: ERROR File = ../lout/msg.h, Line = 33
An identifier is expected.
#define MSG_ERR(...) \
^
cc-1055 c99: ERROR File = findtext.cc, Line = 231
A macro invocation has too many arguments.
_MSG("Having to do.");
^
7 errors detected in the compilation of "findtext.cc".
thoweh@species8472 $>
=
-
vishnu wrote: I get seven errors all having to do with the variadic macros, which MIPSPro 7.4's c99 is supposed to understand.
So if any of you kind people can get it to compile I'll know it's a bad compiler installation on my end.
Code: Select all
Making all in dw
gmake[2]: Entering directory `/usr/people/lgeorge/downtemp/dillo-3.0.2/dw'
source='findtext.cc' object='findtext.o' libtool=no \
DEPDIR=.deps depmode=sgi /bin/ksh ../depcomp \
CC -DHAVE_CONFIG_H -I. -I.. -I.. -I/usr/local/include -mips4 -O3 -c99 -I/usr/nekowar
e/include -I/usr/include -c -o findtext.o findtext.cc
cc-1234 CC: WARNING File = ../lout/object.hh, Line = 66
Access control is not specified ("private" by default).
class Integer: public Object, misc::Comparable
^
cc-1234 CC: WARNING File = ../lout/object.hh, Line = 85
Access control is not specified ("private" by default).
class ConstString: public Object, misc::Comparable
^
cc-1035 CC: WARNING File = /usr/include/stdint.h, Line = 5
#error directive: This header file is to be used only for c99 mode
compilations
#error This header file is to be used only for c99 mode compilations
^
cc-1040 CC: ERROR File = ../lout/msg.h, Line = 14
An identifier is expected.
#define _MSG(...)
^
cc-1040 CC: ERROR File = ../lout/msg.h, Line = 15
An identifier is expected.
#define _MSG_WARN(...)
^
cc-1040 CC: ERROR File = ../lout/msg.h, Line = 16
An identifier is expected.
#define _MSG_ERR(...)
^
cc-1040 CC: ERROR File = ../lout/msg.h, Line = 19
An identifier is expected.
#define MSG(...) \
^
cc-1040 CC: ERROR File = ../lout/msg.h, Line = 27
An identifier is expected.
#define MSG_WARN(...) \
^
cc-1040 CC: ERROR File = ../lout/msg.h, Line = 33
An identifier is expected.
#define MSG_ERR(...) \
^
cc-1055 CC: ERROR File = findtext.cc, Line = 231
A macro invocation has too many arguments.
_MSG("Having to do.");
^
7 errors detected in the compilation of "findtext.cc".
gmake[2]: *** [findtext.o] Error 2
gmake[2]: Leaving directory `/usr/people/george/downtemp/dillo-3.0.2/dw'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/usr/people/george/downtemp/dillo-3.0.2'
gmake: *** [all] Error 2
Code: Select all
urchin 18% printenv
...
CC=c99
CXX=CC
F77=f77
CFLAGS=-mips4 -O3 -c99 -I/usr/nekoware/include -I/usr/include
CXXFLAGS=-mips4 -O3 -c99 -I/usr/nekoware/include -I/usr/include
LDFLAGS=-mips4 -L/usr/nekoware/lib -L/usr/lib32 -Wl,-rpath -Wl,/usr/nekoware/lib
LD_LIBRARY_PATH=/usr/nekoware/lib /usr/lib32
LD_LIBRARYN32_PATH=/usr/nekoware/lib:/usr/lib32
MAKE=gmake
GNUMAKE=gmake
I think that's a bug in the header file, a couple of the others have it too: grep "ifndef __c99" /usr/include/*.h . . . How much does sgi charge for a MIPSPro license again?hamei wrote: Notice the third warning down though ? Something odd going on ?
Yep, I think that's the "other difficulty" I was talking about above...canavan wrote: The MIPSpro C++ compiler isn't c99 compliant...
diegel wrote: There is probably a problem in the IO part. Socket connections don't work at all and opening files has a strange 32byte limit in path length. I am sure this is not a problem of the gcc build.
...
Now?
+MLA
...
Other:
DEC
Sun
,
DG AViiON
,
NeXT