all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
To: emacs-devel@gnu.org
Subject: emacs build failure on today's debian
Date: Wed, 15 Jun 2011 17:52:19 +0900	[thread overview]
Message-ID: <buo7h8nzdbw.fsf@dhlpc061.dev.necel.com> (raw)

   $ make
   ...
   make[1]: Entering directory `/usr/local/build/emacs/master/src'
   make[1]: *** No rule to make target `/usr/lib/crt1.o', needed by `temacs'.  Stop.
   make[1]: Leaving directory `/usr/local/build/emacs/master/src'
   make: *** [src] Error 2
   make: Leaving directory `/usr/local/build/emacs/master'

   $ locate crt1 | grep /usr/lib
   /usr/lib/x86_64-linux-gnu/Mcrt1.o
   /usr/lib/x86_64-linux-gnu/Scrt1.o
   /usr/lib/x86_64-linux-gnu/crt1.o
   /usr/lib/x86_64-linux-gnu/gcrt1.o

It seems pretty dodgy that Emacs is directly looking for these files at
all, but oh well, I guess it's some messiness related to dumping.  If it
needs to use them, though, isn't there a less brittle way to find out
where they are?

For instance, this seems to work with gcc (starting with gcc 4.3):

   $ gcc -print-file-name=crt1.o
   /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.6.1/../../../crt1.o

Thanks,

-Miles

-- 
Somebody has to do something, and it's just incredibly pathetic that it
has to be us.  -- Jerry Garcia



             reply	other threads:[~2011-06-15  8:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15  8:52 Miles Bader [this message]
2011-06-15  9:16 ` emacs build failure on today's debian Julien Danjou
2011-06-15  9:38   ` Miles Bader
2011-06-15  9:50     ` Andreas Schwab
2011-06-15 16:09     ` Glenn Morris
2011-06-16  4:14       ` Miles Bader
2011-06-16  6:57         ` Glenn Morris
2011-06-16  7:18           ` Miles Bader
2011-06-16  7:33             ` Glenn Morris
2011-06-15  9:56   ` Bruce Stephens
2011-06-15 10:06     ` Julien Danjou

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=buo7h8nzdbw.fsf@dhlpc061.dev.necel.com \
    --to=miles@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.