-
Notifications
You must be signed in to change notification settings - Fork 539
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solaris 7+gcc 2.95.1+Perl 5.005_03: core dumps #490
Comments
From sn@neopoly.de[Please enter your report here] I just setup a new Ultra 10 (clone): Installed a fresh Solaris 7 (german). I applied all the latest solaris patches as of 09/03/1999. I downloaded gcc 2.95.1 from sunfreeware.com. I got perl 5.005_03 from CPAN (I built it successfully on Linux). I compiled it with "./configure -des -Dcc=gcc". # ./perl harness comp/cpp.t ?? ?? % ?? Here's the output from gcc -v: Unfortunately, I do not have another C compiler. # env Here's the output of "perl -V" when I'm in the "t" directory: Characteristics of this binary (from libperl): |
From [Unknown Contact. See original ticket]sn@neopoly.de [sn@neopoly.de] quoth: Since I justt installed 2.95.1 recently and have Solaris 7 I had to SunOS chaos 5.7 Generic_106541-05 sun4u sparc SUNW,Ultra-1 gcc version 2.95.1 19990816 (release) I was able to build and test pe arl without trouble using the defaults as Run configure again and see if you notice anything weird. I noticed that Of course, there is always the possibility that sun broke something on the |
From [Unknown Contact. See original ticket]Nick Ing-Simmons [nick@ing-simmons.net] quoth: It wouldn't be the first time and certainly not the last. *>>> Dimitri Papadopoulos <dpo@club-internet.fr> writes: This patch, according to sunsolve, was released in January. It wasn't It doesn't seem to effect sparcworks though :) e. |
From [Unknown Contact. See original ticket]Happyfunball <elaine@chaos.wustl.edu> writes:
Now you mention it there was talk recently on gcc list that one patch set
-- |
Migrated from rt.perl.org#1332 (status was 'resolved')
Searchable as RT1332$
The text was updated successfully, but these errors were encountered: