From: comeau@panix.com (Greg Comeau)
To: 9fans@9fans.net
Subject: Re: [9fans] 8l follows a precedence based on the commandline arrangement
Date: Wed, 2 Mar 2011 13:28:57 +0000 [thread overview]
Message-ID: <iklg89$20s$1@panix2.panix.com> (raw)
In-Reply-To: <AANLkTi=JkUoRaK30rhSjKxbo0eU9varQqo7+pZhC4kVR@mail.gmail.com>
In article <AANLkTi=JkUoRaK30rhSjKxbo0eU9varQqo7+pZhC4kVR@mail.gmail.com>,
Fernan Bolando <fernanbolando@mailc.net> wrote:
>just curious is it normal for 8l to follow some sort of precendence
>based on the commandline? this being done through ape/pcc
>
>this is unable to build
>8l -o spice -v /386/lib/ape/libf2c.a spice.8 unix.8 /386/lib/ape/libap.a
>
>this was able to build
>8l -o spice -v spice.8 unix.8 /386/lib/ape/libf2c.a /386/lib/ape/libap.a
>...
8l requires it to be mentioned/presented in order, and once it
moves on from a library, requires still needed libraries to be repeatedly
mentioned/presented even if "the same library" was already mentioned
previously. As per 8l "When scanning such libraries, the algorithm is
to scan each library repeatedly until no new undefined symbols are picked up,
then to start on the next library. Thus if library A needs B which
needs A again, it may be necessary to mention A explicitly so it will
be read a second time." So your problem lib is probably having put
libf2c.a first.
--
Greg Comeau / 4.3.10.1 with C++0xisms now in beta!
Comeau C/C++ ONLINE ==> http://www.comeaucomputing.com/tryitout
World Class Compilers: Breathtaking C++, Amazing C99, Fabulous C90.
Comeau C/C++ with Dinkumware's Libraries... Have you tried it?
next prev parent reply other threads:[~2011-03-02 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 14:23 Fernan Bolando
2011-02-28 16:31 ` Charles Forsyth
2011-02-28 16:41 ` Rob Pike
2011-03-02 7:22 ` Ethan Grammatikidis
2011-03-02 13:28 ` Greg Comeau [this message]
2011-03-02 14:21 ` Charles Forsyth
2011-03-02 14:34 ` Charles Forsyth
2011-03-03 0:51 ` Fernan Bolando
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='iklg89$20s$1@panix2.panix.com' \
--to=comeau@panix.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).