From: Joel Sherrill <joel@OARcorp.com>
To: gas2@cygnus.com
Subject: i386-go32
Date: Mon, 15 Dec 1997 13:03:00 -0000 [thread overview]
Message-ID: <Pine.BSF.3.96.971215145724.26609C-100000@vespucci.advicom.net> (raw)
Whether or not the name is right, it still does not work in gas-971208 but
did in binutils 2.8.1. I checked the i386-go32 configuration against
i386-go32-rtems and did not spot anything. I have tracked the problem
down and it appears that the BFD vector is somehow misspecified. I have
grep'ed all the configuration files but do not see the problem. gas
prints a fatal error message because it can't find the target vector. I
traced it with gdb and found:
bfd_openw (filename=0x80793b5 "a.out", target=0x8082bc4 "coff-go32")
at ../../src/bfd/opncls.c:348
348 bfd_set_error (bfd_error_system_call);
(gdb) n
353 nbfd = _bfd_new_bfd ();
(gdb)
354 if (nbfd == NULL)
(gdb)
357 target_vec = bfd_find_target (target, nbfd);
(gdb) s
bfd_find_target (target_name=0x8082bc4 "coff-go32", abfd=0x80e9080)
at ../../src/bfd/targets.c:958
958 if (target_name != NULL)
(gdb) s
959 targname = target_name;
(gdb) n
964 if (targname == NULL || strcmp (targname, "default") == 0)
(gdb)
974 abfd->target_defaulted = false;
(gdb)
976 target = find_target (targname);
(gdb)
977 if (target == NULL)
(gdb)
978 return NULL;
(gdb)
982 }
(gdb)
bfd_openw (filename=0x80793b5 "a.out", target=0x8082bc4 "coff-go32")
at ../../src/bfd/opncls.c:358
358 if (target_vec == NULL)
(gdb)
371 objalloc_free ((struct objalloc *) nbfd->memory);
(gdb)
372 free (nbfd);
(gdb)
373 return NULL;
(gdb)
377 }
(gdb)
write_object_file () at ../../src/gas/config/obj-coff.c:3128
3128 if (abfd == 0)
(gdb)
3130 as_perror ("FATAL: Can't create %s", out_file_name);
What do I have wrong in one of the configuration files?
Thanks.
--joel
next reply other threads:[~1997-12-15 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-15 13:03 Joel Sherrill [this message]
1997-12-15 13:08 ` i386-go32 Ian Lance Taylor
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=Pine.BSF.3.96.971215145724.26609C-100000@vespucci.advicom.net \
--to=joel@oarcorp.com \
--cc=gas2@cygnus.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).