libtool and lib?

libtool and lib?

[Peter Shoebridge]

I'm trying to build the latest snapshot of insight under cygwin b20.1 and
get the following error about libtool and lib, plus something about
cygpath.

Anyone have a clue what I'm missing?

Thanks

Peter Shoebridge

echo timestamp > m68k-dis.lo
/bin/sh ./libtool --mode=compile
gcc -DHAVE_CONFIG_H -I. -I../../insight-1999072
7/../insight-19990727/opcodes -I. -D_GNU_SOURCE -I. -I../../insight-199907
27/../
insight-19990727/opcodes -I../bfd -I../../insight-19990727/../insight-1999
0727/o
pcodes/../include -I../../insight-19990727/../insight-19990727/opcodes/../
bfd  -
I../../insight-19990727/../insight-19990727/opcodes/../intl -I../intl    -
g -O2
-W -Wall -c ../../insight-19990727/../insight-19990727/opcodes/m68k-opc.c
Usage: cygpath [-p|--path] (-u|--unix)|(-w|--windows) filename
  -u|--unix     print Unix form of filename
  -w|--windows  print Windows form of filename
  -p|--path     filename argument is a path
gcc -DHAVE_CONFIG_H -I. -I../../insight-19990727/../insight-19990727/opcod
es -I.
 -D_GNU_SOURCE -I. -I../../insight-19990727/../insight-19990727/opcodes -I
../bfd
 -I../../insight-19990727/../insight-19990727/opcodes/../include -I../../i
nsight
-19990727/../insight-19990727/opcodes/../bfd -I../../insight-19990727/../i
nsight
-19990727/opcodes/../intl -I../intl -g -O2 -W -Wall -c
../../insight-19990727/..
/insight-19990727/opcodes/m68k-opc.c -o m68k-opc.o
echo timestamp > m68k-opc.lo
/bin/sh ./libtool --mode=link gcc  -g -O2 -W -Wall  -o
libopcodes.la -rpath /gcc
-m68k/lib -release 2.9.5  dis-buf.lo disassemble.lo m68k-dis.lo
m68k-opc.lo
Usage: cygpath [-p|--path] (-u|--unix)|(-w|--windows) filename
  -u|--unix     print Unix form of filename
  -w|--windows  print Windows form of filename
  -p|--path     filename argument is a path
libtool: link: warning: undefined symbols not allowed in i686-pc-cygwin32
shared
 libraries
mkdir .libs
lib /OUT:.libs/libopcodes.lib  dis-buf.o disassemble.o m68k-dis.o
m68k-opc.o
./libtool: lib: command not found
make[3]: *** [libopcodes.la] Error 127

Re: libtool and lib?

[Keith Seitz]

On Thu, 5 Aug 1999, Peter Shoebridge wrote:

> I'm trying to build the latest snapshot of insight under cygwin b20.1 and
> get the following error about libtool and lib, plus something about
> cygpath.
> 
> Anyone have a clue what I'm missing?

As I recall, libtool has changed. The insight snapshot uses the newer
libtool. I am uncertain if B20.1 can be used to build the debugger: B20.1
is quite old. It _should_ be possible to hack around this problem.
(You could try, for example, installing a newer libtool or hacking 
makefiles to support older libtool.)

Mumit Kahn has managed to build Insight for cygwin native using the cygwin
snapshots. If you would just like a prebuilt binary, take a look at the
insight archives on sourceware. This message was cross-posted to the win32
mailing list:

http://sourceware.cygnus.com/ml/insight/1999-q3/msg00005.html

Keith

Re: libtool and lib?

[Mumit Khan]

Keith Seitz <keiths@cygnus.com> writes:
> On Thu, 5 Aug 1999, Peter Shoebridge wrote:
> 
> > I'm trying to build the latest snapshot of insight under cygwin b20.1 and
> > get the following error about libtool and lib, plus something about
> > cygpath.
> > 
> > Anyone have a clue what I'm missing?
> 
> As I recall, libtool has changed. The insight snapshot uses the newer
> libtool. I am uncertain if B20.1 can be used to build the debugger: B20.1
> is quite old. It _should_ be possible to hack around this problem.
> (You could try, for example, installing a newer libtool or hacking 
> makefiles to support older libtool.)
> 
> Mumit Kahn has managed to build Insight for cygwin native using the cygwin
> snapshots. If you would just like a prebuilt binary, take a look at the
> insight archives on sourceware. This message was cross-posted to the win32
> mailing list:
> 
> http://sourceware.cygnus.com/ml/insight/1999-q3/msg00005.html
> 

Actually, I never build anything on a windows box if I can help it. I 
cross-compiled Insight on a linux box, and had to make a few tweaks to
fix minor configuration buglets when building for x86-win32 host. To
be strictly correct, I should use the term canadian cross here, not
just cross (the target and host machines were both different than build 
machine).

Unfortunately, I blew away my source tree before I had a chance to commit
the changes. I'll hopefully retry this in the near future and forward the
patches to the list.

Insight *should* build on Cygwin b20.1, but I doubt if you can do that
without working around various, albeit minor, configuration issues. 

Unless you have strong need for building it yourself (eg., to fix problems), 
just use the binaries.

Regards,
Mumit

Re: libtool and lib?

[Peter Shoebridge]

I found libtool and will try again tonight. I'm trying to build a m68k-coff
version of the debugger otherwise I would use your bineries.

Thanks

Peter

----- Original Message -----
From: Mumit Khan <khan@xraylith.wisc.EDU>
To: Keith Seitz <keiths@cygnus.com>
Cc: Peter Shoebridge <peter@zeecube.com>; Insight (GDB GUI)
<insight@sourceware.cygnus.com>
Sent: Friday, August 06, 1999 11:47 AM
Subject: Re: libtool and lib?


> Keith Seitz <keiths@cygnus.com> writes:
> > On Thu, 5 Aug 1999, Peter Shoebridge wrote:
> >
> > > I'm trying to build the latest snapshot of insight under cygwin b20.1
and
> > > get the following error about libtool and lib, plus something about
> > > cygpath.
> > >
> > > Anyone have a clue what I'm missing?
> >
> > As I recall, libtool has changed. The insight snapshot uses the newer
> > libtool. I am uncertain if B20.1 can be used to build the debugger:
B20.1
> > is quite old. It _should_ be possible to hack around this problem.
> > (You could try, for example, installing a newer libtool or hacking
> > makefiles to support older libtool.)
> >
> > Mumit Kahn has managed to build Insight for cygwin native using the
cygwin
> > snapshots. If you would just like a prebuilt binary, take a look at the
> > insight archives on sourceware. This message was cross-posted to the
win32
> > mailing list:
> >
> > http://sourceware.cygnus.com/ml/insight/1999-q3/msg00005.html
> >
>
> Actually, I never build anything on a windows box if I can help it. I
> cross-compiled Insight on a linux box, and had to make a few tweaks to
> fix minor configuration buglets when building for x86-win32 host. To
> be strictly correct, I should use the term canadian cross here, not
> just cross (the target and host machines were both different than build
> machine).
>
> Unfortunately, I blew away my source tree before I had a chance to commit
> the changes. I'll hopefully retry this in the near future and forward the
> patches to the list.
>
> Insight *should* build on Cygwin b20.1, but I doubt if you can do that
> without working around various, albeit minor, configuration issues.
>
> Unless you have strong need for building it yourself (eg., to fix
problems),
> just use the binaries.
>
> Regards,
> Mumit
>