From: george anzinger <george@mvista.com>
To: Helge Hafting <helge.hafting@broadpark.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.47-bk4 compile failure, due to crypto
Date: Fri, 15 Nov 2002 21:57:02 -0800 [thread overview]
Message-ID: <3DD5DE2E.9CC9941A@mvista.com> (raw)
In-Reply-To: 3DD53234.B0F1C9C8@broadpark.no
The QUICK fix is to turn the offending function into a
"#define"...
-g
Helge Hafting wrote:
>
> I get this, even if I de-selects all the crypto stuff.
> Helge Hafting
>
> make -f scripts/Makefile.build obj=net/core
> gcc -Wp,-MD,net/core/.skbuff.o.d -D__KERNEL__ -Iinclude -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2
> -march=i686 -Iarch/i386/mach-generic -nostdinc -iwithprefix include
> -DKBUILD_BASENAME=skbuff -DKBUILD_MODNAME=skbuff -c -o
> net/core/skbuff.o net/core/skbuff.c
> In file included from include/net/xfrm.h:6,
> from net/core/skbuff.c:61:
> include/linux/crypto.h: In function `crypto_tfm_alg_modname':
> include/linux/crypto.h:202: dereferencing pointer to incomplete type
> include/linux/crypto.h:205: warning: control reaches end of non-void
> function
> make[2]: *** [net/core/skbuff.o] Error 1
> make[1]: *** [net/core] Error 2
> make: *** [net] Error 2
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
George Anzinger george@mvista.com
High-res-timers:
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml
prev parent reply other threads:[~2002-11-16 5:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 17:43 2.5.47-bk4 compile failure, due to crypto Helge Hafting
2002-11-16 5:57 ` george anzinger [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=3DD5DE2E.9CC9941A@mvista.com \
--to=george@mvista.com \
--cc=helge.hafting@broadpark.no \
--cc=linux-kernel@vger.kernel.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