ALT Linux Team development discussions
 help / color / mirror / Atom feed
From: Andrey Savchenko <bircoph@altlinux.org>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] Q: нерабочий ruby на armh
Date: Fri, 19 Jun 2020 13:16:23 +0300
Message-ID: <20200619131623.0af3ec6cdce4e17980fccf46@altlinux.org> (raw)
In-Reply-To: <m3tuz7h0y1.fsf@altlinux.ru>

[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]

On Fri, 19 Jun 2020 12:14:30 +0300 Sergey Bolshakov wrote:
> >>>>> "Yuri" == Yuri Sedunov <aris-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org> writes:
> 
>  > В Пт, 19/06/2020 в 00:24 +0300, Dmitry V. Levin пишет:
>  >> On Thu, Jun 18, 2020 at 03:41:52PM +0000, Girar Builder awaiter robot
>  >> wrote:
>  >> > http://git.altlinux.org/tasks/253596/logs/events.1.1.log
>  >> > 
>  >> > 2020-Jun-18 15:29:32 :: task #253596 for sisyphus started by shaba:
>  >> > 2020-Jun-18 15:29:33 :: [aarch64] #100 opennebula.git 5.10.5-alt2: 
>  >> > 
>  > ...
>  >> Как это понимать? /usr/bin/ruby на armh нерабочий?
>  >> Каким образом там был собран предыдущий релиз opennebula-5.10.5-alt1?
> 
>  > Похожий вопрос.
>  > [#253621] FAILED srpm=evince-3.36.6-alt1.src.rpm
>  > Каким образом был собран предыдущий релиз evince-3.36.5-alt1.armh.rpm
> 
> Предыдущий собирался в другой среде.
> Судя по строчке
> 
> meson.build:362:13: ERROR: Can not run test applications in this cross environment.
> 
> uname -m в сборочном окружении выдаёт что-то неожиданное.

Он даёт aarch64, что сбивает с толку все приложения.
Исправьте сборочницу armh.

Best regards,
Andrew Savchenko

[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-06-19 10:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 21:24 ` [devel] Q: нерабочий ruby на armh (was: [#253596] FAILED opennebula.git=5.10.5-alt2) Dmitry V. Levin
2020-06-19  7:23   ` Yuri Sedunov
2020-06-19  9:14     ` [devel] Q: нерабочий ruby на armh Sergey Bolshakov
2020-06-19 10:16       ` Andrey Savchenko [this message]
2020-06-19 13:07         ` Dmitry V. Levin
2020-06-19 13:14           ` Sergey Bolshakov
2020-06-19 13:43             ` Dmitry V. Levin
2020-06-19 13:52               ` Andrey Savchenko
2020-06-19 13:55                 ` Dmitry V. Levin
2020-06-19 21:29                   ` Vitaly Lipatov
2020-06-19 22:32                       ` Dmitry V. Levin
2020-06-19 23:07                           ` Andrey Savchenko
2020-06-19 23:20                           ` [devel] Q: setarch для armh Dmitry V. Levin
2020-06-19 13:19           ` [devel] Q: нерабочий ruby на armh Andrey Savchenko
2020-06-19 13:32             ` Антон Мидюков
2020-06-19 14:17               ` Andrey Savchenko
2020-06-19 14:21                 ` Andrey Savchenko
2020-06-19 14:25                   ` Alexey V. Vissarionov
2020-06-19 14:25                   ` Dmitry V. Levin
2020-06-19 15:03                     ` Andrey Savchenko
2020-06-19 15:50                       ` Andrey Savchenko
2020-06-19 16:04                         ` Aleksey Novodvorsky
2020-06-19 16:07                         ` [devel] Q: нерабочий util-linux " Dmitry V. Levin
2020-06-19 16:15                           ` Alexey Gladkov
2020-06-19 16:29                           ` Andrey Savchenko
2020-06-19 17:06                           ` Sergey Bolshakov
2020-06-19 18:15                             ` [devel] Q: setarch для armh Dmitry V. Levin
2020-06-19 18:48                               ` Sergey Bolshakov
2020-06-19 19:36                                   ` Sergey Bolshakov
2020-06-19 14:23                 ` [devel] Q: нерабочий ruby на armh Dmitry V. Levin
2020-06-19 14:27                 ` Антон Мидюков
2020-06-19  9:05   ` Sergey Bolshakov

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=20200619131623.0af3ec6cdce4e17980fccf46@altlinux.org \
    --to=bircoph@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