From: UnixOS2 Archive To: "UnixOS2 Archive" Date: Thu, 19 Sep 2002 04:37:08 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [UnixOS2_Archive] No. 325 ************************************************** Wednesday 18 September 2002 Number 325 ************************************************** Subjects for today 1 Re: Final FHS : Andreas Buening 2 Re: gcc 3.0.3: where does it look for libraries? : Andreas Buening 3 gcc 3.0.3: making the emx 'test' directory... : Thomas Hoffmann **= Email 1 ==========================** Date: Thu, 19 Sep 2002 22:46:01 +0200 From: Andreas Buening Subject: Re: Final FHS Adrian Gschwend wrote: > > On Sat, 14 Sep 2002 02:16:29 +0200, Andreas Buening wrote: > > >If you have anything to mention about this standard then speak now > >or be silent forever. ;-) > > looks very good to me, just one question: Is there a defined way about > how we create the packet name? I mean do we have versioning numbers > included as well, if so in which form? I'm again working on a openssh > package and I would like to release that shortly I'd say we should use the "standard" naming scheme. foo version 1.2.3 is stored in foo-1_2_3.zip which contains the directory foo-1.2.3. 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. **= Email 2 ==========================** Date: Thu, 19 Sep 2002 22:46:24 +0200 From: Andreas Buening Subject: Re: gcc 3.0.3: where does it look for libraries? Thomas Hoffmann wrote: > > This is possibly a rather dumb question, but today I installed gcc 3.0.3 > into a "FHS-like" hierarchy (starting at /usr) and tried to build a very > simple test program. The compile stage runs through, but the linker does > not find the gcc libraries in /usr/lib: it seems to be configured to > look only below gcc-lib and in the mt or st subdirectory of /usr/lib. [gcc output] > Adding -L/usr/lib helps, but a comparison w/ gcc 2.8.1 shows, that the > latter includes /emx/lib and /usr/lib already by default. > > Can anybody comment on this? All dll's have to be in /lib or /usr/lib because only these two directories are in LIBPATH. All applications including gcc may install their own library-like stuff into subdirectories of /usr/lib if they want but _only_ if these files are used exclusively by this specific application. This means gcc may install its own .a and .lib files into subdirectories of /usr/lib. But all libraries that may be used also by other compilers, other versions of gcc or any other programs have to be installed into /usr/lib directly. And gcc had better search $UNIXROOT/lib, $UNIXROOT/usr/lib and $UNIXROOT/usr/local/lib by default to get rid of LIBRARY_PATH. If you can fix it, please do so. The gcc maintainers should know how to add an additional path. 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. **= Email 3 ==========================** Date: Thu, 19 Sep 2002 23:16:48 +0100 From: Thomas Hoffmann Subject: gcc 3.0.3: making the emx 'test' directory... Now that I have gcc 3.0.3 working (I added set LIBRARY_PATH=d:/usr/lib to my config.sys), I thought it would make sense to try to compile the files of emx's test directory. Of course there are some changes of the makefile necessary (e.g. introduction of g++ for .cpp files). But it would be interesting to compare the results from several people and discuss the reasons for failure, just to get a feeling of how gcc 3.0.3 compares to emx-gcc 2.8.1. Did anybody try this out already? (Background is: I would like to switch to gcc 3.0.3 for a rather big project and it would be good to "know" gcc 3.0.3 in comparison with 2.8.1, with which I an rather familiar.) -- Thomas Hoffmann Telephone: 49-351-4598831 thoffman at zappa.sax.de Dresden, Germany ..sig under construction ...