From: Nurdin Premji <npremji@redhat.com>
To: Mike Cvet <mcvet@redhat.com>
Cc: frysk@sourceware.org
Subject: Re: Libunwind 20070224 merge to happen very soon.
Date: Wed, 21 Mar 2007 18:19:00 -0000 [thread overview]
Message-ID: <4601771A.3020506@redhat.com> (raw)
In-Reply-To: <46017410.9030702@redhat.com>
On inspection, it seems like Mike's build created the libunwind-i386
directory but then just didn't run the configure inside of it. Running
the configure and make by hand fixed it. But why they didn't get run
through the autogen script I dunno. They worked on all my test machines...
Mike Cvet wrote:
> Nurdin Premji wrote:
>> This has just been completed.
>> Nurdin Premji wrote:
>>> The libunwind-import-20070313-branch (which contains the libunwind
>>> 20070224 snapshot) will be merged to main more than likely today.
>>> Tomorrow at the latest.
>>
> Build is broken on my machine - Intel Core 2 Duo x86_64
>
> make[4]: Entering directory
> `/home/mcvet/workspace/build/frysk-imports/libunwind-i386'
> make[4]: *** No targets specified and no makefile found. Stop.
>
> - Mike
next prev parent reply other threads:[~2007-03-21 18:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 13:13 Nurdin Premji
2007-03-21 17:50 ` Nurdin Premji
2007-03-21 18:07 ` Mike Cvet
2007-03-21 18:19 ` Nurdin Premji [this message]
2007-03-21 19:57 ` 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=4601771A.3020506@redhat.com \
--to=npremji@redhat.com \
--cc=frysk@sourceware.org \
--cc=mcvet@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).