public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Jesper Hansen <qtxjesp@tn.etx.ericsson.se>
To: insight@sourceware.cygnus.com
Subject: Solaris compile problems
Date: Wed, 13 Oct 1999 04:51:00 -0000	[thread overview]
Message-ID: <3804723B.222A97D@tn.etx.ericsson.se> (raw)

Hi !


I'm trying to compile Insight (1999-10-04) on a Sparc/Solaris 2.6,
but get all kind of errors. I'm not a UNIX expert at all, so I have
no clue to what's wrong.

Did a ./configure, then make.

It compiles a few files, then I get :

gcc -DHAVE_CONFIG_H -I. -I. -I. -D_GNU_SOURCE -I. -I. -I./../include
-I./../intl -I../intl -g -O2 -c elf.c
In file included from /usr/include/sys/old_procfs.h:27,
                 from /usr/include/sys/procfs.h:29,
                 from elf.c:4799:
/usr/include/sys/procfs_isa.h:23: parse error before `instr_t'
/usr/include/sys/procfs_isa.h:23: warning: data definition has no type
or storage class
/usr/include/sys/procfs_isa.h:87: parse error before `uint32_t'
/usr/include/sys/procfs_isa.h:87: warning: no semicolon at end of struct
or union

e.t.c.

This was when I tried compile gdb-4-18. When compilling insight, I get
the same if I do
"make all-gdb". Running only "make", I get a similar error from
terminal.c->termdep.h->
termios.h->sys/termios.h, complaining about the uint32_t type. 

Any ideas ??

I'd prefer to get hands on some binaries for sparc/solaris2.6, for both
gdb and insight,
so I can avoid all this troubles. I also need gdb, as out current gdb,
is modified beyond
recognition, so I need a "local" version.

I hope you can help me with some of this.

Thanks in advance.


Best regards,

Jesper


-- 
Jesper Hansen			Ericsson Telecom   
KnowIT Electronics AB		TN/ETX/XA/KD
http://www.knowit.se		http://www.tn.etx.ericsson.se              
E-mail: jesperh@knowit.se	qtxjesp@tn.etx.ericsson.se
Phone: +46 (708) 18 09 20	Memo: ERI.EXTR.QTXJESP

                 reply	other threads:[~1999-10-13  4:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3804723B.222A97D@tn.etx.ericsson.se \
    --to=qtxjesp@tn.etx.ericsson.se \
    --cc=insight@sourceware.cygnus.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).