From: "Konstantin A. Lepikhov" <lakostis@altlinux.org>
To: devel@lists.altlinux.org
Subject: Re: [devel] transcode-1.0.2-alt3.3: x86_64 rebuild failed
Date: Fri, 18 May 2007 00:01:30 +0400
Message-ID: <20070517200130.GB18811@lks.home> (raw)
In-Reply-To: <20070517181830.49037B0D95@basalt.office.altlinux.org>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
Hi QA!
Thursday 17, at 10:18:30 PM you wrote:
...
>
> ERROR: requirement failed: cannot link against libavcodec
> libavcodec can be found in the following packages:
> libavcodec http://www.ffmpeg.org/
>
> Please see the INSTALL file in the top directory of the
> transcode sources for more information about building
> transcode with this configure script.
>
> error: Bad exit status from /usr/src/tmp/rpm-tmp.92138 (%build)
>
> RPM build errors:
> Bad exit status from /usr/src/tmp/rpm-tmp.92138 (%build)
> Command exited with non-zero status 1
> 54.75user 11.29system 1:18.65elapsed 83%CPU (0avgtext+0avgdata 0maxresident)k
> 0inputs+0outputs (0major+2847480minor)pagefaults 0swaps
> hsh-rebuild: rebuild of `transcode-1.0.2-alt3.3.src.rpm' failed.
> Command exited with non-zero status 1
зачем сломали мой любимый transcode своими бездумными обновлениями ffmpeg?
Ну что там такого нового появляется, что надо его обновлять каждую неделю?
--
WBR et al.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2007-05-17 20:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 20:01 ` Konstantin A. Lepikhov [this message]
2007-05-17 20:46 ` Pavlov Konstantin
2007-05-17 21:52 ` [devel] ranscode-1.0.2-alt3.3: " Konstantin A. Lepikhov
2007-05-17 22:08 ` Dmitry V. Levin
2007-05-17 23:56 ` Pavlov Konstantin
2007-05-18 0:03 ` Dmitry V. Levin
2007-05-18 0:27 ` Pavlov Konstantin
2007-05-18 0:35 ` Dmitry V. Levin
2007-05-18 10:31 ` Led
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070517200130.GB18811@lks.home \
--to=lakostis@altlinux.org \
--cc=devel@lists.altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git