9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: underspecified <underspecified@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Cc: inferno-list@vitanuova.com, acme-sac@googlegroups.com
Subject: Re: [9fans] Re: Plan 9 Port error in mpvecadd-Darwin.s on Leopard
Date: Sat,  3 Nov 2007 18:22:01 +0900	[thread overview]
Message-ID: <ab4cf6420711030222p324adc5nfded30c88b908530@mail.gmail.com> (raw)
In-Reply-To: <ab4cf6420711030035j627e275fh79dedce32fda7288@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1629 bytes --]

Sorry to reply to myself, but I got it working by adding a call to 'ranlib
$lib' after every call to ar.
Hope this helps anyone with similar problems.

--underspecified

On 11/3/07, underspecified <underspecified@gmail.com> wrote:
>
> Greetings,
>
> Could you tell me how exactly you called ranlib to fix this problem?
> I'm getting the same errors when compiling Acme SAC under leopard.
>
>
> --underspecified
>
> On 11/1/07, David Leimbach <leimy2k@gmail.com > wrote:
> >
> > On Oct 31, 2007 12:05 PM, andrey mirtchovski <mirtchovski@gmail.com >
> > wrote:
> > > the problem comes from libmp: the machine-dependent files written in
> > > assembly (/src/libmp/386/*-Darwin.s) are causing it (and they are all
> > > broken, not just the one reported). it's beyond me to figure out why
> > > at the moment. i tried a couple of things at random, but that's not a
> > > way to fix a problem.
> > >
> > > all the functions defined therein have a replacement written in C in
> > > the port/ directory of libmp. a workaround for now will be to fix the
> > > mkfile in port/ to not look for the machine-dependent files (comment
> > > out the test in the reduce script and let it just echo all file
> > > names).
> > >
> > > next bug is all the way to venti:
> > >
> > > 9l -o o.buildindex buildindex.o libvs.a/Users/andrey/plan9/lib/libventi.a
> > > ld: in libvs.a, archive has no table of contents
> > > collect2: ld returned 1 exit status
> > >
> > ranlib to the rescue... Got it run it explicitly on Darwin.  I think
> > gcc lets you get away without it on linux.
> >
> > Dave
> >
>
>
>

[-- Attachment #2: Type: text/html, Size: 2598 bytes --]

  reply	other threads:[~2007-11-03  9:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3e1162e60710301650r35bd83ectbc2d8fbf8e708ba1@mail.gmail.com>
2007-10-30 23:59 ` Bakul Shah
2007-10-31 15:10   ` David Leimbach
2007-10-31 16:24     ` andrey mirtchovski
2007-10-31 16:42       ` David Leimbach
2007-10-31 19:05         ` andrey mirtchovski
2007-10-31 20:18           ` Russ Cox
2007-10-31 20:33             ` David Leimbach
2007-10-31 20:56               ` Michaelian Ennis
2007-11-03  6:02               ` Michaelian Ennis
2007-10-31 20:32           ` David Leimbach
2007-11-03  7:35             ` underspecified
2007-11-03  9:22               ` underspecified [this message]
2007-10-31 20:53         ` Michaelian Ennis

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=ab4cf6420711030222p324adc5nfded30c88b908530@mail.gmail.com \
    --to=underspecified@gmail.com \
    --cc=9fans@cse.psu.edu \
    --cc=acme-sac@googlegroups.com \
    --cc=inferno-list@vitanuova.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 NNTP newsgroup(s).