Building libraries

Building libraries

[punt]

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).

Anyone else have this ?

Charles

Re: Building libraries

[Ian Roxborough]

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.

Re: Building libraries

[punt]

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.

RE: Building libraries

[Bernard Dautrevaux]

> -----Original Message-----
> From: punt [ mailto:punt@kerrskorner.org ]
> Sent: Tuesday, May 15, 2001 1:55 AM
> To: Ian Roxborough; punt
> Cc: sourcenav@sourceware.cygnus.com
> Subject: Re: Building libraries
> 
> 
> 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
> 

Looks like SN thinks the archiver is named gcc... Or is it your settings?

Just my .02 euro

Bernard

--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel:	+33 (0) 1 47 68 80 80
Fax:	+33 (0) 1 47 88 97 85
e-mail:	dautrevaux@microprocess.com
		b.dautrevaux@usa.net
-------------------------------------------- 

RE: Building libraries

[Buczko, Michal]

Hi,

I had a simmilar problem with building a library using sn and after changing
linker from 'gcc' to 'ar' is seems to work perfectly but i think there is
another bug. building executable file gcc was unable to generete output
because all libraries i want to include are added to command line like this:


gcc -o ble ble1.o ble2.o /usr/lib/libncurses.a /usr/lib/libgcontrol.a

this causes lots of conflicts (no matter what is the order of these
libraries), but after replacing /usr/lib/libncurses.a with -lncurses and
/usr/lib/libgcontrol.a with -lgcontrol everything goes ok. that`s way i
wrote a simple patch that renames all included libraries from
/usr/lib/lib*.a to -l*. it isn`t too flexible but it should work.

file: gui/buildtarget.tcl

  method GetLibraryFiles {} {
        regsub -all -nocase {(/usr/lib/lib)([^\.]+)(\.a)} ${LibFiles} {-l\2}
LibFiles   <---- added line
        return ${LibFiles}
  }


Best regards,

Michal Buczko
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
DomData sp. z.o.o
E-mail: Michal.Buczko@domdata.depfa-it.com
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> -----Original Message-----
> From: Bernard Dautrevaux [ mailto:Dautrevaux@microprocess.com ]
> Sent: Tuesday, May 15, 2001 9:41 AM
> To: 'punt'; Ian Roxborough
> Cc: sourcenav@sourceware.cygnus.com
> Subject: RE: Building libraries
> 
> 
> > -----Original Message-----
> > From: punt [ mailto:punt@kerrskorner.org ]
> > Sent: Tuesday, May 15, 2001 1:55 AM
> > To: Ian Roxborough; punt
> > Cc: sourcenav@sourceware.cygnus.com
> > Subject: Re: Building libraries
> > 
> > 
> > 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
> > 
> 
> Looks like SN thinks the archiver is named gcc... Or is it 
> your settings?
> 
> Just my .02 euro
> 
> Bernard
> 
> --------------------------------------------
> Bernard Dautrevaux
> Microprocess Ingenierie
> 97 bis, rue de Colombes
> 92400 COURBEVOIE
> FRANCE
> Tel:	+33 (0) 1 47 68 80 80
> Fax:	+33 (0) 1 47 88 97 85
> e-mail:	dautrevaux@microprocess.com
> 		b.dautrevaux@usa.net
> -------------------------------------------- 
>