From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Paul Edwards <mutazilah@gmail.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
Ian Lance Taylor <iant@google.com>,
gcc@gcc.gnu.org
Subject: Re: i370 port - constructing compile script
Date: Sat, 14 Nov 2009 10:49:00 -0000 [thread overview]
Message-ID: <20091114104817.GI27368@gmx.de> (raw)
In-Reply-To: <3FAFF5DABCFE4E2481AF2B69337626F4@Paullaptop>
* Paul Edwards wrote on Sat, Nov 14, 2009 at 09:51:39AM CET:
> >Well, the configure process should result in the variable LIBOBJS
> >in the generated libiberty Makefile to be set to list of objects
> >containing implementations of replacement system routines.
> >
> >So if you do not have HAVE_STRCASECMP in config.h, you should
> >have been getting strcasecmp.o in LIBOBJS ...
>
> And indeed, I sort of am.
>
> LIBOBJS includes a strcasecmp.s$U.s
>
> That suffix is certainly strange-looking though. I checked in
> config.log and I can see that it automatically detected that
> my "object code" has a ".s" extension, which is basically
> correct given that I forced the "-S" option.
Why do you pass -S in the compiler script? configure sort of expects
that neither -S nor -c are passed automatically.
> In addition, there's another problem - it has included strncmp
> in the list. I had a look and it appears that it attempts to
> actually run the program to see if strncmp works. That's
> not going to work in a cross-compile environment though.
> So maybe it assumes the worst.
Yes. The macro that does this is libiberty_AC_FUNC_STRNCMP in
libiberty/aclocal.m4. In a cross-compile situation, the macro assumes
that strncmp does not work. It uses the cache variable
ac_cv_func_strncmp_works, which you can set if you need to override the
decision, e.g.:
ac_cv_func_strncmp_works=yes
export ac_cv_func_strncmp_works
../gcc/configure ...
A more permanent solution would be to set this correctly based upon
$host in libiberty/configure.ac and regenerate libiberty/configure with
autoconf.
> And then I changed ac_libobjs to stop putting that $U in there as
> well, and I finally got my strcasecmp.
Why does that $U hurt you? It should get expanded to nothing later on.
(It is a remainder from some ansi2knr scheme.)
> Note that I also seem to be getting strerror. It's on the list
> of "required files", even though it isn't required or wanted.
> configure correctly detected that I already had strerror.
> I manually excluded that from my list of files and now things
> are looking good again - including strcasecmp being
> automatically selected in the build process. :-)
Again, rather than hacking the generated configure script, I think you
should start modifying the input files, configure.ac in this case, for
permanent solutions to your build issues. Even if you're only changing
a few lines, doing it each time you want to build a different GCC
version is an unnecessary burden.
Thanks,
Ralf
next prev parent reply other threads:[~2009-11-14 10:49 UTC|newest]
Thread overview: 114+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 22:33 i370 port Paul Edwards
2009-09-14 15:42 ` Ulrich Weigand
2009-09-15 12:59 ` Paul Edwards
2009-09-15 13:51 ` Ulrich Weigand
2009-09-17 13:00 ` Paul Edwards
2009-09-17 17:55 ` Ulrich Weigand
2009-09-18 0:35 ` Paul Edwards
2009-09-18 12:06 ` Ulrich Weigand
2009-09-18 12:23 ` Paul Edwards
2009-09-18 13:27 ` Ulrich Weigand
2009-09-18 13:42 ` Paul Edwards
2009-09-18 16:08 ` Ulrich Weigand
2009-09-19 12:57 ` Paul Edwards
2009-09-25 10:19 ` Paul Edwards
2009-09-25 15:20 ` Ulrich Weigand
2009-09-30 17:24 ` i370 port - constructing compile script Paul Edwards
2009-09-30 17:36 ` Richard Henderson
2009-09-30 21:40 ` Paul Edwards
[not found] ` <mcrpr98x9w8.fsf@dhcp-172-17-9-151.mtv.corp.google.com>
2009-10-01 0:16 ` Joseph S. Myers
2009-10-01 14:00 ` Paul Edwards
2009-10-02 12:41 ` Paul Edwards
2009-10-02 16:00 ` Ian Lance Taylor
2009-10-02 22:53 ` Paul Edwards
2009-10-04 4:11 ` Ian Lance Taylor
2009-10-04 5:14 ` Paul Edwards
2009-10-04 6:04 ` Ian Lance Taylor
2009-10-04 6:50 ` Paul Edwards
2009-10-04 15:38 ` Ulrich Weigand
2009-10-04 22:51 ` Paul Edwards
2009-10-05 13:15 ` Ulrich Weigand
2009-10-06 9:32 ` Paul Edwards
2009-10-06 13:15 ` Ulrich Weigand
2009-10-06 13:38 ` Paul Edwards
2009-10-06 14:01 ` Ulrich Weigand
2009-10-14 14:33 ` Paul Edwards
2009-10-19 14:19 ` Paul Edwards
2009-10-19 17:37 ` Ulrich Weigand
2009-10-20 14:18 ` Paul Edwards
2009-10-20 15:30 ` Ulrich Weigand
2009-11-12 14:03 ` Paul Edwards
2009-11-12 20:06 ` Ralf Wildenhues
2009-11-12 20:56 ` Paul Edwards
2009-11-13 11:43 ` Paul Edwards
2009-11-13 12:01 ` Ulrich Weigand
2009-11-13 12:18 ` Paul Edwards
2009-11-13 12:57 ` Ulrich Weigand
2009-11-14 8:52 ` Paul Edwards
2009-11-14 10:49 ` Ralf Wildenhues [this message]
2009-11-14 11:28 ` Paul Edwards
2009-11-22 0:51 ` Paolo Bonzini
2009-11-18 10:51 ` Paul Edwards
2009-11-19 14:27 ` Ulrich Weigand
2009-11-21 13:40 ` Paul Edwards
2009-11-23 10:33 ` i370 port - 3.4.6 to 4.4 upgrade attempt Paul Edwards
2009-11-23 10:43 ` Andreas Schwab
2009-11-23 15:43 ` Paolo Bonzini
2009-11-24 14:05 ` Ulrich Weigand
2009-11-24 14:36 ` Paul Edwards
2009-11-28 15:14 ` i370 port - music/sp - possible generic gcc problem Paul Edwards
2009-11-28 16:03 ` Richard Guenther
2009-11-28 16:35 ` Paul Edwards
2009-11-28 17:03 ` Richard Guenther
2009-11-28 23:44 ` Paul Edwards
2010-05-26 14:40 ` i370 port - status Paul Edwards
2021-03-14 5:55 ` negative indexes Paul Edwards
2021-03-14 8:05 ` Richard Biener
2021-03-14 8:12 ` Paul Edwards
2021-03-14 13:37 ` Richard Biener
[not found] ` <755065BE2A0B4B508DD3A262B2A83801@DESKTOP0OKG1VA>
2021-03-15 9:22 ` Richard Biener
2021-03-15 13:55 ` extended segments on 80386 Paul Edwards
2009-12-07 12:05 ` i370 port - 3.4.6 to 4.4 upgrade attempt Paul Edwards
2009-12-08 13:55 ` Ulrich Weigand
2009-11-15 14:22 ` i370 port - finally building Paul Edwards
2009-11-22 0:46 ` i370 port - constructing compile script Paolo Bonzini
2009-11-13 12:08 ` Ulrich Weigand
2009-10-05 13:17 ` Michael Matz
2009-10-05 13:38 ` Paul Edwards
2009-10-05 13:46 ` Michael Matz
2009-10-01 14:28 ` Paul Brook
2009-10-01 16:00 ` Paul Edwards
2009-10-01 18:36 ` Ian Lance Taylor
2009-10-01 23:43 ` Paul Edwards
2009-10-01 21:10 ` David Edelsohn
2009-10-01 22:22 ` Toon Moene
2009-10-02 0:19 ` Paul Edwards
2009-11-04 5:21 ` i370 port Paul Edwards
2009-11-04 16:47 ` Ulrich Weigand
2009-11-09 14:55 ` Paul Edwards
2009-11-09 15:57 ` Ian Lance Taylor
2009-11-09 23:10 ` Paul Edwards
2009-11-10 14:58 ` Paul Edwards
2009-11-10 15:36 ` Ian Lance Taylor
2009-11-10 15:51 ` Paul Edwards
2009-11-10 15:56 ` Ian Lance Taylor
2009-12-02 22:03 ` Paul Edwards
2011-08-13 8:34 ` Paul Edwards
2011-08-15 14:32 ` Ulrich Weigand
2011-08-15 15:26 ` Paul Edwards
2011-08-15 17:23 ` Ulrich Weigand
2011-08-16 11:20 ` Paul Edwards
2011-08-16 13:26 ` Ulrich Weigand
2011-08-18 12:15 ` Paul Edwards
2011-08-18 13:14 ` Ulrich Weigand
2011-08-18 14:18 ` Paul Edwards
[not found] <OF0A51B575.29A29744-ON42257656.0067E35B-42257656.00682411@de.ibm.com>
2009-10-22 9:06 ` i370 port - constructing compile script Paul Edwards
2009-10-22 19:26 ` Ulrich Weigand
2009-10-22 22:04 ` Paul Edwards
2009-10-23 14:36 ` Paul Edwards
2009-10-23 14:58 ` Ian Lance Taylor
2009-10-23 15:16 ` Ulrich Weigand
2009-10-24 0:20 ` Paul Edwards
2009-10-24 4:11 ` Ulrich Weigand
2009-10-27 12:18 ` Paul Edwards
2009-11-02 14:45 Paul Edwards
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=20091114104817.GI27368@gmx.de \
--to=ralf.wildenhues@gmx.de \
--cc=gcc@gcc.gnu.org \
--cc=iant@google.com \
--cc=mutazilah@gmail.com \
--cc=uweigand@de.ibm.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).