Another Expired Certificate Error Thread

I've searched all over, and apologize in advance if there is already an answer for this.
I'm using the Symbian Belle OS and am running into the old problem of expired certificate errors when trying to install certain apps. The solution to this was to change the date on the phone so it coincides with that of the application you're trying to install. But that solution is no longer working.
Does anyone know of a workaround?

I did every year all the way back to 2000 but no luck
I also tried sites that will convert the .sis file into one with a valid certificate, but that fails as well. When going down that road it just tells me the certificate is not valid or that the author cannot be verified (instead of expired).

Similar Messages

5800 XM "Expired Certificate" error message

For people who own a Nokia 5800 XM, the error message of "Expired Certificate" when downloading applications onto the device will be mean you cannot load on new apps, which can be frustrating.
Firstly you should try to update the firmware on your phone by 1 of 3 ways.
Using FOTA (Firmware Over The Air). Another thread of mine will explain this in detail. You can find it here.
Downloading Nokia Software Updater(NSU) and connecting your 5800 to the computer using a data cable.
Taking the handset to a Nokia Care point if you do not want to try the above 2 options.
**NOTE: Always be sure to make a back up of your personal details that are held on the phone as updating firmware will most likely delete any data left on the phone.
If you have used FOTA or NSU to update your firmware, or there is no new update available then doing the following will work and will allow you to install new applications without the expired certificate error message.
With the phone switched on, press the power button key once.
Scroll down to and select "Remove E: Memory Card".
Select Yes to remove the memory card.
Press OK and remove memory card from phone.
Press the Dialler on the main screen.
Type *#7370#
Enter security code. Default is 12345 unless it has been changed.
The phone will reset, wait for this to complete and power back on.
Select your country and type in the correct time and date.
Wait for the phone to complete its configurations, you may receive "My Nokia" or tutorial messages.
Power off phone.
Insert the memory card.
Power on the phone.
Wait for the phone to install any pre-loaded content from the memory card
Phone is ready to install applications, without "Expired Certificate" error message.
I have done the above myself and downloaded the PDF reader from the "Download" application from within the handset and it installed with no error after these steps.
I hope this helps.
My posts are my opinion and in no way the direct views of Nokia.
If my posts are helpful, please give me some KUDOS using the green star on the left.

try to sign your app(s) through Opda site.
If you want to thank someone, just click on the blue star at the bottom of their post

ISE 1.2 / WLC 5508 EAP-TLS expired certificate error, but wireless still working

Hi I have a customer that we've deployed ISE 1.2 and WLC 5508s at. Customer is using EAP-TLS with and everything appears to setup properly. Users are able to login to the network and authenticate, however, frequently, I'm getting the following error in ISE authentication logs:
12516 EAP-TLS failed SSL/TLS handshake because of an expired certificate in the client certificates chain
OpenSSL messages are:
SSL alert: code=Ox22D=557 : source=local ; type=fatal : message="X509
certificate ex pi red"'
4 727850450.3616:error.140890B2: SS L
rOYbne s: SSL 3_ G ET _CL IE NT _CE RT IF ICAT E:no ce rtific ate
relurned: s3_ srvr.c: 272 0
I'm not sure if this is cosmetic or if this is something that I should be tracking down. System isn't in full production yet, but every client seems to be working and there is no expired cert in the chain. Any ideas what to check?

Hello Dino,
thanks very much for your reply.
The client uses a machine-certificate, the PKI is not a microsoft one, but a third party PKI. The certificate is fresh and valid, the root-cert is installed and checked to be validated against it for the login.
Clock is correct too. The same setup works flawlessly in Windows 7 and XP.
EKU is set on the certificate (1.3.6.1.5.5.7.3.2)
I suspect the cert-setup itself, but don't get a clue where this might stuck...
Björn

'Certificate Expired/ Certificate Error' in Nokia ...

I have bought a new Nokia N91 8GB. But when I try to instal any application or theme. I get an error saying 'Certificate Expired' or 'Certificate Error. Contact Application Supplier'. Please let me know how this can be resolved.

