Date: Sun, 16 Mar 2003 02:38:41 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [Ux2bs_Archive] No. 107 ************************************************** Saturday 15 March 2003 Number 107 ************************************************** Subjects for today 1 Building httpd : Sohnen-Moe Associates, Inc" 2 Re: Building httpd : Sohnen-Moe Associates, Inc" 3 Re: Building httpd : Andreas Buening **= Email 1 ==========================** Date: Sun, 16 Mar 2003 10:40:25 -0700 (MST) From: "Sohnen-Moe Associates, Inc" Subject: Building httpd -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Ok, thanks for the help so far with building apache's httpd v2.0.44. The crypt() package (gnuufc) worked well. Now there is some problem about linking. The build script uses a lot of ".la" files. The actual .lib files also exist, usually in a .lib/ directory somewhere. When the build goes to create an executable, a swag of "undefined symbol" errors emerge. The command line uses the .la file, not the .lib file, as input. There are also two copies of each .la, one in the source directory, and one in the .lib/ directory where the .lib is. The linker only gets the .la from the source dir. How does the linker find the actual .lib? The contents of the .la seems to not have any particularily useful information in that respect. ____________________________________________________________________ Sohnen-Moe Associates, Inc. 3906 West Ina Road #200-367 Tucson, AZ 85741-2295 email: sma at sohnen-moe.com Voice: 520.743.3936 Website: http://www.sohnen-moe.com FAX: 520.743.3656 ____________________________________________________________________ -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0 OS/2 for non-commercial use Comment: PGP 5.0 for OS/2 Charset: cp850 wj8DBQE+dLcJ5z5shEq8TYMRAkGbAKDiMETUFMxHU+83VQPJcN9WpLggbwCfRzFq uzBF5SsrJmh3Gf6wmY9s9dw= =fB8+ -----END PGP SIGNATURE----- _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 2 ==========================** Date: Sun, 16 Mar 2003 15:55:54 -0700 (MST) From: "Sohnen-Moe Associates, Inc" Subject: Re: Building httpd -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 16 Mar 2003 23:13:57 +0100, Andreas Buening wrote: >Sounds like libtool. > Hmm. I did hack configure to prevent it from using a special os/2 libtool, aplibtool.exe. The reason is that aplibtool.exe produced .la files of zero (0) length, even less useful than libtool. ____________________________________________________________________ Sohnen-Moe Associates, Inc. 3906 West Ina Road #200-367 Tucson, AZ 85741-2295 email: sma at sohnen-moe.com Voice: 520.743.3936 Website: http://www.sohnen-moe.com FAX: 520.743.3656 ____________________________________________________________________ -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0 OS/2 for non-commercial use Comment: PGP 5.0 for OS/2 Charset: cp850 wj8DBQE+dQD65z5shEq8TYMRAgETAJ0XzEYN9EU3iIoHbDTS3mQkFE385ACg2o5D dQ4eEDma7XyfOVBVwffzHzQ= =1d8I -----END PGP SIGNATURE----- _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs **= Email 3 ==========================** Date: Sun, 16 Mar 2003 23:13:57 +0100 From: Andreas Buening Subject: Re: Building httpd Sohnen-Moe Associates, Inc wrote: > Hello, > Ok, thanks for the help so far with building apache's httpd v2.0.44. The > crypt() package (gnuufc) worked well. > Now there is some problem about linking. The build script uses a lot of > ".la" files. The actual .lib files also exist, usually in a .lib/ directory > somewhere. When the build goes to create an executable, a swag of > "undefined symbol" errors emerge. The command line uses the .la file, not > the .lib file, as input. > There are also two copies of each .la, one in the source directory, and > one in the .lib/ directory where the .lib is. The linker only gets the .la > from the source dir. > > How does the linker find the actual .lib? The contents of the .la seems > to not have any particularily useful information in that respect. Sounds like libtool. The .la files are dummy library files that are part of the libtool interface. make calls libtool with that dummy library and libtool's builtin voodoo translates that to the "real" name and libtool finally calls gcc with the correct arguments. At least, that's the theory. ;-) Bye, Andreas -- One OS to rule them all, One OS to find them, One OS to bring them all and in the darkness bind them In the Land of Mordor where the Shadows lie. _______________________________________________ UX2BS mailing list UX2BS at os2ports.com http://os2ports.com/mailman/listinfo/ux2bs