From: David SAUVAGE - AdaLabs Ltd <david.sauvage@adalabs.com>
To: binutils@sourceware.org
Cc: gingold@adacore.com
Subject: Re: ld for ia64-hp-openvms target
Date: Thu, 23 Apr 2015 13:15:00 -0000 [thread overview]
Message-ID: <5538F055.2010304@adalabs.com> (raw)
In-Reply-To: <4E233EC2-EFF3-4009-BA17-AA42E21384AA@adacore.com>
On 03/18/2015 12:45 PM, Tristan Gingold wrote:
>> ia64-hp-openvms-ld: cannot find -limagelib
>> >ia64-hp-openvms-ld: cannot find -lstarlet
>> >ia64-hp-openvms-ld: cannot find -lsys$public_vectors
> You have to import these libraries from a VMS system.
>
I imported the 3 of them from VMS by using copy and zip them before
transfer to Unix.
While the cross ld _seems_ to correctly process imagelib.exe and
starlet.exe, a segfault is raised while processing
sys$public_vectors.exe [1]
Did you took sys$public_vectors.exe 'as it is' from VMS or did you
rework/transform/.../ it ?
[1]
binutils-2.23.1/elf64-ia64-vms.c
A.
in function elf64_vms_link_add_object_symbols htab->dynobj has NULL
value in the call to elf64_ia64_create_dynamic_sections
B.
Moreover in function elf64_ia64_create_dynamic_sections elf_hash_table
(info)->dynobj also has NULL value
Any idea why both htab->dynobj and elf_hash_table (info)->dynobj has
NULL value ?
Thanks
--
David SAUVAGE
Software Agile Architect, Director
AdaLabs Ltd - Mauritius
http://adalabs.com
+230 542 818 32
skype sauvaged
BRN C10097052
next prev parent reply other threads:[~2015-04-23 13:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 10:31 David SAUVAGE - AdaLabs Ltd
2015-03-17 10:42 ` Andreas Schwab
2015-03-17 14:37 ` David SAUVAGE - AdaLabs Ltd
2015-03-17 15:00 ` Tristan Gingold
2015-03-17 19:42 ` David SAUVAGE - AdaLabs Ltd
2015-03-18 8:46 ` Tristan Gingold
2015-03-19 16:54 ` David SAUVAGE - AdaLabs Ltd
2015-03-20 8:38 ` Tristan Gingold
2015-04-23 13:15 ` David SAUVAGE - AdaLabs Ltd [this message]
2015-04-23 15:30 ` Tristan Gingold
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=5538F055.2010304@adalabs.com \
--to=david.sauvage@adalabs.com \
--cc=binutils@sourceware.org \
--cc=gingold@adacore.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).