From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Re: Re:cross compilation of BlueZ for MIPS
Date: Wed, 23 Mar 2005 13:25:40 +0100 [thread overview]
Message-ID: <1111580740.22872.152.camel@pegasus> (raw)
In-Reply-To: <20050323044813.25763.qmail@web8508.mail.in.yahoo.com>
Hi,
> >when i compile i get error like non structure ember
> >"nice" in core.c file.
>
> >the Bluetooth kernel source code uses more than one
> >core.c and I only that it must be the kernel source,
> >because a nice member doesn"t exists inside the
> >userspace code. Provide a the full error message and
> >explain what you are doing, because otherwise such
> >posts are useless.
>
> After patching(patch2.4.20-mh18),enabling BNEP and
> HIDP support in menuconfig, when i compile using cross
> toolchain i get error message as given below.If i
> doesnot include BNEP and HIDP it successfully compiles
> with rfcomm support.
>
> ..compiling stuff.......
> ........................
> make[4]: Entering directory
> `/home/08_03_05_project/kernels/linux-2.4.20/net/bluetooth/bnep'
> mips_fp_le-gcc -D__KERNEL__
> -I/home/08_03_05_project/kernels/linux-2.4.20/include
> -Wall -Wstrict-prototypes -Wno-trigraphs -O2
> -fno-strict-aliasing -fno-common -g -ggdb
> -fno-omit-frame-pointer
> -I
> /home/08_03_05_project/kernels/linux-2.4.20/include/asm/gcc
> -G 0 -mno-abicalls -fno-pic -pipe -mtune=r4600
> -mips32 -Wa,--trap -nostdinc -iwithprefix include
> -DKBUILD_BASENAME=core -c -o core.o core.c
> core.c: In function `bnep_session':
> core.c:482: error: structure has no member named
> `nice'
> make[4]: *** [core.o] Error 1
> .......................
> .......................
> make: *** [_dir_net] Error 2
this actually means that your kernel contains another backport that is
not mainline. The -mh patches are only tested with mainline. In your
case replacing that line with "set_user_nice(current, -15);" may helps.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-03-23 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 4:48 [Bluez-users] Re: Re:cross compilation of BlueZ for MIPS mahabaleshwara k
2005-03-23 12:25 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-24 5:12 mahabaleshwara k
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=1111580740.22872.152.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.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 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.