public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Stephen Feyrer <steve@toth.org.uk>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] C compiler cannot create executables
Date: Sat, 19 Sep 2009 09:35:08 +0100	[thread overview]
Message-ID: <4AB497BC.9060409@toth.org.uk> (raw)
In-Reply-To: <4AB3850D.9060807@blue-labs.org>

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

David Ford wrote:
> 
> [...]
> configure:4191: checking for C compiler default output file name
> configure:4213: armv5tel-softfloat-linux-gnueabi-gcc    conftest.c
> /usr/armv5tel-softfloat-linux-gnueabi/lib/libc-2.3.4.so >&5
> /usr/armv5tel-softfloat-linux-gnueabi/lib/libc-2.3.4.so: undefined
> reference to `_dl_out_of_memory@GLIBC_PRIVATE'
> collect2: ld returned 1 exit status
> configure:4217: $? = 1
> configure:4255: result:
> configure: failed program was:
> | /* confdefs.h.  */
> | #define PACKAGE_NAME "Dovecot"
> | #define PACKAGE_TARNAME "dovecot"
> | #define PACKAGE_VERSION "1.2.rc5"
> | #define PACKAGE_STRING "Dovecot 1.2.rc5"
> | #define PACKAGE_BUGREPORT "dovecot@dovecot.org"
> | #define PACKAGE "dovecot"
> | #define VERSION "1.2.rc5"
> | /* end confdefs.h.  */
> |
> | int
> | main ()
> | {
> |
> |   ;
> |   return 0;
> | }
> configure:4261: error: in `/root/dovecot/dovecot-1.2.3':
> configure:4264: error: C compiler cannot create executables
> 

Sorry, I can only guess at what's going on here (except of cause that it
doesn't work).  I imagine from this excerpt of my config.log that it
should be obvious and staring me in the face.

If this has a specific mean that I should know, please tell me.

Better yet, if there is away making my build environment target the host
system with that version glibc, tell me that instead.

Indeed all I really need to know is how to build a working version of
dovecot for the qnap network attached storage device.


--
Hopefully yours

Stephen.

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3322 bytes --]

  reply	other threads:[~2009-09-19  8:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 18:30 [gentoo-embedded] C compiler cannot create executables Stephen Feyrer
2009-09-17 23:28 ` Peter Stuge
2009-09-18  8:49   ` Stephen Feyrer
2009-09-18 13:03     ` David Ford
2009-09-19  8:35       ` Stephen Feyrer [this message]
2009-09-19 15:26         ` David Ford
2009-09-20  8:55           ` Stephen Feyrer
2009-09-19 14:15       ` Mike Frysinger
2009-09-19 15:28         ` David Ford
2009-09-20  9:10           ` Stephen Feyrer
2009-09-20  8:51         ` Stephen Feyrer
2009-09-22 21:40         ` Stephen Feyrer
  -- strict thread matches above, loose matches on Subject: below --
2007-11-05 18:55 Jean-Claude Gervais
2007-11-05 22:41 ` Peter Stuge
2007-11-05 23:50   ` Ned Ludd
2007-11-06 17:26     ` Jean-Claude Gervais
2007-11-06 17:46       ` Jason
2007-11-06 17:55         ` Jean-Claude Gervais
2007-11-06 17:59           ` Jean-Claude Gervais
2007-11-06 18:11           ` Jason
2007-11-06 19:55             ` Jean-Claude Gervais
2007-11-06 20:19               ` Jason
2007-11-06 20:31                 ` Jean-Claude Gervais
2007-11-06 20:38                   ` Jason
2007-11-06 20:48                     ` Jean-Claude Gervais
2007-11-06 20:55                       ` Jason
2007-11-06  0:50   ` Mike Frysinger

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=4AB497BC.9060409@toth.org.uk \
    --to=steve@toth.org.uk \
    --cc=gentoo-embedded@lists.gentoo.org \
    /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