Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Sander <msander@ripnet.com>
To: buildroot@busybox.net
Subject: [Buildroot] portmap build error
Date: Sat, 25 Oct 2008 22:14:24 -0400	[thread overview]
Message-ID: <4903D280.60009@ripnet.com> (raw)
In-Reply-To: <4900852F.4010809@ripnet.com>

Following up from my earlier post.  I am still unable to build portmap.  

What I have noticed is that the earlier buildroot (april) has these symbols in arm-linux-uclibc/lib/libgcc_s.so.  They are not present in the newer buildroot.  I am trying to figure out how libgcc is built.

As far as I can tell all RPC related configurations are identical between my two buildroot trees.

Anyone have any ideas?

Thanks,

<cut earlier output>

staging_dir//usr/lib/crtn.o
portmap.o: In function `reg_service':
portmap.c:(.text+0x120): undefined reference to `svc_sendreply'
portmap.c:(.text+0x23c): undefined reference to `svc_sendreply'
portmap.c:(.text+0x404): undefined reference to `svcerr_decode'
portmap.c:(.text+0x550): undefined reference to `clntudp_create'
portmap.c:(.text+0x578): undefined reference to `authunix_create'
portmap.c:(.text+0x5e0): undefined reference to `svc_sendreply'
portmap.c:(.text+0x62c): undefined reference to `svcerr_noproc'
portmap.c:(.text+0x650): undefined reference to `xdr_void'
portmap.c:(.text+0x654): undefined reference to `xdr_pmap'
portmap.c:(.text+0x65c): undefined reference to `xdr_int'
portmap.c:(.text+0x664): undefined reference to `xdr_pmaplist'
portmap.o: In function `xdr_encap_parms':
portmap.c:(.text+0x688): undefined reference to `xdr_bytes'
portmap.o: In function `xdr_rmtcall_result':
portmap.c:(.text+0x6a0): undefined reference to `xdr_u_long'
portmap.o: In function `xdr_rmtcall_args':
portmap.c:(.text+0x6c8): undefined reference to `xdr_u_long'
portmap.c:(.text+0x6dc): undefined reference to `xdr_u_long'
portmap.c:(.text+0x6f0): undefined reference to `xdr_u_long'
portmap.o: In function `xdr_opaque_parms':
portmap.c:(.text+0x71c): undefined reference to `xdr_opaque'
portmap.o: In function `main':
portmap.c:(.text+0x914): undefined reference to `svcudp_create'
portmap.c:(.text+0x9a0): undefined reference to `svctcp_create'
portmap.c:(.text+0x9fc): undefined reference to `svc_register'
portmap.c:(.text+0xa1c): undefined reference to `svc_run'
pmap_check.o: In function `logit':
pmap_check.c:(.text+0x34): undefined reference to `getrpcbynumber'
collect2: ld returned 1 exit status
make[1]: *** [portmap] Error 1
make[1]: Leaving directory `/home/br22oct/buildroot/build_arm/portmap_5beta'
make: *** [/home/br22oct/buildroot/build_arm/portmap_5beta/portmap] Error 2

      reply	other threads:[~2008-10-26  2:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-23 14:07 [Buildroot] portmap build error mike sander
2008-10-26  2:14 ` Mike Sander [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=4903D280.60009@ripnet.com \
    --to=msander@ripnet.com \
    --cc=buildroot@busybox.net \
    /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