From: "Robert Cragie" <rcc@jennic.com>
To: "Ben Elliston" <bje@au1.ibm.com>, <sid@sources.redhat.com>
Subject: RE: error building SID
Date: Fri, 07 May 2004 10:00:00 -0000 [thread overview]
Message-ID: <NMEDLDELHPEFHOMFIJBHKEAGDEAA.rcc@jennic.com> (raw)
In-Reply-To: <s9roep29v0i.fsf@fs.ozlabs.ibm.com>
I couldn't get a CVS snapshot I checked out last night at about 2000 GMT to
build on Mandrake 10.0 - got exactly the same error as Ashutosh.
init_disassemble_info() is in opcodes/dis-init.c, which gets built into
libopcodes.a - right?
So it looks like libopcodes.a is not being included somehow when building
SID STATIC - that's about as much as I can figure at the moment!
Anyone any ideas?
Robert Cragie, Design Engineer
_______________________________________________________________
Jennic Ltd, Furnival Street, Sheffield, S1 4QT, UK
http://www.jennic.com Tel: +44 (0) 114 281 2655
_______________________________________________________________
> -----Original Message-----
> From: sid-owner@sources.redhat.com
> [mailto:sid-owner@sources.redhat.com]On Behalf Of Ben Elliston
> Sent: 06 May 2004 02:58
> To: Robert Cragie
> Cc: sid@sources.redhat.com
> Subject: Re: error building SID
>
>
> "Robert Cragie" <rcc@jennic.com> writes:
>
> > I have been following this thread and should point out that I
> > managed to build snapshot-20040424.tar.bz2 successfully on a SuSE
> > 7.2 linux system (gcc 2.95.3) without specifically needing anything
> > else, so please can you explain what you mean by "You need more than
> > the sid/ subdirectory nowdays."? (note I didn't get a chance to try
> > it). I think Ashustosh is also using snapshots.
>
> Well, some SID components rely on BFD, for example. It is possible
> that the snapshots include all of the requisite directories. Is that
> right, Frank?
>
> > I think the issues are to do with building in a cygwin environment
> > which I have not attempted (yet) - are there packages missing in
> > this environment which are normally present in a Linux environment?
>
> I used to build SID regularly on Cygwin. There should not be anything
> major to make it work. If there is, please report it here.
>
> Ben
>
>
next prev parent reply other threads:[~2004-05-07 10:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 12:18 Ashutosh Vyas
2004-05-05 0:47 ` Ben Elliston
2004-05-05 8:58 ` Robert Cragie
2004-05-05 9:49 ` Ashutosh
2004-05-06 1:58 ` Ben Elliston
2004-05-07 10:00 ` Robert Cragie [this message]
2004-05-07 17:18 ` Frank Ch. Eigler
-- strict thread matches above, loose matches on Subject: below --
2008-12-11 21:28 Error Building SID Shamik Datta
2008-12-11 23:50 ` Frank Ch. Eigler
[not found] ` <239b036a0812121037p534a4ca1t759ea754c7ebad62@mail.gmail.com>
[not found] ` <20081212195729.GB1200@redhat.com>
[not found] ` <239b036a0812130700v2ba9e054yb63be621c223b769@mail.gmail.com>
[not found] ` <239b036a0812150100h1330ba92nb89c0597268a8c01@mail.gmail.com>
[not found] ` <20081215175754.GA7910@redhat.com>
[not found] ` <239b036a0812151202y5ed2a0a4y486ce4905503de67@mail.gmail.com>
2008-12-15 20:39 ` Frank Ch. Eigler
[not found] ` <239b036a0812211557h2d73685pf3ccd01a5ac3d6da@mail.gmail.com>
2008-12-25 18:45 ` Frank Ch. Eigler
2007-10-31 13:45 Error building SID badiu raz
2007-10-31 14:58 ` Dave Brolley
2007-10-31 17:25 ` Dave Brolley
2003-06-20 21:17 error " Partha Palit
2003-06-20 21:31 ` Frank Ch. Eigler
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=NMEDLDELHPEFHOMFIJBHKEAGDEAA.rcc@jennic.com \
--to=rcc@jennic.com \
--cc=bje@au1.ibm.com \
--cc=sid@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).