Re: EGCS 1.1.1 FYI

7 messages, 6 authors, 1998-12-12 · open the first message on its own page

Re: EGCS 1.1.1 FYI

From: David Edelsohn <hidden>
Date: 1998-12-07 15:10:10

quoted
quoted
quoted
quoted
"Paul J Schinder" writes:
Paul> So are Gary Thomas' patches still necessary?

	The trampoline patch now has become a shared library compatibility
issue for glibc-1.99 support.  It only is necessary until LinuxPPC cuts
over to glibc-2.1 which will require other binary incompatible changes at
the same time.

David

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: EGCS 1.1.1 FYI

From: Ralf Weidemann <hidden>
Date: 1998-12-07 22:22:42

quoted
quoted
quoted
quoted
"David" == David Edelsohn [off-list ref] writes:
"Paul J Schinder" writes:
    Paul> So are Gary Thomas' patches still necessary?

    David> 	The trampoline patch now has become a shared library
    David> compatibility issue for glibc-1.99 support.  It only is
    David> necessary until LinuxPPC cuts over to glibc-2.1 which will
    David> require other binary incompatible changes at the same time.

Can someone clarify where the problem is exact with native
egcs and libc-1.99 ? I use egcs-1.1.1 since the weekend and
it seems to work fine. I had no trouble to build some shared
lib stuff like in the latest jade or sgml-tools. This packages
didn't compile with older version I tried (also Gary's egcs-1.1b),
but that were generell compiler issues, I think.

But on the other side I also tried to run the SeaMonkeyBrowser
(Mozilla) from recent cvs-sources. Building went fine, but the
beast didn't run. I get only a simple "Aborted" message on the
console and it seems to crash somewhere in the startup code.
So maybe this is somehow related ?

Had someone luck to run a recent version of Mozilla at all on
LinuxPPC ?

Thanks,
Ralf




[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: EGCS 1.1.1 FYI

From: <hidden>
Date: 1998-12-08 04:28:30

FYI, I get the same problem with glibc-2.0.104... I have an strace, last
50 lines are attached... No time to do anything anymore... <sigh>
								-Rob

On Mon, 7 Dec 1998, Ralf Weidemann wrote:
Date: Mon, 7 Dec 1998 23:22:42 +0100 (CET)
From: Ralf Weidemann <redacted>
To: LinuxPPC Dev <redacted>
Subject: Re: EGCS 1.1.1 FYI 

quoted
quoted
quoted
quoted
quoted
"David" == David Edelsohn [off-list ref] writes:
"Paul J Schinder" writes:
    Paul> So are Gary Thomas' patches still necessary?

    David> 	The trampoline patch now has become a shared library
    David> compatibility issue for glibc-1.99 support.  It only is
    David> necessary until LinuxPPC cuts over to glibc-2.1 which will
    David> require other binary incompatible changes at the same time.

Can someone clarify where the problem is exact with native
egcs and libc-1.99 ? I use egcs-1.1.1 since the weekend and
it seems to work fine. I had no trouble to build some shared
lib stuff like in the latest jade or sgml-tools. This packages
didn't compile with older version I tried (also Gary's egcs-1.1b),
but that were generell compiler issues, I think.

But on the other side I also tried to run the SeaMonkeyBrowser
(Mozilla) from recent cvs-sources. Building went fine, but the
beast didn't run. I get only a simple "Aborted" message on the
console and it seems to crash somewhere in the startup code.
So maybe this is somehow related ?

Had someone luck to run a recent version of Mozilla at all on
LinuxPPC ?

Thanks,
Ralf


Re: EGCS 1.1.1 FYI

From: David T. McWherter <hidden>
Date: 1998-12-08 10:42:34

I've tried compiling the mozilla code too, but it aborts due
to a failing dynamic linking call in normal startup code...
it's particularly odd, as it's trying to dlopen a file with
a name parameter of NULL, and it's not even trying to hide it
(the last code I saw had a dlopen(NULL,...).  I'm *guessing*
that on other Linux platforms, such code is well-defined, 
perhaps to use the "current executable file" to do the opening,
or something...but I'm not sure...still kinda odd to me...

-David

On Mon, 7
Dec
1998 hagopiar@vuser.vu.union.edu wrote:
FYI, I get the same problem with glibc-2.0.104... I have an strace, last
50 lines are attached... No time to do anything anymore... <sigh>
								-Rob

On Mon, 7 Dec 1998, Ralf Weidemann wrote:
quoted
Date: Mon, 7 Dec 1998 23:22:42 +0100 (CET)
From: Ralf Weidemann <redacted>
To: LinuxPPC Dev <redacted>
Subject: Re: EGCS 1.1.1 FYI 

quoted
quoted
quoted
quoted
quoted
"David" == David Edelsohn [off-list ref] writes:
"Paul J Schinder" writes:
    Paul> So are Gary Thomas' patches still necessary?

    David> 	The trampoline patch now has become a shared library
    David> compatibility issue for glibc-1.99 support.  It only is
    David> necessary until LinuxPPC cuts over to glibc-2.1 which will
    David> require other binary incompatible changes at the same time.

Can someone clarify where the problem is exact with native
egcs and libc-1.99 ? I use egcs-1.1.1 since the weekend and
it seems to work fine. I had no trouble to build some shared
lib stuff like in the latest jade or sgml-tools. This packages
didn't compile with older version I tried (also Gary's egcs-1.1b),
but that were generell compiler issues, I think.

