[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Conflicting getrlimit and setrlimit?

From: Dale Rossetti
Subject: Conflicting getrlimit and setrlimit?
Date: Fri, 21 Mar 2003 16:17:22 -0500

I installed Slackware 8.0 with as few options as I could. The kernel during 
install is 2.4.5. I've downloaded, installed and recompiled kernels 2.4.20 and 
2.5.65. I've also recompiled the 2.4.5 kernel.

I'm trying to install XFree86 4.3.0, glibc 2.3.2 and gcc 3.2.2. I need glibc 
2.3 or better for XFree86 4.3.0 and I need gcc better than 2.95.3 (currently 
installed) for glibc 2.3.2. I'm at a stumbling block with gcc. In the 
downloaded gcc-3.2.2/gcc/system.h, it declares both getrlimit and setrlimit. 
However, in /usr/include/sys/resource.h, the declarations are different.


# if defined (HAVE_DECL_GETRLIMIT) && !HAVE_DECL_GETRTLIMIT (Dale comments: 
isn't this pointless? Won't the statement always be false?)
#  ifndef getrlimit
struct rlimit;
#   endif
extern int getrlimit PARAMS ((int, struct rlimit *));
#  endif
# endif

# if defined (HAVE_DECL_SETRLIMIT) && !HAVE_DECL_SETRTLIMIT (Dale comments: 
Again, won't this always be false?)
#  ifndef setrlimit
struct rlimit;
#   endif
extern int setrlimit PARAMS ((int, const struct rlimit *));
#  endif
# endif


extern int getrlimit (__rlimit_resource_t __resource, struct rlimit *__rlimits) 
extern int setrlimit (__rlimit_resource_t __resource, __const struct rlimit 
*__rlimits) __THROW;

Just wondering if you've come across something similar or if I maybe missed a 
step when recompiling the kernels. Should I set up a symbolic link somewhere 
that points to a subdirectory in /usr/src/linux-2.5.65? I added/updated 
symbolic links:
/usr/include/asm --> /usr/src/linux-2.5.65/include/asm.
/usr/include/asm-generic --> /usr/src/linux-2.5.65/include/asm-generic.
/usr/include/linux --> /usr/src/linux-2.5.65/include/linux.

Thank you for your assistance.


Try AOL and get 1045 hours FREE for 45 days!

Get AOL Instant Messenger 5.1 for FREE! Download Now!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]