public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tim Prince <tprince@computer.org>
To: Joseph North <joseph.north@gmail.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,  gcc-help@gcc.gnu.org
Subject: Re: GNU GCC -m32 Problem?
Date: Mon, 29 Oct 2007 16:16:00 -0000	[thread overview]
Message-ID: <472604C2.6020709@computer.org> (raw)
In-Reply-To: <1d11c7570710290840u5a8ecd43v1f931bc0b8b63156@mail.gmail.com>

Joseph North wrote:
>>
>> Your question is off-topic on the gcc mailing list, which is for
>> discussion of development *of* GCC, not *with* GCC.
>>
>>    Thanks a lot, ~ "gcc -m32 . . " worked!
>>    However, then, I got,
>>
>> /usr/bin/ld: skipping incompatible ../../libastro/libastro.a when
>> searching for -lastro
>> /usr/bin/ld: cannot find -lastro
>> collect2: ld returned 1 exit status
>>     
If you insist on cross-posting, you will gain a place in more and more 
kill files.
As to the error message, it means that the library path you have 
specified probably shows a copy of libastro.a for a different target 
(e.g. 64-bit linux), but none matching your -m32 target.  Supposing you 
built it yourself with -m64, the reason should be evident.

---AV & Spam Filtering by M+Guardian - Risk Free Email (TM)---

  reply	other threads:[~2007-10-29 16:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1d11c7570710281419t792edb36xb46d40048c4fd9d9@mail.gmail.com>
     [not found] ` <47250329.4060403@mbnet.fi>
     [not found]   ` <1d11c7570710281603u3a35a457g1dc99793d2447b62@mail.gmail.com>
     [not found]     ` <4348dea50710281608j4e53ca49nee5e0c2c7545456d@mail.gmail.com>
2007-10-29 16:08       ` Joseph North
2007-10-29 16:16         ` Tim Prince [this message]
2007-10-30  1:30         ` Kai Ruottu

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=472604C2.6020709@computer.org \
    --to=tprince@computer.org \
    --cc=gcc-help@gcc.gnu.org \
    --cc=joseph.north@gmail.com \
    --cc=jwakely.gcc@gmail.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).