Package conflicts trying to install jpegdupes package

2QdxY4RzWzUUiLuE at potatochowder.com 2QdxY4RzWzUUiLuE at potatochowder.com
Mon Sep 27 14:03:18 EDT 2021


On 2021-09-28 at 03:23:53 +1000,
Chris Angelico <rosuav at gmail.com> wrote:

> On Tue, Sep 28, 2021 at 3:11 AM Skip Montanaro <skip.montanaro at gmail.com> wrote:
> >>
> >> Those are all warnings. Are there any errors that follow them?
> >
> >
> > Maybe I just missed the actual errors, but the compiler exit status was 1, so there must have been. I'll give it another try.
> 
> Yeah, one of the annoying things of building large C packages is when
> the maintainers don't care about warnings, and then legit errors get
> lost in the spam.

It's also possible that the compiler is running in a "warnings are
errors" mode.  Hack the Makefile (or equivalent) at your own peril.

One of the annoying things about warnings is that they're not standard,
so squelching them under one compiler makes another compiler (or a
different version of the same compiler) whine.  IIRC, a compliant C
compiler can issue a warning for anything it wants, including "this
variable name contains too many vowels" or "this is a computer, and
today may be Tuesday."

In many ways, the engineering pieces of software engineering remain in
their infancy.  *sigh*


More information about the Python-list mailing list