Opened 6 years ago

Closed 6 years ago

#55725 closed defect (fixed)

unpaper @6.1: error: Package requirements (libavformat libavcodec libavutil) were not met

Reported by: jxy (Xiao-Yong) Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: unpaper

Description

Compile unpaper-6.1 gives the following error.

:info:configure checking for libavformat libavcodec libavutil... no
:info:configure configure: error: Package requirements (libavformat libavcodec libavutil) were not met:
:info:configure No package 'libavformat' found
:info:configure No package 'libavcodec' found
:info:configure No package 'libavutil' found
:info:configure Consider adjusting the PKG_CONFIG_PATH environment variable if you
:info:configure installed software in a non-standard prefix.
:info:configure Alternatively, you may set the environment variables LIBAV_CFLAGS
:info:configure and LIBAV_LIBS to avoid the need to call pkg-config.
:info:configure See the pkg-config man page for more details.
:info:configure Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_unpaper/unpaper/work/unpaper-6.1" && ./configure --prefix=/opt/local --disable-silent-rules 
:info:configure Exit code: 1

Change History (2)

comment:1 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: set to ryandesign
Status: newaccepted
Summary: unpaper-6.1 fails configure phase (requires libav?)unpaper @6.1: error: Package requirements (libavformat libavcodec libavutil) were not met

Yes, unpaper 6 requires libavcodec provided by libav, which is not in MacPorts (#50039). unpaper 6.1 adds support for ffmpeg's implementation of libavcodec.

comment:2 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: acceptedclosed

In 2dbfc6857566525e048bc64b93082a97e0aab3d8/macports-ports:

unpaper: Add missing ffmpeg and pkgconfig dependencies

Closes: #55725

No longer override the optimization flags, since MacPorts prefers to
follow Apple's lead and use -Os rather than -O2.

No longer use -march=native flag because that can result in binaries
that cannot be used on user systems, if the user system has a different
processor than our build machine.

No longer use -pipe flag because MacPorts already uses that flag if
requested by the user in macports.conf; the default is to do so.

No longer use -flto flag on gcc-4.2 compiler which does not support it.

Note: See TracTickets for help on using tickets.