Hi ismaniyar
Firstly go to Application Manager > Options > Settings and set "Online Certificate check" = Off and Software Installation = All.
Secondly try resetting date on phone to January 1 2007 first and if that doesn't work try December 31 2006 as Symbian certificate may have expired on theme; reset date after installation.
The actual date is a case of trial and error and previously quoted dates may no longer apply due to the passage of time.
Happy to have helped forum in a small way with a Support Ratio = 37.0

Expired certificate error for language packages

I wish to inform the nokia authority,that the language package(UK english Martin) provided for Message Reader app (symbian belle) is showing 'CERTIFICATE EXPIRED' error ,whenever I tried to install the language pack.
I request the authority to kindly extend the certificate period more so that all user can use those packages.
I downloaded the language pack from:
http://www.nokia.com/global/support/text-to-speech/
Handset model : NOKIA 701

Same problem with US english language packs, expired certificate despite the fact that I just downloaded it from Nokia a few days ago. So please Nokia renew the certificate for the Nokia super 701 Text To Speech Language packs.
Handset Model: Nokia super 701 FP2

Expired certificate error

when try to install any application on my phone it tell me that you have expired certificate. So what can i do to have the new certificate?
Moderator's note: We have amended the title of this post as it was moved from another board.

If the app is asking for a licence key, it means that you have most likely installed a free trial which may expire after a certain time or restrict use of certain features until the full version is purchased.
You can usually make the purchase through the app itself, otherwise please see the web site of the app producer or the store from where you downloaded the app.
If this or any post answers your question, please remember to help others by pressing the 'Accept as solution' button.

Another Log & Transfer Error Thread

I have read over all log and transfer threads. I have done everything I could find that was previously described in other threads by deleting the pref. files and all that jazz. Followed everything in this thread http://discussions.apple.com/thread.jspa?threadID=2672530#NoData . I am certain that all my setting are set correctly. I am still running across the error when transferring telling me the clip has no data. My specs are the following:
Camera: Sony HDR-AX2000
Filming in 1080i60 (all setting in FCE reflect this)
I do not know what else to do to fix this problem. I am transferring directly from the SD card plugged into the stock port in my computer. I have not tried transferring with my camera plugged into USB 2.0 but am pretty sure these are both the same methods, as I have read. Am I missing something? Any help would be appreciated. Please let me know if there is any vital information I may have left out to get proper help.
-Thx

Hi -
Don't know if this is repeating advice you have already applied but:
1) Make sure you are editing with the latest update to FCE, FCE 4.0.1
2) Make sure you are recording HD with your camera. SD will not transfer by Log and Transfer - only HD.
3) There are reports of difficulties using Log and Transfer if you Camera Storage Card also contain clips in other video formats and/or if it contains still images.
4) Open the Log and Transfer window.
Click on the little gear shaped icon towards the upper middle of the L&T window
Select Preferences from the drop down menu.
When the preference window opens, set the AVCHD Plug-In audio format to Plain Stereo.
5) When you are navigating to the Storage Card, navigate to the top level of the card only. Do not drill down into the card structure. Log and Transfer needs to see the Card Structure to ingest properly.
MtD

Expired certificate problem

I 've recently bought new Nokia 5530 express music. i found out that the General icon under themes setting are not functioning. Also, I can't install any application. Always failed and expired certificate message are popping out.
Appreciate any advice

are you trying to download from Ovi store? if you are and you are having expired certificate error message, change the date on your mobile device to January of 2007 or January of 2009 and try these steps: 1. Close the Ovi Store client 2. Open your mobile browser and go to the following URL: http://contacts.ovi.com/dist/Verisign_Class_3_Public_Primary_Certification_Authority.der 3. Select Save to download the certficicate to your device 4. Lauch the Ovi Store client.

URGENT!! ERROR WITH EXPIRED CERTIFICATE USING JDK 1.4.2.05

Hi,
I have created a client/server application with SSL and have found the following problem.
I have made these two tests:
1) jdk 1.4.2.03 --> the certificate is expired, I obtain this exception "No trusted certificate found". it's ok
2) jdk 1.4.2.06 --> the certificate is expired, no error occurs. WHY?????
Someone can help me?
Gianna

