public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Nurdin Premji <npremji@redhat.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: Tim Moore <timoore@redhat.com>, frysk@sourceware.org
Subject: Re: build problems with fresh checkout
Date: Fri, 23 Mar 2007 18:05:00 -0000	[thread overview]
Message-ID: <460416E2.4080204@redhat.com> (raw)
In-Reply-To: <20070323125236.GA20015@ca-server1.us.oracle.com>

A patch has been committed which creates a dummy libunwind-i386 directory.
Builds with plain make should work again.

Kris Van Hees wrote:
> Nightly auto-builds indicate that both full checkout and incremental
> update fail due to a somewhat scary absence of a
> frysk-imports/libunwind-i386 directory.
>
> 	Kris
>
> On Fri, Mar 23, 2007 at 10:18:59AM +0100, Tim Moore wrote:
>   
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> gcj: ./libunwind-i386/src/.libs/libunwind-x86.a: No such file or directory
>> make[3]: *** [fryski] Error 1
>>
>> Looks like something is missing from the libunwind-x86 merge...
>>
>> Tim
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.7 (GNU/Linux)
>> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>>
>> iD8DBQFGA5uDeDhWHdXrDRURAnO/AJ0d5BWNjs2v8grqlC6jhUsTVa6bTwCgv7f4
>> KgQyRyq92cQ+V/0tiS7tK/g=
>> =Ci9x
>> -----END PGP SIGNATURE-----
>>     

  reply	other threads:[~2007-03-23 18:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-23  9:19 Tim Moore
2007-03-23 12:53 ` Kris Van Hees
2007-03-23 18:05   ` Nurdin Premji [this message]
2007-03-23 13:49 ` Rick Moseley
2007-03-23 15:18   ` Nurdin Premji

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=460416E2.4080204@redhat.com \
    --to=npremji@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=kris.van.hees@oracle.com \
    --cc=timoore@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).