public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: "Wiegert, Arnold" <Arnold.Wiegert@glenayre.com>
To: 'Mark Thornber' <emthornber@iee.org>
Cc: "'sourcenav@sources.redhat.com'" <sourcenav@sources.redhat.com>
Subject: RE: compiling/linking a parser under Solaris
Date: Mon, 09 Jul 2001 09:35:00 -0000	[thread overview]
Message-ID: <6A1BC64042DFD211903A0008C7C56704050369BB@vancouver_nt2.vancouver.glenayre.com> (raw)

HI,

with some help from the local Unix guru, we were able to find all the
libraries and finally get the file compiled and linked. 

Unfortunately, this is a 'backburner' job and I have to attend to a couple
of 'important' jobs for the next few days, but I will be getting back to
this problem and the will have to try and integrate the parser etc.

Thank you all for your help and comments. Will keep you posted of the
progress - or lack ;)

Arnold

-----Original Message-----
From: Mark Thornber [ mailto:emthornber@iee.org ]
Sent: Thursday, July 05, 2001 12:35 AM
To: Wiegert, Arnold
Cc: 'sourcenav@sources.redhat.com'
Subject: Re: compiling/linking a parser under Solaris


Arnold,

As Mo says, the missing library is flex, which is _not_ on Solaris by
default.  You will need to install from the usual places - try
http://www.sunfreeware.com


--MarkT

"Wiegert, Arnold" wrote:
> 
> Hi,
> 
> I've downloaded and installed SourceNavigator. It looks pretty good so
far.
> 
> However since most of our work involves cross-compiling under Solaris for
an
> embedded system running Motorola 68K CPUs, I need to add a assembly code
> parser for the 68K CPUs - using the Green Hills OASYS cross-compiler.
> 
> I have gotten as far as modifying a basic 68K..m4; it seems to get
> translated properly to C and using a version of a GNU C compiler, I get as
> far as the linking step, where it complains about a missing library:
> 
>         wiegert/scsi2:awiegert@fairmont[226] gmake test
>         gnucc -o abrowser abrowser.o -L../../../../sdk/lib -lm -ldl -lfl
> -lsnptools -ldbutils -lpafdb -ltcl8.1 -lutils
>         ld: fatal: library -lfl: not found
>         ld: fatal: File processing errors. No output written to abrowser
>         make: *** [abrowser] Error 1
>         awiegert/scsi2:awiegert@fairmont[227]
> 
> Where might I find this library on a Solaris system - I've already had to
> hunt down a GNU make and compiler :)
> 
> Thank you in advance for any help.
> Arnold
> ========================================================================
> 
> Arnold Wiegert
> Software Engineer               Tel: (604) 293-4399 ext.4814
> Glenayre Technologies           Email: awiegert@glenvan.glenayre.com
> 1570 Kootenay St.
> Vancouver, BC  V5K-5B8
> 
> ========================================================================

             reply	other threads:[~2001-07-09  9:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-09  9:35 Wiegert, Arnold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-04 13:45 Wiegert, Arnold
2001-07-04 14:50 ` Mo DeJong
2001-07-05  0:34 ` Mark Thornber

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6A1BC64042DFD211903A0008C7C56704050369BB@vancouver_nt2.vancouver.glenayre.com \
    --to=arnold.wiegert@glenayre.com \
    --cc=emthornber@iee.org \
    --cc=sourcenav@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).