RE: UPDATE: grep problem

["Dave Korn" <dk at artimi dot com>]

> -----Original Message-----
> From: gcc-owner On Behalf Of Terry L Moore
> Sent: 29 June 2004 15:20

> Hi all exhalted GNU gurus,
>     Can anyone even point to where I might be blowing this?  
> I would be happy to 
> furnish more information.  I changed the single quotes to 
> double quotes inside 
> the Makefile in the libjava directory.  Here is the result:

  Dunno a lot about this, but one thing jumps out at me:

> Creating list of files to link...
> /bin/ksh ./libtool --tag=CXX --mode=link 

  You're using ksh; maybe it has unexpected semantics relating to command
line metachars and quoting.  Do you have SH=ksh defined in your environment?
You could try setting it to sh or bash and see if that makes it work.

  OTOH, you could be barking up the wrong tree here.  The backquoted grep
expression is used to generate an argument for the -version-info switch; and
the argument it passes is "5:0:0".  That's not a filename and if something
went wrong with the backquoted grep I wouldn't expect to see a message
complaining that an input file didn't exist, I'd expect to see one saying
that the version number was invalid.  So maybe the grep expression is
working fine, and something else is going wrong.  I notice one obvious
possiblity:

> libgcj.la -objectlist libgcj.objectlist \

  My local version of libtool doesn't have that option, so I haven't rtfm'd
it, but I'd guess that "--objectlist FILENAME" means "Open FILENAME and read
it a line at a time, treating each line as the name/path of an object file
to be linked in.", and I'd guess that libgcj.objectlist is either empty, has
a blank line that libtool passes as a linker input filename rather than
simply ignoring, or perhaps has the wrong kind of line-endings (dos/unix)
for your system, making libtool think it has alternate blank lines in it.

  Failing that, I don't know if libtool passes through the -v option, but it
might, in which case it would be worth cut-and-pasting the libtool command
line as you see it in the build output and adding the -v option before
trying it manually.  That way you'll see what flags and filenames libtool is
passing when it invokes the linker, and it might become more clear what's
going wrong.

    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....