From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>,
Theodore Tso <tytso@mit.edu>
Subject: commit a4b69b7f1809898c87bdc11502ca258a8f16a220 breaks parallel builds
Date: Wed, 07 May 2008 21:58:03 -0500 [thread overview]
Message-ID: <48226C3B.5060007@redhat.com> (raw)
CC unpack.c
CC unparse.c
CC uuid_time.c
GEN_LIB libuuid.a
GEN_LIB ../../lib/libuuid.a
/bin/ln: creating hard link `../../../lib/libuuid.a' to
`../../lib/libuuid.a': No such file or directory
make[2]: *** [../../lib/libuuid.a] Error 1
make[2]: Leaving directory `/tmp/e2fsprogs-1.41/lib/uuid'
make[1]: *** [all-libs-recursive] Error 1
make[1]: Leaving directory `/tmp/e2fsprogs-1.41'
make: *** [all] Error 2
I tried looking into this, but I'm at a bit of a loss as to what the
change was trying to do, so not sure how to fix it... but from
e2fsprogs/lib/uuid/ it would appear that the addition of
$(LIB)/$(LIBRARY).a here has got us backing up one ".." too far :)
$(LIB)/$(LIBRARY).a $(LIBRARY).a: $(OBJS)
@echo " GEN_LIB $@"
@(if test -r $@; then $(RM) -f $@.bak && $(MV) $@ $@.bak; fi)
@$(ARGEN) $@ $(OBJS)
-@$(RANLIB) $@
@$(RM) -f ../$@
@$(LN) $@ ../$@
-Eric
next reply other threads:[~2008-05-08 2:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 2:58 Eric Sandeen [this message]
2008-05-12 0:38 ` commit a4b69b7f1809898c87bdc11502ca258a8f16a220 breaks parallel builds Theodore Tso
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=48226C3B.5060007@redhat.com \
--to=sandeen@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.