From: "Dmitry V. Levin" <ldv@altlinux.org>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: Re: [devel] openmpi & debuginfo
Date: Fri, 11 Feb 2011 12:35:14 +0300
Message-ID: <20110211093514.GB15689@altlinux.org> (raw)
In-Reply-To: <4D54C6F8.1020104@mmedia2.kemsu.ru>
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
On Fri, Feb 11, 2011 at 11:19:52AM +0600, REAL wrote:
> Привет!
>
> Раньше я уже поднимал вопрос про
> сломанную сборку libhdf5-mpi
> (http://git.altlinux.org/beehive/logs/Sisyphus-i586/latest/error/libhdf5-6-mpi-1.8.5_patch1-alt1
> ). Я покопался в config.log, но, чтобы было
> понятней другим, вот более наглядный
> пример (он полностью аналогичен данному
> случаю):
> http://git.altlinux.org/tasks/38420/build/100/i586/log
>
> Как видно, поломка происходит именно
> из-за debuginfo:
>
> mpif77 -o climate mutils.o srcmodel.o dstmodel.o coupler.o master.o
> -pipe -Wall -g -O2 -march=i586 -mtune=i686 -fPIC -DPIC
> -L/usr/src/RPM/BUILD/mct-2.6.0/mpeu -L/usr/src/RPM/BUILD/mct-2.6.0/mct
> -lmct -lmpeu -L/usr/lib/openmpi/lib -lmpi_f77 -lmpi_f90 -lmpi
> -Wl,-R/usr/lib/openmpi/lib
> /usr/bin/ld: master.o(.debug_info+0xd5e): unresolvable R_386_32
> relocation against symbol `mpi_fortran_argv_null_'
> /usr/bin/ld: final link failed: Nonrepresentable section on output
>
> Как такое лечить?
В этот момент в сборочной среде нет ни одного debuginfo-пакета.
Похоже что кто-то очень рассчитывает на mpi_fortran_argv_null_, который
уехал в какой-то debuginfo-пакет. Попробуйте найти файл, в котором сейчас
живет mpi_fortran_argv_null_.
--
ldv
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-02-11 9:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 5:19 REAL
2011-02-11 7:51 ` REAL
2011-02-11 9:35 ` Dmitry V. Levin [this message]
2011-02-11 9:45 ` REAL
2011-02-11 9:57 ` REAL
2011-02-11 9:56 ` Dmitry V. Levin
2011-02-11 10:07 ` REAL
2011-02-11 10:04 ` Dmitry V. Levin
2011-02-11 10:20 ` REAL
2011-02-14 9:19 ` REAL
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=20110211093514.GB15689@altlinux.org \
--to=ldv@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