CC 5.5 compiler flag to issue 64bit porting warnings on sparc-solaris

10 More Discussions You Might Find Interesting

1. Solaris

SUNWi1cs SUNWi15cs packages for solaris 10 64bit sparc

hi, i need to install SUNWi1cs and SUNWi15cs packages for solaris 10 sparc 64 bit , where can i download these packages . Thanks .

2. Solaris

Where to download solaris 10 for sparc 64bit?

hi all I just got a sun blade 2000 server for free. I need to load a solaris 10 for sparc OS to it. the memory inside the box is 5gb. the cup is SUNW,UltraSPARC-III+ (1200 MHz @ 8:1, 8 MB). so my questions is 1. do I need to install a 64bit os or a 32bit os? 2. where can I download the...

3. UNIX for Dummies Questions & Answers

Changing colors for compiler errors/warnings

Hi, I am using GNU unix. And running a bash shell. Can anyone please tell me what is the command for changing the color of the compiler error/warning messages on the console. I think it is in .bashrc and do not know how. Thanks Pink

4. UNIX for Advanced & Expert Users

Changing colors for compiler errors/warnings

5. Solaris

Compiler - 32bit or 64bit?

Hi Gurus, I need to check whether the compiler installed in my system supports 64bit compilation. Server - Sun fire v490 OS - Solaris 5.9 Processor - Sparcv9 (64bit) Install Directory - /opt/SUNWSpro Compiler Model - Sun Forte C Compiler. My development team is claiming that there...

6. Solaris

Apcahe2 64bit on solaris 10 sparc!

Hi, i'm trying to compile apache 2.2.13 on solaris 10 sparc as 64bit and for some reason its always compiled as 32bit! i know it can be done cause i've already done it before, so i'm not sure what am i doint wronghttp://forums.digitalpoint.com/images/smilies/frown.gif i've edit /.profile...

7. Solaris

Solaris SPARC 10 64Bit -JDK Installation 1.6.05

In Sun Solaris 10, not able to create the key. JDK 1.6 Installed & PATH & JAVA_HOME both are referred to jdk 1.6. It is showing the belwo error Error: wrap() failed java.security.InvalidKeyException: wrap() failed at sun.security.pkcs11.P11RSACipher.engineWrap(P11RSACipher.java:395) at...

8. Solaris

32bit / 64bit issue with x86 solaris

i have solaris 10 x86 64bit installed on my pc (dell 3100). i then decided to move my hard drive to another pc (dell 4600). I noticed that each time i boot up, the OS show as 32 bit (instead of 64bit) and i can't even get past this stage to the login page. when i moved it back to dell 3100 it...

9. UNIX for Dummies Questions & Answers

How to suppress minor C compiler warnings

Hi, I develop code using a few different solaris platforms. I've recently moved to SunOS 5.10 using the following c compiler. Sun C++ 5.9 SunOS_sparc Patch 124863-01 2007/07/25 On this box and these versions I get hundreds of warnings that do not appear of the earlier solaris/c versions. ...

10. Programming

C compiler to build Sparc/Solaris binaries on Linux

Just that the Subject says. I am looking for a C compiler for Linux x86 that will allow me to compile a C source code file and the resulting binary will be able to run on a Sparc running Solaris. Thanks.

LEARN ABOUT MOJAVE

apache2::porting

install::TempContent::Objects::mod_perl-2.0.9::docs::apiUseraContribuinstall::TempContent::Objects::mod_perl-2.0.9::docs::api::Apache2::porting(3)

NAME

       Apache2::porting -- a helper module for mod_perl 1.0 to mod_perl 2.0 porting

Synopsis
	 # either add at the very beginning of startup.pl
	 use Apache2::porting;

	 # or httpd.conf
	 PerlModule Apache2::porting

	 # now issue requests and look at the error_log file for hints

Description
       "Apache2::porting" helps to port mod_perl 1.0 code to run under mod_perl 2.0. It doesn't provide any back-compatibility functionality,
       however it knows to trap methods calls that are no longer in the mod_perl 2.0 API and tell what should be used instead if at all. If you
       attempts to use mod_perl 2.0 methods without first loading the modules that contain them, it will tell you which modules you need to load.
       Finally if your code tries to load modules that no longer exist in mod_perl 2.0 it'll also tell you what are the modules that should be
       used instead.

       "Apache2::porting" communicates with users via the error_log file. Everytime it traps a problem, it logs the solution (if it finds one) to
       the error log file. If you use this module coupled with "Apache2::Reload" you will be able to port your applications quickly without
       needing to restart the server on every modification.

       It starts to work only when child process start and doesn't work for the code that gets loaded at the server startup. This limitation is
       explained in the Culprits section.

       It relies heavily on "ModPerl::MethodLookup".  which can also be used manually to lookup things.

Culprits
       "Apache2::porting" uses the "UNIVERSAL::AUTOLOAD" function to provide its functionality. However it seems to be impossible to create
       "UNIVERSAL::AUTOLOAD" at the server startup, Apache segfaults on restart. Therefore it performs the setting of "UNIVERSAL::AUTOLOAD" only
       during the child_init phase, when child processes start. As a result it can't help you with things that get preloaded at the server
       startup.

       If you know how to resolve this problem, please let us know. To reproduce the problem try to use an earlier phase, e.g.
       "PerlPostConfigHandler":

	 Apache2::ServerUtil->server->push_handlers(PerlPostConfigHandler => &porting_autoload);

       META: Though there is a better solution at work, which assigns AUTOLOAD for each class separately, instead of using UNIVERSAL. See the
       discussion on the dev list (hint: search the archive for EazyLife)

See Also
       mod_perl 2.0 documentation.

Copyright
       mod_perl 2.0 and its core modules are copyrighted under The Apache Software License, Version 2.0.

Authors
       The mod_perl development team and numerous contributors.

perl v5.18.2							    2install::TempContent::Objects::mod_perl-2.0.9::docs::api::Apache2::porting(3)

Solaris