Project Home
Project Home
Trackers
Trackers
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - qcc/QCC with "-pipe" option produce error on QNX 6.4.1: (9 Items)
   
qcc/QCC with "-pipe" option produce error on QNX 6.4.1  
If I use a simple Makefile that was working on previous version of QNX (6.21, 6.3, 6.40) I got the following error with 
QNX 6.4.1:
  
--------------  
  $ qcc -O2 -Wall -g -pipe -I. -c -o somefile.o somefile.c
  cc1: error: unrecognized command line option "-pipe"
  cc: /usr/qnx641/host/qnx6/x86/usr/lib/gcc/i386-pc-nto-qnx640/4.3.3/cc1 error 1
--------------

If I use directly gcc instead of qcc, it work.

I know that "-pipe" is probably by default and there's only the "-nopipe" option documented for qcc, but gcc take "-pipe
" and the previous version of qcc was working as well, removing the "-pipe" option to qcc can break some old Makefile...


thanks

-- 
Martin Gagnon
Re: qcc/QCC with "-pipe" option produce error on QNX 6.4.1  
qcc always just passed the -pipe straight through to cc1 - that is what changed (4.2.4 to 4.3.3), so it was just 
coincidence that it worked.

Martin Gagnon wrote:
> If I use a simple Makefile that was working on previous version of QNX (6.21, 6.3, 6.40) I got the following error 
with QNX 6.4.1:
>   
> --------------  
>   $ qcc -O2 -Wall -g -pipe -I. -c -o somefile.o somefile.c
>   cc1: error: unrecognized command line option "-pipe"
>   cc: /usr/qnx641/host/qnx6/x86/usr/lib/gcc/i386-pc-nto-qnx640/4.3.3/cc1 error 1
> --------------
> 
> If I use directly gcc instead of qcc, it work.
> 
> I know that "-pipe" is probably by default and there's only the "-nopipe" option documented for qcc, but gcc take "-
pipe" and the previous version of qcc was working as well, removing the "-pipe" option to qcc can break some old 
Makefile...
> 
> thanks
> 

-- 
cburgess@qnx.com
Re: qcc/QCC with "-pipe" option produce error on QNX 6.4.1  
> qcc always just passed the -pipe straight through to cc1 - that is what 
> changed (4.2.4 to 4.3.3), so it was just coincidence that it worked.
> 
> -- 
> cburgess@qnx.com

What coincidence you talk about.. if qcc was passing the "-pipe" to gcc before and since 4.3.3 it doesn't, it not a 
coincidence if now it doen't work and before it was working... it's just broken now..

gcc 4.3.3 support the option, it's just qcc that see the "-pipe" as a bad parameter instead of passing it to gcc...

-- 
Martin Gagnon

Re: qcc/QCC with "-pipe" option produce error on QNX 6.4.1  
qcc just passes -p* through to cc1, so if you did qcc -pfoobar then cc1 would see -pfoobar.

qcc only understands -nopipe, since -pipe is the default.

Martin Gagnon wrote:
>> qcc always just passed the -pipe straight through to cc1 - that is what 
>> changed (4.2.4 to 4.3.3), so it was just coincidence that it worked.
>>
>> -- 
>> cburgess@qnx.com
> 
> What coincidence you talk about.. if qcc was passing the "-pipe" to gcc before and since 4.3.3 it doesn't, it not a 
coincidence if now it doen't work and before it was working... it's just broken now..
> 
> gcc 4.3.3 support the option, it's just qcc that see the "-pipe" as a bad parameter instead of passing it to gcc...
> 

-- 
cburgess@qnx.com
Re: qcc/QCC with "-pipe" option produce error on QNX 6.4.1  
> > qcc always just passed the -pipe straight through to cc1 - that is what 
> > changed (4.2.4 to 4.3.3), so it was just coincidence that it worked.
> > 
> > -- 
> > cburgess@qnx.com
> 
> What coincidence you talk about.. if qcc was passing the "-pipe" to gcc before
>  and since 4.3.3 it doesn't, it not a coincidence if now it doen't work and 
> before it was working... it's just broken now..
> 
> gcc 4.3.3 support the option, it's just qcc that see the "-pipe" as a bad 
> parameter instead of passing it to gcc...

Sorry.. I just realize that qcc pass to cc1 and not directly to gcc..  To this qcc that don't pass "-pipe" to cc1 do the
 job for now..
Re: qcc/QCC with "-pipe" option produce error on QNX 6.4.1  
Colin Burgess wrote:
> qcc always just passed the -pipe straight through to cc1 - that is what changed (4.2.4 to 4.3.3), so it was just 
coincidence that it worked.

qcc used to do special handling for -pipe and -pedantic. Every other -p 
option was treated as profiling. -pipe is now passed through and cc1
doesn't accept it. I'll file a PR.

Regards,

Ryan Mansfield
Re: qcc/QCC with "-pipe" option produce error on QNX 6.4.1  
Ah, so that's what happened...


Ryan Mansfield wrote:
> Colin Burgess wrote:
>> qcc always just passed the -pipe straight through to cc1 - that is what changed (4.2.4 to 4.3.3), so it was just 
coincidence that it worked.
> 
> qcc used to do special handling for -pipe and -pedantic. Every other -p 
> option was treated as profiling. -pipe is now passed through and cc1
> doesn't accept it. I'll file a PR.
> 
> Regards,
> 
> Ryan Mansfield
> 
> _______________________________________________
> General
> http://community.qnx.com/sf/go/post30947
> 

-- 
cburgess@qnx.com
Re: qcc/QCC with "-pipe" option produce error on QNX 6.4.1  
The attached qcc will not pass -pipe through to cc1. 

Regards,

Ryan Mansfield
Attachment: Text qcc.gz 65.53 KB
Re: qcc/QCC with "-pipe" option produce error on QNX 6.4.1  
> The attached qcc will not pass -pipe through to cc1. 
> 
> Regards,
> 
> Ryan Mansfield


Thanks.. It works..

-- 
Martin Gagnon