Re: /usr/bin/file

Re: /usr/bin/file

[Ralf Baechle]

On Fri, Aug 10, 2001 at 01:59:59PM +1000, Salisbury, Roger wrote:

> how would I update /usr/bin/file ??
> ./configure spits this out
> 
> *** Warning: the command libtool uses to detect shared libraries,
> *** /usr/bin/file, produces output that libtool cannot recognize.
> *** The result is that libtool may fail to recognize shared libraries
> *** as such.  This will affect the creation of libtool libraries that
> *** depend on shared libraries, but programs linked with such libtool
> *** libraries will work regardless of this problem.  Nevertheless, you
> *** may want to report the problem to your system manager and/or to
> *** bug-libtool@gnu.org

That's a libtool bug.  My RH 7.0 port has the fix.

  Ralf

Re: /usr/bin/file

[Maciej W. Rozycki]

On Fri, 10 Aug 2001, Ralf Baechle wrote:

> That's a libtool bug.  My RH 7.0 port has the fix.

 Libtool doesn't really need the file program for decent shared library
systems.  Linux/ELF is one of them and the current CVS version of libtool
shouldn't depend on file for MIPS/Linux anymore. 

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +

Re: /usr/bin/file

[Ralf Baechle]

On Fri, Aug 10, 2001 at 03:37:58PM +0200, Maciej W. Rozycki wrote:

>  Libtool doesn't really need the file program for decent shared library
> systems.  Linux/ELF is one of them and the current CVS version of libtool
> shouldn't depend on file for MIPS/Linux anymore. 

We're talking about old code here.

The fact that each package based on libtool is carrying it's own copy of
libtool around doesn't exactly help to eleminate old libtool copies
quickly either.

  Ralf

Re: /usr/bin/file

[Maciej W. Rozycki]

On Fri, 10 Aug 2001, Ralf Baechle wrote:

> The fact that each package based on libtool is carrying it's own copy of
> libtool around doesn't exactly help to eleminate old libtool copies
> quickly either.

 It's worth to run `libtoolize -c -f' before building any libtool-based
software. 

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +

Re: /usr/bin/file

[Ralf Baechle]

On Mon, Aug 13, 2001 at 01:32:19PM +0200, Maciej W. Rozycki wrote:

> > The fact that each package based on libtool is carrying it's own copy of
> > libtool around doesn't exactly help to eleminate old libtool copies
> > quickly either.
> 
>  It's worth to run `libtoolize -c -f' before building any libtool-based
> software. 

That results in build failures for a few rpms.  Many packages already do
that but unfortunately not all.

  Ralf

Re: /usr/bin/file

[Maciej W. Rozycki]

On Mon, 13 Aug 2001, Ralf Baechle wrote:

> >  It's worth to run `libtoolize -c -f' before building any libtool-based
> > software. 
> 
> That results in build failures for a few rpms.  Many packages already do
> that but unfortunately not all.

 Well, libtool is pretty self-contained, but you may try to regenerate
scripts as well.  If that fails, too, the software needs to be fixed
sooner or later.  Look at my packages for a number of updates in this
area.

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +

RE: /usr/bin/file

[Salisbury, Roger]

where do I get "libtoolize"

Still trying to update everything.

