Re: Building libraries

[punt <punt@kerrskorner.org>]

Well, I am not sure that is the issue.  It looks as if ar is never called, 
but the linker is:


gcc -r ../bin/libdatastore.a diskmulstor.o mapdatadisk.o
gcc: ../bin/libdatastore.a: No such file or directory


Note that ../bin/libdatastore.a is the library I am attempting to build. Even 
though I selected library in the link options, it is as if it was not 
accepted (As I stated before, the selection was "grayed", but one could 
select and change it).  This wasn't a problem on 4.52.







On Monday 14 May 2001 11:43, Ian Roxborough wrote:
> punt wrote:
> > As anyone gotten 5.0 to successfully build a library?  I noticed the link
> > option between library and executable is grayed, but still selectable.
> > When I select library, and do a build, it bombs at the link process (it
> > is not asking gcc or the librarian to create the lib file).
>
> The library building bits need to be revisited.  I'm not sure
> what problem you are having, but it may be related to flag order
> problems with the linker flags.
>
> When I wrote the backend build system I didn't pay attention
> to flag ordering and it seems "ar"  needs flags in a certain
> order.  This probably won't get fixed until a build engine
> rewrite.
>
> Ian.