The problem is not the expired certificate! I know that it is expired, but I don't understand why using jdk 1.4.2.05 this certificate is not recognize invalid.
With this jdk the channel is created. Using jdk 1.4.2.03 instead the certificate was recognized expired and the channel is not created between client and server.
For me the correct behavior has with the old version of the JDK and not the new.
WHY?????

Certificate error/expired

Helo there again. pls help me guys bout my friends phone problem.i try to help him yesterday to download some application like youtube application but the problem is when i try to open the program it said 'feature not supported' also i download a game but when i open it said something like expired i forgot exactly whats the error.i think the only problem is the bout certificates and i dont know how to fix hope you can help me.
Btw his phone is nokia e61i. Tnx!
NOKIA E52-1
034.001
RM-469

for expired certificate change date back by one year install the app and return date to correct date,the you tube app must not be compatible with that phone
If i have helped at all a click on the white star below would be nice thanks.
Now using the Lumia 1520

Anyconnect VPN - Expired certificate causing Java error

Hello,
Since April 4th 2015 Java has been blocking the process of installing AnyConnect via web-deployment (see attached screenshot). It indicates there is an expired certificate with these details:
Issuer CN=VeriSign Class 3 Code Signing 2010 CA,
OU=Terms of use at https://www.verisign.com/rpa (c)10,
OU=VeriSign Trust Network,
O="VeriSign, Inc.",
C=US
Validity [From: Wed Jan 02 19:00:00 EST 2013,
To: Sat Apr 04 19:59:59 EDT 2015] <-----------------------------
Subject CN="Cisco Systems, Inc.", <-----------------------------
OU=Digital ID Class 3 - Microsoft Software Validation v2,
O="Cisco Systems, Inc.",
L=Boxborough,
ST=Massachusetts,
C=US
This certificate is not seen when entering 'show crypto ca cert' on the ASA -- it is NOT our certificate, as it is issued to "Cisco Systems, Inc", and it has clearly expired.
We are running the ASA software 9.1.6 and this behavior happens (at least) with the three latest versions of Java.
Is anyone else having this issue? Is there anything that can be done (server-side) to resolve this?
Thanks in advance...

I think it is possible to use same digital certificate. You can specify whether you want users to authenticate using AAA with a username and password or using a digital certificate (or both). When you configure certificate-only authentication, users can connect with digital certificate and are not required to provide a user ID and password.

SSLSocket created with expired certificates

