public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: mpsuzuki@hiroshima-u.ac.jp
To: Tristan Gingold <gingold@adacore.com>
Cc: fleury@labri.fr, binutils@sourceware.org
Subject: Re: [libbfd] Mach-O format support ?
Date: Wed, 14 Apr 2010 09:11:00 -0000	[thread overview]
Message-ID: <20100414181108.40e98561.mpsuzuki@hiroshima-u.ac.jp> (raw)
In-Reply-To: <9FD2BC70-88A6-49E2-A7CD-9080A95C0D8F@adacore.com>

Hi,

On Wed, 14 Apr 2010 10:49:02 +0200
Tristan Gingold <gingold@adacore.com> wrote:
>> on Mac OS X, "nm" complains as:
>> 
>> $ ./nm-new /usr/lib/libwrap.a 
>> ./nm-new: /usr/lib/libwrap.a:i386: File format not recognized
>> ./nm-new: /usr/lib/libwrap.a:powerpc:common: File format not recognized
>
>Yes, nm on universal archive doesn't work, because nm doesn't handle archives of archives!

Thank you for quick reply!

It seems that the "ar" of GNU binutils doesn't handle
universal binary archive directly. I guess the universal
binary archive of Mac OS X is concatenated in fat binary
format, instead of "ar" archive format. In fact, even
Apple's "ar" cannot parse the universal binary archive,
it tells to split the universal binary archive by libtool/lipo
and execute "ar" on the splitted files.

Is there GNU replacement of Apple's lipo?

Regards,
mpsuzuki

  reply	other threads:[~2010-04-14  9:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13 15:05 [libbdf] " Emmanuel Fleury
2010-04-14  7:35 ` Tristan Gingold
2010-04-14  8:08   ` Emmanuel Fleury
2010-04-14  8:27     ` Tristan Gingold
2010-04-14  8:40       ` [libbfd] " mpsuzuki
2010-04-14  8:49         ` Tristan Gingold
2010-04-14  9:11           ` mpsuzuki [this message]
2010-04-14  9:19             ` Tristan Gingold
2010-04-14  8:51       ` [libbdf] " Emmanuel Fleury
2010-04-14  8:57         ` Tristan Gingold

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=20100414181108.40e98561.mpsuzuki@hiroshima-u.ac.jp \
    --to=mpsuzuki@hiroshima-u.ac.jp \
    --cc=binutils@sourceware.org \
    --cc=fleury@labri.fr \
    --cc=gingold@adacore.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).