binutils-2.9.5.0.37 seems ok. although runtest not found.( needs testsuite,
which needs DejaGnu from  ftp ://gcc.gnu.org/pub/gcc/infrastructure  BUT the
site is  currently down.

glibc-2.2.3 needs  gcc-3.0 it seems. (checking version of gcc...
egcs-2.91.66, bad ...*** Some critical program is missing or too old
)

gcc-3.0  needs rectification in [libgcc_s.so]  & [libgcc.a]  it seems (see
make error below!)


Any idea Anyone please.

###############################################################
bash-2.04# pwd
/gcc-3.0
bash-2.04#make 
...
...
/usr/local/mips-unknown-linux-gnu/bin/ld: bfd assertion fail
elf32-mips.c:8348
/usr/local/mips-unknown-linux-gnu/bin/ld: bfd assertion fail
elf32-mips.c:8348
/usr/local/mips-unknown-linux-gnu/bin/ld: bfd assertion fail
elf32-mips.c:8348
/usr/local/mips-unknown-linux-gnu/bin/ld: bfd assertion fail
elf32-mips.c:8348
collect2: ld returned 1 exit status
make[2]: *** [libgcc_s.so] Error 1
make[2]: Leaving directory `/gcc-3.0/gcc'
make[1]: *** [libgcc.a] Error 2
make[1]: Leaving directory `/gcc-3.0/gcc'
make: *** [all-gcc] Error 2
bash-2.04#
###############################################################

Any idea Anyone please.

Thanks 
Roger



> -----Original Message-----
> From:	Maciej W. Rozycki [SMTP:macro@ds2.pg.gda.pl]
> Sent:	Tuesday, 14 August 2001 2:28 am
> To:	Ralf Baechle
> Cc:	Salisbury, Roger; linux-mips@oss.sgi.com; linux-mips@fnet.fr
> Subject:	Re: /usr/bin/file
> 
> On Mon, 13 Aug 2001, Ralf Baechle wrote:
> 
> > >  It's worth to run `libtoolize -c -f' before building any
> libtool-based
> > > software. 
> > 
> > That results in build failures for a few rpms.  Many packages already do
> > that but unfortunately not all.
> 
>  Well, libtool is pretty self-contained, but you may try to regenerate
> scripts as well.  If that fails, too, the software needs to be fixed
> sooner or later.  Look at my packages for a number of updates in this
> area.
> 
> -- 
> +  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
> +--------------------------------------------------------------+
> +        e-mail: macro@ds2.pg.gda.pl, PGP key available        +

Re: /usr/bin/file

[Ralf Baechle]

On Tue, Aug 14, 2001 at 11:40:48AM +1000, Salisbury, Roger wrote:

> where do I get "libtoolize"

GNU libtools.

> glibc-2.2.3 needs  gcc-3.0 it seems. (checking version of gcc...
> egcs-2.91.66, bad ...*** Some critical program is missing or too old
> )

> gcc-3.0  needs rectification in [libgcc_s.so]  & [libgcc.a]  it seems (see
> make error below!)

linker problem.  If you still run gcc 1.2 then your ld is probably to
antique anyway.

  Ralf

Re: /usr/bin/file

[Andreas Jaeger]

"Salisbury, Roger" <Roger.Salisbury@team.telstra.com> writes:

> where do I get "libtoolize"
>
> Still trying to update everything.
>
> binutils-2.9.5.0.37 seems ok. although runtest not found.( needs testsuite,
> which needs DejaGnu from  ftp ://gcc.gnu.org/pub/gcc/infrastructure  BUT the
> site is  currently down.

> glibc-2.2.3 needs  gcc-3.0 it seems. (checking version of gcc...
> egcs-2.91.66, bad ...*** Some critical program is missing or too old
> )
>
> gcc-3.0  needs rectification in [libgcc_s.so]  & [libgcc.a]  it seems (see
> make error below!)

GCC 3.0 will not compile a correct glibc at all, wait for GCC 3.0.1
and glibc 2.2.5 and read the glibc announcements,

Andreas
-- 
 Andreas Jaeger
  SuSE Labs aj@suse.de
   private aj@arthur.inka.de
    http://www.suse.de/~aj

RE: /usr/bin/file

[Maciej W. Rozycki]

On Tue, 14 Aug 2001, Salisbury, Roger wrote:

> where do I get "libtoolize"

 It's included in the libtool distribution.

> glibc-2.2.3 needs  gcc-3.0 it seems. (checking version of gcc...
> egcs-2.91.66, bad ...*** Some critical program is missing or too old
> )

 Gcc 2.95.3 is fine if patched appropriately. 

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +