RELENG_7_0 buildworld fails
I'm attempting to rebuild world after the latest security advisories, but am having trouble getting the build to complete. I'm following the instructions listed in the handbook [1], as I have done before, but keep tripping in the same spot. Originally I was getting the error from a `make buildworld`. I then moved my make.conf out of the way, thinking it could be something from there. $ ls -l /etc/make.conf -rw-r--r-- 1 root wheel 0 Sep 4 12:29 /etc/make.conf With an empty make.conf, I got the same results. Then I tried a make buildincludes. This fails in the same place. Here are the last few lines of the buildincludes: BEGIN === include/rpc (buildincludes) rpcgen -C -h -DWANT_NFS3 rpcb_prot.x -o rpcb_prot.h === kerberos5 (buildincludes) === kerberos5/doc (buildincludes) === kerberos5/tools (buildincludes) === kerberos5/tools/make-print-version (buildincludes) === kerberos5/tools/make-roken (buildincludes) === kerberos5/tools/asn1_compile (buildincludes) === kerberos5/lib (buildincludes) === kerberos5/lib/libasn1 (buildincludes) compile_et /usr/src/kerberos5/lib/libasn1/../../../crypto/heimdal/lib/asn1/asn1_err.et compile_et:No such file or directory *** Error code 1 Stop in /usr/src/kerberos5/lib/libasn1. *** Error code 1 Stop in /usr/src/kerberos5/lib. *** Error code 1 Stop in /usr/src/kerberos5. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. END $ uname -a FreeBSD hoenikker.aset.psu.edu 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #0: Thu Apr 17 12:44:09 EDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 Is there any advice on how I can rebuild my world? If I've forgotten any information, please let me know. -Derek. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: error allocating memory with realloc(). how can i increase max_allowed in the system?
On Tue, 12 Aug 2008, Jordi Moles Blanco wrote:
Hi,
i'm running a FreeBSD 7.0 amd64 machine and struggling with some C code
i'm writing.
In addition to the other comments already given, I think that it might
be useful for your learning experience to have some additional comments.
I've had some trouble with this home-made script as it keeps crashing
while launching a realloc() call.
I narrowed down the problem and here i'm sending you a short example of
code that crashes:
*
#include stdio.h
#include stdlib.h
int main()
{
int midataula;
midataula = 3000;
char *missatge = (char *)malloc(midataula * sizeof(char));
You should not cast the return value of malloc. [1]
missatge[0]='h';
missatge[1]='o';
missatge[2]='l';
missatge[3]='a';
Recall that malloc() makes no promises about the contents of the memory
allocated. I recommend, in the current style, adding:
missatge[4]='\0';
printf(\n\ntaula1: %s,missatge);
int voltes;
voltes = 0;
Traditionally in C, all variable declarations appear at the beginning of
the local scope. Declaring new variables mid-scope is valid in certain
off-shoots of C and may be acceptable in newer dialects/standards of the
language, but the majority of C programmers might make certain
assumptions about your code following older traditions.
This certainly is not too egregious, but while I was here, I thought I'd
mention it.
while(voltes4)
{
midataula = midataula+500;
realloc(missatge, midataula * sizeof(char));
voltes++;
}
printf(\n\ntaula2: %s,missatge);
}
*
this is a full working you can compile on your machine.
Like this... i get Segmentation fault (core dumped)
but if instead of while(voltes4) i use while(voltes3)
the script works fine with this output:
**
taula1: hola
taula2: hola
**
so... i guess there must be a limit in the system somewhere.
I've tried to reset all variables that i've seen in the sysctl -a list
refering to malloc, memory, mem, and so on... but so far i haven't fixed
the problem.
i'm running this script as root and in the /etc/login.conf file there's
only the default group with the unlimited values.
A part from that, if i perform a limit call, i get this:
*
# limit
cputime unlimited
filesize unlimited
datasize 33554432 kbytes
stacksize524288 kbytes
coredumpsize unlimited
memoryuseunlimited
vmemoryuse unlimited
descriptors 45000
memorylocked unlimited
maxproc 22500
sbsize unlimited
*
i've tried to resize datasize and stacksize, but the system won't let me
do so.
any idea how to solve this?
thanks.
Good luck with your programming and systems work!
-Derek.
[1] http://c-faq.com/malloc/mallocnocast.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kerberized CIFS client?
On Wed, 14 May 2008, Derek Taylor wrote: I would like to use smb/cifs with kerberos auth, but mount_smbfs doesn't seem to support this. Is anyone aware of an alternate means of performing a mount via smb/cifs or any patches to provide such functionality? I already have smbclient working with -k, but I am also interested in a mount. Having heard nothing yet, would it be advisable to try freebsd-hackers instead? Is more information about what I want and have tried necessary/advisable? Thanks, -Derek. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Kerberized CIFS client?
I would like to use smb/cifs with kerberos auth, but mount_smbfs doesn't seem to support this. Is anyone aware of an alternate means of performing a mount via smb/cifs or any patches to provide such functionality? I already have smbclient working with -k, but I am also interested in a mount. Thanks -Derek. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
