public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: "Marty Leisner" <leisner@rochester.rr.com>
To: gas2@cygnus.com
Subject: should this configure line work?
Date: Sun, 04 Apr 1999 21:48:00 -0000	[thread overview]
Message-ID: <199904050448.AAA25026@rochester.rr.com> (raw)

I'm working again with gas alphas...

Should this line work (I copied it from a released 2.9):

  296  /usr/local/src/gnu/gas-990403/configure --prefix=/usr/gnu/gas-990403 --enable-commonbfdlib --enable-shared --enable-targets=i386-go32,i386-bsd,i386-pe

I end up getting:
gcc -g -O2 -o .libs/ld-new ldgram.o ldlex.o lexsup.o ldlang.o mri.o ldctor.o ldmain.o ldwrite.o ldexp.o ldemul.o ldver.o ldmisc.o ldfile.o ldcref.o eelf_i386.o ei386linux.o ei386go32.o ei386bsd.o ei386pe.o -Wl,--rpath -Wl,/usr/gnu/gas-990403/lib ../bfd/.libs/libbfd.so ../libiberty/libiberty.a
ei386pe.o: In function `gld_i386pe_parse_args':
/usr/local/obj/gas-990403/ld/ei386pe.c:414: undefined reference to `pe_dll_export_everything'
/usr/local/obj/gas-990403/ld/ei386pe.c:418: undefined reference to `pe_dll_add_excludes'
/usr/local/obj/gas-990403/ld/ei386pe.c:422: undefined reference to `pe_dll_kill_ats'
/usr/local/obj/gas-990403/ld/ei386pe.c:425: undefined reference to `pe_dll_stdcall_aliases'
ei386pe.o: In function `gld_i386pe_after_open':
/usr/local/obj/gas-990403/ld/ei386pe.c:621: undefined reference to `pe_process_import_defs'
/usr/local/obj/gas-990403/ld/ei386pe.c:623: undefined reference to `pe_dll_build_sections'
ei386pe.o: In function `gld_i386pe_unrecognized_file':
/usr/local/obj/gas-990403/ld/ei386pe.c:706: undefined reference to `pe_def_file'
/usr/local/obj/gas-990403/ld/ei386pe.c:707: undefined reference to `def_file_empty'
/usr/local/obj/gas-990403/ld/ei386pe.c:707: undefined reference to `pe_def_file'
/usr/local/obj/gas-990403/ld/ei386pe.c:708: undefined reference to `def_file_parse'
/usr/local/obj/gas-990403/ld/ei386pe.c:709: undefined reference to `pe_def_file'
/usr/local/obj/gas-990403/ld/ei386pe.c:720: undefined reference to `pe_def_file'
/usr/local/obj/gas-990403/ld/ei386pe.c:720: undefined reference to `pe_def_file'
/usr/local/obj/gas-990403/ld/ei386pe.c:738: undefined reference to `pe_def_file'
/usr/local/obj/gas-990403/ld/ei386pe.c:760: undefined reference to `pe_def_file'
ei386pe.o:/usr/local/obj/gas-990403/ld/ei386pe.c:763: more undefined references to `pe_def_file' follow
ei386pe.o: In function `gld_i386pe_recognized_file':
/usr/local/obj/gas-990403/ld/ei386pe.c:791: undefined reference to `pe_implied_import_dll'
ei386pe.o: In function `gld_i386pe_finish':
/usr/local/obj/gas-990403/ld/ei386pe.c:803: undefined reference to `pe_dll_fill_sections'
/usr/local/obj/gas-990403/ld/ei386pe.c:805: undefined reference to `pe_def_file'
/usr/local/obj/gas-990403/ld/ei386pe.c:805: undefined reference to `pe_dll_generate_implib'
/usr/local/obj/gas-990403/ld/ei386pe.c:808: undefined reference to `pe_dll_generate_def_file'
collect2: ld returned 1 exit status
make[3]: *** [ld-new] Error 1
make[3]: Leaving directory `/usr/local/obj/gas-990403/ld'

(this was a probably with gas from a month ago).



(can someone change my address from leisner@sdsp.mc.xerox.com to leisner@rochester.rr.com
on this list...I didn't see any instructions).

Marty Leisner
leisner@rochester.rr.com

                 reply	other threads:[~1999-04-04 21:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=199904050448.AAA25026@rochester.rr.com \
    --to=leisner@rochester.rr.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).