The tests documented here were performed using Sun JSSE 1.0.2.
Server
I have installed TOMCAT and configured it for SSL by following the instructions detailed in the following link:
http://jakarta.apache.org/tomcat/tomcat-3.3-doc/tomcat-ssl-howto.html
NB: The system date was set back by more than three months to ensure that the certificate contained in the store is now expired.
Client
I have created a simple java client test program that attempts to create an SSLSocket connecting to the TOMCAT SSL port.
The code is listed below:
SSLSocketFactory factory = (SSLSocketFactory)SSLSocketFactory.getDefault();
SSLSocket socket = (SSLSocket)factory.createSocket("127.0.0.1", 8443);
System.out.println("Establishing SSL socket connection");
* register a callback for handshaking completion event
socket.addHandshakeCompletedListener(
new HandshakeCompletedListener() {
public void handshakeCompleted(HandshakeCompletedEvent event) {
     System.out.println("Handshake finished!");
     System.out.println("\t CipherSuite:" + event.getCipherSuite());
     System.out.println("\t SessionId " + event.getSession());
     System.out.println("\t PeerHost " + event.getSession().getPeerHost());
socket.startHandshake();
socket.close();
System.out.println("Established SSL socket connection");
Tests
The test program was run as follows (NB: With the system date set correctly to the current date):
Test 1
With no parameters passed.
Result: This produces an untrusted server cert chain error. This happens because the truststore information has not been supplied. This result is as expected.
Test 2
With the following parameters:
-Djavax.net.debug=ssl:keymanager
-Djavax.net.ssl.trustStore= set to the location of a truststore file containing the same EXPIRED server certificate mentioned above
Result: This does not produce any errors and the socket is created successfully and the handshake completes successfully. As the truststore at the client (i.e. the java test program) and the keystore at the server (i.e. SSL enabled TOMCAT) both contain the same EXPIRED certificate it was expected this would result in a failure to create the SSLSocket. The debug trace that is output does indeed show that the certificate has expired yet somehow the connection is still being made.
It should be noted that test 2 has been run on numerous occasions in the past and has previously given the expected result. That is to say, a failure to create the SSLSocket with an error message stating that the certificate had expired. Nothing appears to have changed in the environment in which these tests are being run that should cause them to start to fail now.
Has anyone seen this strange behaviour before?

There are fellow sufferers...
http://forum.java.sun.com/thread.jspa?threadID=560690&tstart=0
I too noticed this.
I've a simple 20 line SSL server and SSL client and can reproduce this behaviour.
ie. trying with an good cert, it exchanges data, with a bad cert, I get an exception, and with
an expired cert, it exchanges data when I expect this last one to fail.
I dont know what the solution is but if I were to hazard a guess, I'd say maybe I need
to subclass the TrustManager? or maybe set some policy somewhere.
In the meantime, I've just invalidated it manually.
ie. on startup or whenever appropriate, I do the following...
KeyStore keystore = null;
// Load the keystore in the user's home directory
FileInputStream is = new FileInputStream(filename);
keystore = KeyStore.getInstance(KeyStore.getDefaultType());
keystore.load(is, password.toCharArray());
is.close();
for (Enumeration ea = keystore.aliases(); ea.hasMoreElements();) {
String alias = (String) ea.nextElement();
// Get certificate
java.security.cert.X509Certificate cert =
(java.security.cert.X509Certificate) keystore.getCertificate(alias);
try {
cert.checkValidity();
} catch (java.security.cert.CertificateException e) {
System.out.println( "Invalid Certificate for " + alias );
keystore.deleteEntry(alias);
ie. I remove the offending cert from the truststore...
This is a stop-gap measure till I figure out what to do instead.
Hope this helps...
Chai

N96 certificate errors

Hi all,
Apologies if this is in the wrong part of the site, brand new to this forum.
I've just received my nokia n96. I've tried to install a few programs downloaded from legit websites and I keep getting alot of 'Certificate error - contact application supplier' errors.
I've seen a couple of things about hacking the phones firmware and stuff but no clear concise solution.
Can anyone on here help me?

craigkilner1986 wrote:
Thanks,
I've have messaged the author of the app and found another version which is currently being signed so fingers crossed it will work.
I'm seeing alot of forums suggesting the need to hack the phone in order to get most of the apps working. Why can the phone not just accept software?!?!?
Frustrating when you want to install something and such things as stupid as certificates won't let you.
You don't need to hack a phone to get "most" apps working. It might be most of the ones that certain people have tried, or it might be that people only notice the installations that cause problems, or it might be that very old apps have expired certificates, but most new apps should install correctly on phones with which they are officially compatible. Most new apps should also have much longer certificates than they used to (10+ years instead of 2 years), so the expired certificate problem should go away.
Some people have to hack phones to use apps which aren't officially compatible, but what do you expect if an app is being put onto a phone which it wasn't written for?
The reason there are certificates is to stop malware.
Malware on phones can be potentially a lot more troublesome than malware on computers, because almost all phones have a SIM card which effectively works as a credit card. That would in theory allow malware to basically steal money from you through your phone bill by connecting to premium or foreign numbers, possibly without you noticing. There's other stuff malware can do too.
Some people will say certificates aren't the best answer to preventing malware, and that's an area of big debate, but I'm just explaining why there are certificates.

Certificate error when try to send mail

Masters,
First of all sorry for my poor english. Im not IT specialist, so please ...
I need help to fix my problem. I know there are many post with this but i can't figure out.
We had a working enviroment with no certificate issue.
I tried to set the Outlook Anywhere, and so i messed up something. Now if user open outlook and send / or reply a mail got a certificate error message. I don't care Outlook Anyhere anymore but i need to fix my issue...
I have not enough reputation point, so i can't attach image. I used Snag to attach picture.
Certification error message:
This is how exchange certs looks like:
The problem is occure when start outlook and start or reply a mail. Certfication error pop-up, and inside the message windows on the Certification Chain tab i see: "mydomain".local
When i try to configure outlook anywhere i create and enable new certificate. I think when i did this i have to allow owerrite some service... I deleted that certification already.
If i install the cert to root CA, then works ok. But i don't want to install it all our server, because its workd earlier. How can i fix this?
Thank you

Hello,
First of all thank you for helpin' me.
I do not want to use outlook anywhere anymore, but now i know need 3rd certf for work...
Only i want to get back everything.
I know if i install to root CA than pop up disappear (i test this one of our server) but because earlier we have no installed this cert...so i don't understand what should i did...
1. i installed a new self-sign certificate and associate service SMTP for it.
2. after all test failed i decided to delete this cert...
3. now outlook get pop up with certificated issued by: ourcompany.local
- i did not seen any certificate in the certificate store with this name...
Now i test it again and the no pop up in outlook?! What happend? I check and the mentioned certificate not in the store?!
If i delete a certificate and assign service to another one, how many time need to affect this to the enviroment?
Thank you

"error: thread-local storage not supported for this target"

I have a program that uses the __thread specifier, to be run on a Solaris 9/UltraSprac.
I am not able to compile it using gcc 3.4.4 or 4.0.4, it emits the msg "error: thread-local storage not supported for this target".
xz@gamera% gcc -v -Wall -D_REENTRANT -c -o func_stack.o func_stack.c
Reading specs from /opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/specs
Configured with: ../srcdir/configure --prefix=/opt/gcc/3.4.4 --disable-nls
Thread model: posix
gcc version 3.4.4
/opt/gcc/3.4.4/libexec/gcc/sparc-sun-solaris2.8/3.4.4/cc1 -quiet -v -D_REENTRANT -DMESS func_stack.c -quiet -dumpbase func_stack.c -mcpu=v7 -auxbase-strip func_stack.o -Wall -version -o /var/tmp//cc0poHSN.s
ignoring nonexistent directory "/usr/local/include"
ignoring nonexistent directory "/opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/../../../../sparc-sun-solaris2.8/include"
#include "..." search starts here:
#include <...> search starts here:
/opt/gcc/3.4.4/include
/opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/include
/usr/include
End of search list.
GNU C version 3.4.4 (sparc-sun-solaris2.8)
        compiled by GNU C version 3.4.4.
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
func_stack.c:16: error: thread-local storage not supported for this target
func_stack.c:17: error: thread-local storage not supported for this target
func_stack.c:19: error: thread-local storage not supported for this target
xs@gamera% gcc -v -D_REENTRANT -c -o func_stack.o func_stack.c
Using built-in specs.
Target: sparc-sun-solaris2.9
Configured with: /net/clpt-v490-0/export/data/bldmstr/20070711_mars_gcc/src/configure --prefix=/usr/sfw --enable-shared --with-system-zlib --enable-checking=release --disable-libmudflap --enable-languages=c,c++ --enable-version-specific-runtime-libs --with-cpu=v9 --with-ld=/usr/ccs/bin/ld --without-gnu-ld
Thread model: posix
gcc version 4.0.4 (gccfss)
/pkg/gcc/4.0.4/bin/../libexec/gcc/sparc-sun-solaris2.9/4.0.4/cc1 -quiet -v -I. -iprefix /pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/ -D__sparcv8 -D_REENTRANT -DMESS func_stack.c -quiet -dumpbase func_stack.c -mcpu=v9 -auxbase-strip func_stack.o -version -m32 -o /tmp/ccjsdswh.s -r /tmp/cc2w4ZRo.ir
ignoring nonexistent directory "/pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/../../../../sparc-sun-solaris2.9/include"
ignoring nonexistent directory "/usr/local/include"
ignoring nonexistent directory "/usr/sfw/lib/gcc/sparc-sun-solaris2.9/4.0.4/include"
ignoring nonexistent directory "/usr/sfw/lib/../sparc-sun-solaris2.9/include"
#include "..." search starts here:
#include <...> search starts here:
/pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/include
/usr/sfw/include
/usr/include
End of search list.
GNU C version 4.0.4 (gccfss) (sparc-sun-solaris2.9)
        compiled by GNU C version 4.0.4 (gccfss).
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
func_stack.c:16: error: thread-local storage not supported for this target
func_stack.c:17: error: thread-local storage not supported for this target
func_stack.c:19: error: thread-local storage not supported for this targetJust as comparison, the corresponding output of compiling another file which does not have __thread declaration is as follows:
xz@gamera% gcc -v -Wall -D_REENTRANT -c -o common.o common.c
Reading specs from /opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/specs
Configured with: ../srcdir/configure --prefix=/opt/gcc/3.4.4 --disable-nls
Thread model: posix
gcc version 3.4.4
/opt/gcc/3.4.4/libexec/gcc/sparc-sun-solaris2.8/3.4.4/cc1 -quiet -v -D_REENTRANT -DMESS common.c -quiet -dumpbase common.c -mcpu=v7 -auxbase-strip common.o -Wall -version -o /var/tmp//cc4VxrLz.s
ignoring nonexistent directory "/usr/local/include"
ignoring nonexistent directory "/opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/../../../../sparc-sun-solaris2.8/include"
#include "..." search starts here:
#include <...> search starts here:
/opt/gcc/3.4.4/include
/opt/gcc/3.4.4/lib/gcc/sparc-sun-solaris2.8/3.4.4/include
/usr/include
End of search list.
GNU C version 3.4.4 (sparc-sun-solaris2.8)
        compiled by GNU C version 3.4.4.
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
/usr/ccs/bin/as -V -Qy -s -xarch=v8 -o common.o /var/tmp//cc4VxrLz.s
/usr/ccs/bin/as: Sun WorkShop 6 update 2 Compiler Common 6.2 Solaris_9_CBE 2001/04/02Note that the last 2 lines seem to suggest that a Sun assembler is used as the back-end of gcc. I am not sure whether the failure to compile the first file (with __thread) was due to the incompatibility of this Sun assembler. In the first case, the error msg was emitted before these 2 lines are printed.
I further read a post about gcc 3.3.3's inability to compile code that has __thread in it, on a HP-UX 11.11: http://forums12.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1216595175060+28353475&threadId=1148976 The conclusion seems to suggest that "the 2.17 GNU assembler did not support thread local storage" and gcc sees that and thus disallows TLS.
If the assembler is the culprit, then does anyone know whether this "Sun WorkShop 6 update 2" assembler in my installation can work with TLS? And how come a Sun assembler becomes the back-end of gcc? I read that gas (the GNU assembler) is the default backend of gcc. (How) can one specify the assembler to be used for gcc?
As an aside, I am able to compile my file on this same Solaris 9/UltraSparc platform using the Sun Studio 12 C Compiler:
xz@gamera% cc -V -# -D_REENTRANT -c -o func_stack.o func_stack.c
cc: Sun C 5.9 SunOS_sparc Patch 124867-01 2007/07/12
### Note: NLSPATH = /pkg/SUNWspro/12/prod/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/pkg/SUNWspro/12/prod/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat
###     command line files and options (expanded):
### -c -D_REENTRANT -V func_stack.c -o func_stack.o
/pkg/SUNWspro/12/prod/bin/acomp -xldscope=global -i func_stack.c -y-fbe -y/pkg/SUNWspro/12/prod/bin/fbe -y-xarch=generic -y-xmemalign=8i -y-o -yfunc_stack.o -y-verbose -y-xthreadvar=no%dynamic -y-comdat -xdbggen=no%stabs+dwarf2+usedonly -V -D_REENTRANT -m32 -fparam_ir -Qy -D__SunOS_5_9 -D__SUNPRO_C=0x590 -D__SVR4 -D__sun -D__SunOS -D__unix -D__sparc -D__BUILTIN_VA_ARG_INCR -D__C99FEATURES__ -Xa -D__PRAGMA_REDEFINE_EXTNAME -Dunix -Dsun -Dsparc -D__RESTRICT -xc99=%all,no%lib -D__FLT_EVAL_METHOD__=0 -I/pkg/SUNWspro/12/prod/include/cc "-g/pkg/SUNWspro/12/prod/bin/cc -V -D_REENTRANT -c -o func_stack.o " -fsimple=0 -D__SUN_PREFETCH -destination_ir=yabe
acomp: Sun C 5.9 SunOS_sparc Patch 124867-01 2007/07/12Interestingly, the output no longer mentions the "/usr/ccs/bin/as: Sun WorkShop 6 update 2" assembler.

Just as another comparison, I compiled a file without __thread on the Solaris 9/UltraSparc platform using gcc 4.0.4. Not surprisingly it worked. But I no longer see the mention of the Sun assembler as in the case of gcc 3.4.4. Nor did I see the mention of "GNU assembler" as in the case of gcc 4.0.4/Solaris 10/x86. Instead, I saw something called "iropt" and "cg". Does anyone know what they are?
xz@gamera% gcc -v -Wall -D_REENTRANT -c -o common.o common.c
Using built-in specs.
Target: sparc-sun-solaris2.9
Configured with: /net/clpt-v490-0/export/data/bldmstr/20070711_mars_gcc/src/configure --prefix=/usr/sfw --enable-shared --with-system-zlib --enable-checking=release --disable-libmudflap --enable-languages=c,c++ --enable-version-specific-runtime-libs --with-cpu=v9 --with-ld=/usr/ccs/bin/ld --without-gnu-ld
Thread model: posix
gcc version 4.0.4 (gccfss)
/pkg/gcc/4.0.4/bin/../libexec/gcc/sparc-sun-solaris2.9/4.0.4/cc1 -quiet -v -iprefix /pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/ -D__sparcv8 -D_REENTRANT -DMESS common.c -quiet -dumpbase common.c -mcpu=v9 -auxbase-strip common.o -Wall -version -m32 -o /tmp/ccSGJIDD.s -r /tmp/ccKuJz76.ir
ignoring nonexistent directory "/pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/../../../../sparc-sun-solaris2.9/include"
ignoring nonexistent directory "/usr/local/include"
ignoring nonexistent directory "/usr/sfw/lib/gcc/sparc-sun-solaris2.9/4.0.4/include"
ignoring nonexistent directory "/usr/sfw/lib/../sparc-sun-solaris2.9/include"
#include "..." search starts here:
#include <...> search starts here:
/pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4/include
/usr/sfw/include
/usr/include
End of search list.
GNU C version 4.0.4 (gccfss) (sparc-sun-solaris2.9)
        compiled by GNU C version 4.0.4 (gccfss).
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
/pkg/gcc/4.0.4/SUNW0scgfss/4.0.4/prod/bin/iropt -F -xarch=v8plus -xchip=generic -O1 -xvector=no -xbuiltin=%none -xcache=generic -Qy -h_gcc -o /tmp/ccUl4mVM.ircg /tmp/ccKuJz76.ir -N/dev/null -is /tmp/ccSGJIDD.s
/pkg/gcc/4.0.4/SUNW0scgfss/4.0.4/prod/bin/cg -Qy -xarch=v8plus -xchip=generic -OO0 -T3 -Qiselect-C0 -Qrm:newregman:coalescing=0 -xcode=abs32 -xcache=generic -xmemalign=8i -il /pkg/gcc/4.0.4/bin/../lib/gcc/sparc-sun-solaris2.9/4.0.4//gccbuiltins.il -xvector=no -xthreadvar=no%dynamic -xbuiltin=%none -Qassembler-ounrefsym=0 -Qiselect-T0 -Qassembler-I -Qassembler-U -comdat -h_gcc -is /tmp/ccSGJIDD.s -ir /tmp/ccUl4mVM.ircg -oo common.o

Another Expired Certificate Error Thread

Similar Messages

Maybe you are looking for