From 314ed0a58bff27fb2753395d2e42174f12fc1f55 Mon Sep 17 00:00:00 2001 From: Eric Andersen Date: Wed, 12 Feb 2003 13:10:00 +0000 Subject: Some minor doc updates --- docs/uclibc.org/FAQ.html | 59 +++++++++++------------------------------------- 1 file changed, 13 insertions(+), 46 deletions(-) (limited to 'docs/uclibc.org') diff --git a/docs/uclibc.org/FAQ.html b/docs/uclibc.org/FAQ.html index 39861a018..11a3cef33 100644 --- a/docs/uclibc.org/FAQ.html +++ b/docs/uclibc.org/FAQ.html @@ -236,7 +236,7 @@ to the uClibc home page. builder from http://www.uclibc.org/downloads/toolchain/, or the uClibc buildroot system from - http://www.uclibc.org/downloads/buildroot/, ajust the Makefile + http://www.uclibc.org/downloads/buildroot/, adjust the Makefile settings to match your target system, and then run 'make'.

@@ -260,47 +260,6 @@ to the uClibc home page. run your shell on a real console... -

- - - I have code that uses constructors and destructors. Why is it - when I use uClibc, the ctors/dtors do not run? - - - - - The uClibc compiler wrapper toolchain by default, does not - enable constructor and destructor support for C code. It - only enables ctors/dtors support by default for C++ code. - If you have C code that uses ctors/dtors and you wish to use - the uClibc compiler wrapper toolchain, you will need to add - the --uclibc-ctors option to the gcc command line. i.e. - -

-	$ cat test.c 
-	#include 
-
-	void __attribute__((constructor)) my_ctor(void)
-	{
-	    char msg[]="I am a constructor!\n";
-	    write(2, msg, sizeof(msg));
-	}
-
-	int main(void)
-	{
-	    _exit(42);
-	}
-
-	$ /usr/i386-linux-uclibc/bin/i386-uclibc-gcc --uclibc-ctors ./test.c -o test
-	$ ./test 
-	I am a constructor!
-
- - Another option is to build a native uClibc toolchain. Native toolchains - always enable ctors/dtors support, even for C code. - - -

@@ -312,7 +271,13 @@ to the uClibc home page. First run 

export PATH=/usr/i386-linux-uclibc/bin:$PATH
(or similar adjusted for your target architecture) then run you can simply - run autoconf/automake and it should _just work_. + run autoconf/automake and it should _just work_. Unfortunately, a large + number of configure scripts (such as the one from openssh) try to execute + test applications using your target C library, even if you are cross- + compiling. This is bad, since it will prevent these programs from compiling. + You need to complain to the authors of these programs and ask them to fix + their broken configure scripts. + @@ -352,6 +317,8 @@ to the uClibc home page. http://www.uclibc.org/lists/uclibc/2002-August/006261.html in the uClibc mailing list archive. + You can store the value of TZ in the file '/etc/TZ' and uClibc will then + automagically use the specified setting.

@@ -470,9 +437,9 @@ to the uClibc home page. - If you prefer to contact us directly for payments (Erik has a credit card machine so - you can avoid making payments online), hardware donations, support requests, etc., you can - contact CodePoet Consulting here. + If you prefer to contact us directly for payments, hardware donations, + support requests, etc., you can contact + CodePoet Consulting here.

-- cgit v1.2.3