This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: egcs-19981122 fails to compile xpdf-0.80 on Solaris 2.6 x86
- To: Alexandre Oliva <oliva at dcc dot unicamp dot br>
- Subject: Re: egcs-19981122 fails to compile xpdf-0.80 on Solaris 2.6 x86
- From: Bernard Michaud <bmichaud at excom dot com>
- Date: Mon, 30 Nov 1998 20:29:24 -0500
- Cc: egcs-bugs at cygnus dot com
- References: <Bernard Michaud's message of "Mon, 30 Nov 1998 06:19:48 -0500"><4.1.19981130061118.00a2f220@mail.magma.ca>
At 30/11/98 14:21 -0200, Alexandre Oliva wrote:
>On Nov 30, 1998, Bernard Michaud <bmichaud@excom.com> wrote:
>
>> This was the attempt to compile xpdf-0.80 using egcs-19981122 on a dual
>> Pentium Pro running Solaris 2.6 x86:
>
>> LTKButtonDialog.cc:97: passing `const char *' as argument 3 of
>> `LTKButton::LTKButton(char *, int, char *, LTKButtonAction, void
>> (*)(LTKWidget *, int, int))' discards qualifiers
>> LTKButtonDialog.cc:101: passing `const char *' as argument 3 of
>> `LTKButton::LTKButton(char *, int, char *, LTKButtonAction, void
>> (*)(LTKWidget *, int, int))' discards qualifiers
>
>Well, based on the error message you posted without the corresponding
>source code, I can only agree with egcs. You can't pass a `const
>char*' where a `char*' is expected. xpdf seems to be in error.
>
>--
>Alexandre Oliva http://www.dcc.unicamp.br/~oliva aoliva@{acm.org}
>oliva@{dcc.unicamp.br,gnu.org,egcs.cygnus.com,samba.org}
>Universidade Estadual de Campinas, SP, Brasil
>
Firstly, the source code for xpdf is freely available on the Internet; one
of the possible sites is "http://www.foolabs.com/xpdf/". It is a graphical
Adobe Acrobat PDF file viewer, and it is very popular with the Solaris for
Intel crowd because we unfortunately use one of the few platforms for which
Adobe chooses not to port their free Acrobat viewer.
Secondly, the reason I chose to submit this to the egcs bugs mailing list
is because xpdf compiled cleanly with the egcs-1.1 release, but not with
the egcs-19981122 snapshot. If there is indeed a bug in the xpdf source
code (which is certainly possible), then it should not have compiled
cleanly under egcs-1.1. The way I see it, either there is a problem with
egcs-1.1 for compiling the faulty xpdf source code, or there is a problem
with egcs-19981122 for not compiling the same code.
Bernard Michaud
Excom Informatics Services