From: "Fernan Bolando" <fernanbolando@mailc.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] more porting questions from newbie
Date: Thu, 16 Mar 2006 13:33:06 +0800 [thread overview]
Message-ID: <1d5d51400603152133w79c602bqedb23f853290ff93@mail.gmail.com> (raw)
In-Reply-To: <84fbfa983a05af9590554e9b75b87a3e@terzarima.net>
On 3/15/06, Charles Forsyth <forsyth@terzarima.net> wrote:
> > I found a thread in 9fans archive about undefined _main in .a libs
> > ****** from 9fans archive ***************************
> > andrey mirtchovski wrote:
> >> cc -o ocamlrun prims.o libcamlrun.a
> >> _main: undefined: main in _main
>
> it is complaining that `main' is undefined but called by
> a function `_main'. `_main' is in the C startup code, and is
> provided by the C library. i'm not sure
> why the linker doesn't pick up `main' if it is in the library.
>
> if you give ape's cc the -v option, it will give a little trace
> of loading of object files and libraries, which might help
On 3/16/06, Charles Forsyth <forsyth@terzarima.net> wrote:
> it's intentional, in that the automatic dependency loading (the `autolib'
> messages)
> is done only for libraries referenced implicitly (by #pragma lib lines in
> #include files),
> and that is done after all explicitly named object files and libraries are
> dealt with in
> command line order.
sorry for taking this out of 9fans. I am not used to using gmail as my
main interface
Charles thanks
,Fernan
--
Public PGP/GnuPG key (http://www.fernski.com)
pub 1024D/3576CA71 2006-02-02 Fernan Bolando
Key fingerprint = FDFE C9A8 FFED C1A5 2F5C EFEB D595 AF1C 3576 CA71
prev parent reply other threads:[~2006-03-16 5:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 8:05 Fernan Bolando
2006-03-15 9:33 ` Charles Forsyth
[not found] ` <84fbfa983a05af9590554e9b75b87a3e@terzarima.net>
2006-03-16 5:33 ` Fernan Bolando [this message]
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=1d5d51400603152133w79c602bqedb23f853290ff93@mail.gmail.com \
--to=fernanbolando@mailc.net \
--cc=9fans@cse.psu.edu \
/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).