> I am trying to prepare packages for the new MaxDB release 7.5.00.38 and
> am having problems with a new piece of code in there.
>
> The code in question looks like this and is known to work on Suse SLES9:
...
> # include
> are user-space applications not supposed to include any headers belo
On 9/22/06, Martin Kittel <[EMAIL PROTECTED]> wrote:
So this brings me back to me original problem: are user-space
applications allowed/supposed to use these headers? And if so, how are
they to be used if the headers rely on __KERNEL__ to be defined?
My understanding was that userspace should n
Am Freitag 22 September 2006 19:54 schrieb Martin Kittel:
> So this brings me back to me original problem: are user-space
> applications allowed/supposed to use these headers? And if so, how are
> they to be used if the headers rely on __KERNEL__ to be defined?
Did you try to comment out those inc
>> /usr/include/linux/seqlock.h:76: error: expected '=', ',', ';\
>> ', 'asm' or '__attribute__' before 'unsigned'
>> /usr/include/linux/seqlock.h:91: error: expected '=', ',', ';\
>> ', 'asm' or '__attribute__' before 'int'
>
> This comes from the __always_inline that is not defined. To define it
On Sep 21, Martin Kittel <[EMAIL PROTECTED]> wrote:
> I have no experience in this area, so I am just wondering: are
> user-space applications not supposed to include any headers below
> /usr/include/asm
Yes. The application is buggy.
--
ciao,
Marco
signature.asc
Description: Digital signature
Am Donnerstag 21 September 2006 20:09 schrieb Martin Kittel:
> In file included from /usr/include/asm-x86_64/vsyscall.h:4,
> from /usr/include/asm/vsyscall.h:8,
> from /usr/include/asm-x86_64/timex.h:11,
> from /usr/include/asm/timex.h:8,
>
Hi,
I am trying to prepare packages for the new MaxDB release 7.5.00.38 and
am having problems with a new piece of code in there.
The code in question looks like this and is known to work on Suse SLES9:
...
#ifdef LINUX
# include
typedef SAPDB_UInt8 u64;
# include
# include
# incl
7 matches
Mail list logo
