From: Mark Hatle <mark.hatle@windriver.com>
To: <poky@yoctoproject.org>
Subject: Re: Error in pulling nspr package
Date: Tue, 3 May 2011 23:51:52 -0500 [thread overview]
Message-ID: <4DC0DB68.1040303@windriver.com> (raw)
In-Reply-To: <BANLkTim0CS8a5Q1Mv-m=KDsBGTPNA3V6mQ@mail.gmail.com>
On 5/3/11 11:19 PM, chinmaya hoshing wrote:
> Hi,
>
> I am trying to port Poky to the "sandybridge platform" and using the branch
> "bernard" for "sugarbay" machine.
> I am running Ubuntu 10.10 on 64 bit machine.
> I am getting error for nspr package following is the error log:
> NOTE: package nss-3.12.9-r2: task do_patch: Succeeded
> | x86_64-poky-linux-gcc -m64
> --sysroot=/home/sct/logi_sandybridge/poky/build/tmp/sysroots/sugarbay -m32 -o
> now.o -c -fexpensive-optimizations -fomit-frame-pointer -frename-registers
> -O2 -ggdb -feliminate-unused-debug-types -Wall -g -fno-inline -fPIC -UNDEBUG
> -DDEBUG_sct -DDEBUG=1 -DHAVE_VISIBILITY_HIDDEN_ATTRIBUTE=1
> -DHAVE_VISIBILITY_PRAGMA=1 -DXP_UNIX=1 -D_GNU_SOURCE=1
> -DHAVE_FCNTL_FILE_LOCKING=1 -DLINUX=1 -Di386=1 -DHAVE_LCHOWN=1 -DHAVE_STRERROR=1
> -D_REENTRANT=1 -DFORCE_PR_LOG -D_PR_PTHREADS -UHAVE_CVAR_BUILT_ON_SEM now.c
> fatal error: gnu/stubs-32.h: No such file or directory
Something is wrong in the above. Both -m64 and -m32 are specified. The later
takes priority. This is causing the compiler to attempt a 32-bit compile,
automatically including "gnu/stubs-32.h", which doesn't exist because you are
building for a 64-bit target.
So it appears there is a bug in the nspr integration.
--Mark
>
>
> Can you help me to find the solution
>
> Chinmaya
>
>
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
next prev parent reply other threads:[~2011-05-04 4:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 4:19 Error in pulling nspr package chinmaya hoshing
2011-05-04 4:51 ` Mark Hatle [this message]
2011-05-04 6:16 ` chinmaya hoshing
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=4DC0DB68.1040303@windriver.com \
--to=mark.hatle@windriver.com \
--cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.