non-mulit-arch compiles probs

non-mulit-arch compiles probs

[Andrew Cagney]

FYI,

The file std-regs.c doesn't compile with -Werror on non-multi-arch 
targets.  They all dropped like flies.

Adding to the fun, I've found an entry for the ``how did this ever 
compile'' category:

exec.c:print_section_info (struct target_ops *t, bfd *abfd)
maint.c:print_section_info (const char *name, flagword flags,

(one is static, the other has a .h declaration).

fixing ...
Andrew

Re: non-mulit-arch compiles probs

[Andreas Schwab]

Andrew Cagney <ac131313@cygnus.com> writes:

|> Adding to the fun, I've found an entry for the ``how did this ever
|> compile'' category:
|> 
|> exec.c:print_section_info (struct target_ops *t, bfd *abfd)
|> maint.c:print_section_info (const char *name, flagword flags,
|> 
|> (one is static, the other has a .h declaration).

As long as the extern declaration is not visible while the static
definition is compiled, all is well.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: non-mulit-arch compiles probs

[Andrew Cagney]

> As long as the extern declaration is not visible while the static
> definition is compiled, all is well.
> 
> Andreas.

Yes, me `fixing' the -Werror compile problem makes that declaration 
visible  :-(

enjoy,
Andrew

Re: non-mulit-arch compiles probs

[Michael Snyder]

Andrew Cagney wrote:
> 
> FYI,
> 
> The file std-regs.c doesn't compile with -Werror on non-multi-arch
> targets.  They all dropped like flies.
> 
> Adding to the fun, I've found an entry for the ``how did this ever
> compile'' category:
> 
> exec.c:print_section_info (struct target_ops *t, bfd *abfd)
> maint.c:print_section_info (const char *name, flagword flags,
> 
> (one is static, the other has a .h declaration).

Doesn't the static one override the global one?

Re: non-mulit-arch compiles probs

[Andrew Cagney]

> Andrew Cagney wrote:
> 
>> 
>> FYI,
>> 
>> The file std-regs.c doesn't compile with -Werror on non-multi-arch
>> targets.  They all dropped like flies.
>> 
>> Adding to the fun, I've found an entry for the ``how did this ever
>> compile'' category:
>> 
>> exec.c:print_section_info (struct target_ops *t, bfd *abfd)
>> maint.c:print_section_info (const char *name, flagword flags,
>> 
>> (one is static, the other has a .h declaration).
> 
> 
> Doesn't the static one override the global one?

Yes, you can have both a static and a global function with the same 
name.  I think it is asking for trouble though.  As with my case, when 
the global function's declaration becomes visible in the file with the 
static declaration (new #include) the compile will barf (the functions 
had different signatures).

enjoy,
Andrew