From: Sven Joachim <svenjoac@gmx.de>
To: Glenn Morris <rgm@gnu.org>
Cc: Dan Nicolaescu <dann@gnu.org>, 5655@debbugs.gnu.org
Subject: bug#5655: incorrect paths for crt1.o, crtn.o, etc.
Date: Tue, 27 Apr 2010 21:27:27 +0200 [thread overview]
Message-ID: <87r5m0elwg.fsf@turtle.gmx.de> (raw)
In-Reply-To: <3wtyqw2433.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 27 Apr 2010 13:33:04 -0400")
On 2010-04-27 19:33 +0200, Glenn Morris wrote:
> The following patch might make things behave like they used to, could
> you try it out? You will need to run autoconf.
Does not seem to work at all.
>
> *** configure.in 2010-04-27 08:09:01 +0000
> --- configure.in 2010-04-27 17:22:23 +0000
> ***************
> *** 761,766 ****
> --- 761,776 ----
> if test "x$RANLIB" = x; then
> AC_PROG_RANLIB
> fi
> +
> + ## Although we're running on an amd64 kernel, we're actually compiling for
> + ## the x86 architecture. The user should probably have provided an
> + ## explicit --build to `configure', but if everything else than the kernel
> + ## is running in i386 mode, we can help them out.
> + if test "$machine" = "amdx86-64"; then
> + AC_CHECK_DECL([i386])
> + test "$ac_cv_have_decl_i386" = "yes" && machine=intel386
> + fi
> +
> AC_PATH_PROG(INSTALL_INFO, install-info)
> AC_PATH_PROG(INSTALL_INFO, install-info,, /usr/sbin)
> AC_PATH_PROG(INSTALL_INFO, install-info,:, /sbin)
Okay, configure picks this up:
checking whether i386 is declared... yes
> *** src/m/amdx86-64.h 2010-04-27 03:14:14 +0000
> --- src/m/amdx86-64.h 2010-04-27 17:27:11 +0000
> ***************
> *** 17,31 ****
> You should have received a copy of the GNU General Public License
> along with GNU Emacs. If not, see <http://www.gnu.org/licenses/>. */
>
> - #ifdef i386
> - /* Although we're running on an amd64 kernel, we're actually compiling for
> - the x86 architecture. The user should probably have provided an
> - explicit --build to `configure', but if everything else than the kernel
> - is running in i386 mode, then the bug is really ours: we should have
> - guessed better. */
> - #include "m/intel386.h"
> - #else
> -
> /* The following line tells the configuration script what sort of
> operating system this machine is likely to run.
> USUAL-OPSYS="linux" */
> --- 17,22 ----
> ***************
> *** 90,96 ****
> #define LIB_STANDARD -lgcc -lc -lgcc $(CRT_DIR)/crtn.o
>
> #endif /* SOLARIS2 */
> - #endif /* !i386 */
>
> /* arch-tag: 8a5e001d-e12e-4692-a3a6-0b15ba271c6e
> (do not change this comment) */
> --- 81,86 ----
This part does not apply cleanly, and after I removed the corresponding lines
manually things broke badly because BITS_PER_LONG got #defined to 64 etc.
Sven
next prev parent reply other threads:[~2010-04-27 19:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 4:30 bug#5655: 23.1; incorrect paths for crt1.o, crtn.o, etc Nathan Phillip Brink
2010-03-01 23:22 ` bug#5655: crt*.o Nathan Phillip Brink
2010-04-24 2:24 ` bug#5655: incorrect paths for crt1.o, crtn.o, etc Glenn Morris
2010-04-24 19:26 ` Dan Nicolaescu
2010-04-24 19:51 ` Glenn Morris
2010-04-25 21:19 ` Dan Nicolaescu
2010-04-26 16:36 ` Glenn Morris
2010-04-26 17:16 ` Andreas Schwab
2010-04-26 17:26 ` Glenn Morris
2010-04-26 17:33 ` Andreas Schwab
2010-04-26 17:33 ` Dan Nicolaescu
2010-04-27 3:18 ` Glenn Morris
2010-04-27 6:31 ` Sven Joachim
2010-04-27 6:51 ` Glenn Morris
2010-04-27 7:04 ` Glenn Morris
2010-04-27 7:11 ` Dan Nicolaescu
2010-04-27 7:49 ` Sven Joachim
2010-04-27 7:25 ` Sven Joachim
2010-04-27 17:33 ` Glenn Morris
2010-04-27 19:27 ` Sven Joachim [this message]
2010-04-27 19:32 ` Glenn Morris
2010-04-27 19:59 ` Sven Joachim
2010-04-27 20:17 ` Glenn Morris
2010-04-28 5:49 ` Sven Joachim
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r5m0elwg.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=5655@debbugs.gnu.org \
--cc=dann@gnu.org \
--cc=rgm@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).