Re: Problem(s) With FreeBSD-Current
On Sat, Sep 29, 2001 at 05:48:37PM -0700, Luigi Rizzo wrote: Hello, I have tried to compile FreeBSD Current (several times) over the last couple of days and get the following message when trying to run XFree86 and a number of other applications: /user/lib/libpam.so.1 : Undefined symbol __stdoutp... Does anyone else have the same problem ?? same here (though cross-compilig CURRENT on 4.3), for me the fix was to revert the sep.20 change on src/include/stdio.h @@ -198,7 +198,7 @@ __END_DECLS #endif /* To be removed by 5.0-RELEASE */ -#if (defined(__i386__) || defined(__alpha__)) !defined(_FIXED_STDIO) +#if (defined(__i386__) || defined(__alpha__)) defined(_OLD_STDIO) #definestdin (__sF[0]) #definestdout (__sF[1]) #definestderr (__sF[2]) Maybe it is the wrong fix, but it did work. Yes, it's the wrong fix. If you actually go and read your -current mailbox, you'll find it very hard to avoid tripping over an email containing the correct fix. Kris PGP signature
Re: Problem(s) With FreeBSD-Current
Hello, I have tried to compile FreeBSD Current (several times) over the last couple of days and get the following message when trying to run XFree86 and a number of other applications: /user/lib/libpam.so.1 : Undefined symbol __stdoutp... Does anyone else have the same problem ?? same here (though cross-compilig CURRENT on 4.3), for me the fix was to revert the sep.20 change on src/include/stdio.h @@ -198,7 +198,7 @@ __END_DECLS #endif /* To be removed by 5.0-RELEASE */ -#if (defined(__i386__) || defined(__alpha__)) !defined(_FIXED_STDIO) +#if (defined(__i386__) || defined(__alpha__)) defined(_OLD_STDIO) #definestdin (__sF[0]) #definestdout (__sF[1]) #definestderr (__sF[2]) Maybe it is the wrong fix, but it did work. cheers luigi --+- Luigi RIZZO, [EMAIL PROTECTED] . ACIRI/ICSI (on leave from Univ. di Pisa) http://www.iet.unipi.it/~luigi/ . 1947 Center St, Berkeley CA 94704 Phone: (510) 666 2927 --+- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Problem(s) With FreeBSD-Current
Hello, I have tried to compile FreeBSD Current (several times) over the last couple of days and get the following message when trying to run XFree86 and a number of other applications: /user/lib/libpam.so.1 : Undefined symbol __stdoutp... Does anyone else have the same problem ?? Thanks, -- Glenn Gombert [EMAIL PROTECTED] - email (513) 587-2643 x2263 - voicemail/fax __ FREE voicemail, email, and fax...all in one place. Sign Up Now! http://www.onebox.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message
Re: Problem(s) With FreeBSD-Current
* Glenn Gombert [EMAIL PROTECTED] [010929 12:21] wrote: Hello, I have tried to compile FreeBSD Current (several times) over the last couple of days and get the following message when trying to run XFree86 and a number of other applications: /user/lib/libpam.so.1 : Undefined symbol __stdoutp... Does anyone else have the same problem ?? Yes, a lot of people. -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-hackers in the body of the message