This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Query about cpp0 binary in version 3.3.4 on Debian


> -----Original Message-----
> From: gcc-owner On Behalf Of Tim Parker
> Sent: 21 October 2004 12:07

> Hi,
> 
> I am trying to compile some source code which is currently 
> being built on 
> RedHat 9 using gcc-3.1 but when I try to compile the same 
> code with the 
> current Debian version of gcc (3.3.4) it complains that there 
> is no cpp0 binary.

  Yes, we know, we heard you the first time.  And the second time.  And the
third time.  You come across as rather demanding.  If you find the customer
service round here isn't snappy enough to meet your expectations, you're
welcome to a *full* refund....

> Has this been removed and if it has, has it been replaced by 
> an alternative?

  Just use plain 'cpp', which is most likely what you should have been using
all along.  The C preprocessor functionality was originally a separate
subprogram from the compiler, so 'cpp0' was called to do the preprocessing
and the result was passed to 'cc1', the actual compiler.  Both the 'gcc' and
'cpp' executables are simple driver programs that handle invoking the
various stages, passing output from one to the next, and separating out the
various command line flags that each stage understands.  The preprocessor
functionality is now builtin to 'cc1', so there is no need for a standalone
'cpp0'; the equivalent function could be achieved by using 'cc1 -E'.
However, you should really just use 'gcc -E' or 'cpp -E' and allow the
driver to take care of getting things right for you; it was never right to
be invoking 'cpp0' anymore than it would be to invoke 'cc1' directly as part
of a compilation.  The drivers are wrappers that are there to isolate and
protect you from these sort of under-the-bonnet changes; if you make an
end-run around that protection, this is what you get.

> Thanks for any help people can give me on this.
> 
> Cheers
> Tim.
> 
> p.s. sorry for having the disclaimer on my previous post - it 
> should hopefully be removed now!
>
> This e-mail and any attachments are confidential and may also 
[KERSNIPFLUSH]

  Just not your day, is it?

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]