But on the other side I also tried to run the SeaMonkeyBrowser
(Mozilla) from recent cvs-sources. Building went fine, but the
beast didn't run. I get only a simple "Aborted" message on the
console and it seems to crash somewhere in the startup code.
So maybe this is somehow related ?

Had someone luck to run a recent version of Mozilla at all on
LinuxPPC ?

Thanks,
Ralf


-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
       David T. McWherter     dtm@waterw.com


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Compiler porblems

From: Giovanni Liotine <hidden>
Date: 1998-12-09 12:36:33

Hi all
I've some problem compiling c++ apps under linuxppc with egcs.1.0.2
prerelease:
during compiling this code 
"#include <iostream.h>
 main
    {
    } "

gcc output are a long series of warnings: invalid type 'void *' for
default argument to 'ostream *'

When compiling some applications (that compile fine with gcc 2.8.1 under
Intel/Linux) like MidsEye gcc results in internal compiler error, e.g:

In method 'void MatrixImage <float>::drawLine(int, int, int, int, float)
Internal compiler error.

Is it a compiler bug or what?
Any suggestion? Note that this code compile under Intel/Linux box.

Thanks
Gianni. 


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

RE: Compiler porblems

From: Gary Thomas <hidden>
Date: 1998-12-11 12:40:26


On 09-Dec-98 Giovanni Liotine wrote:
Hi all
I've some problem compiling c++ apps under linuxppc with egcs.1.0.2
prerelease:
during compiling this code 
"#include <iostream.h>
 main
    {
    } "

gcc output are a long series of warnings: invalid type 'void *' for
default argument to 'ostream *'

When compiling some applications (that compile fine with gcc 2.8.1 under
Intel/Linux) like MidsEye gcc results in internal compiler error, e.g:

In method 'void MatrixImage <float>::drawLine(int, int, int, int, float)
Internal compiler error.

Is it a compiler bug or what?
Any suggestion? Note that this code compile under Intel/Linux box.
Try the latest EGCS-1.1.1 available at:
  ftp://ftp.linuxppc.org/pub/gary/redhat/RPMS/ppc
Pick up the 'egcs-*1.1-1b*' packages.  These are suitable for existing
Linux/PPC (pre GLIBC-2.1.xx) systems.

------------------------------------------------------------------------
Gary Thomas                              |
email: gdt@linuxppc.org                  | "Fine wine is a necessity of
   ... opinions expressed here are mine  |        life for me"
       and no one else would claim them! |
                                         |      Thomas Jefferson
------------------------------------------------------------------------



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

Re: Compiler porblems

From: <hidden>
Date: 1998-12-12 00:54:55

Works fine for me with egcs 1.1.1 and glibc-2.1.104 (linuxppc-pre5 or
such). That is, after I changed that from "main" to "main ()" :-)
								-Rob H.

On Wed, 9 Dec 1998, Giovanni Liotine wrote:
Date: Wed, 9 Dec 1998 13:36:33 +0100 (CET)
From: Giovanni Liotine <redacted>
To: linuxppc-dev@lists.linuxppc.org
Cc: hagopiar@vuser.vu.union.edu, Ralf Weidemann <redacted>,
     linuxppc-dev@lists.linuxppc.org
Subject: Compiler porblems

Hi all
I've some problem compiling c++ apps under linuxppc with egcs.1.0.2
prerelease:
during compiling this code 
"#include <iostream.h>
 main
    {
    } "

gcc output are a long series of warnings: invalid type 'void *' for
default argument to 'ostream *'

When compiling some applications (that compile fine with gcc 2.8.1 under
Intel/Linux) like MidsEye gcc results in internal compiler error, e.g:

In method 'void MatrixImage <float>::drawLine(int, int, int, int, float)
Internal compiler error.

Is it a compiler bug or what?
Any suggestion? Note that this code compile under Intel/Linux box.

Thanks
Gianni. 

[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help