From: Ric White <richard.white@hp.com>
To: "openhpi-devel@lists.sourceforge.net"
<openhpi-devel@lists.sourceforge.net>,
Garrett Cooper <yanegomi@gmail.com>
Cc: LTP list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [Openhpi-devel] [PATCH] Cross-compile configure bug
Date: Mon, 24 Aug 2009 19:15:18 -0600 [thread overview]
Message-ID: <1251162918.4388.33.camel@OSLORic> (raw)
In-Reply-To: <364299f40908191611x4accc24yc36b344956c7a40c@mail.gmail.com>
Hi Garrett,
I was wondering about your addition of the cross_compiling test. If
there is OpenHPI code that may behave badly on a system where an int
isn't 4 bytes, I'm thinking that a warning should be issued even for a
cross compile to such an architecture as well. Like:
if test "x$OH_SIZEOF_INT" != "x4"; then
AC_MSG_WARN([
*** int is not 4 bytes, it is $OH_SIZEOF_INT bytes on this platform
*** undefined behavior may result from this.
])
fi
Will having a warning instead of an error cause problems for LTP when
cross compiling?
Does anyone else in the OpenHPI community oppose changing this error to
a warning?
Best Regards,
Ric White
On Wed, 2009-08-19 at 23:11 +0000, Garrett Cooper wrote:
> Hi,
> Found this bug while trying to cross-compile with the
> openhpi-test-suite in LTP, and made the ERROR into WARN. Please fix
> this item as per the attached patch.
> Thanks,
> -Garrett
>
> PS Please CC my address in all correspondence w.r.t. this email thread.
>
> Summary:
>
> 1. int != 4 shouldn't be checked for while cross-compiling.
> 2. Warn instead of erroring out, because we have a _lot_ of 64-bit
> platforms that we test on which will be negatively impacted by this
> check.
>
> Signed-off-by: Garrett Cooper <yanegomi@gmail.com>
>
> --- /nfs.mac/ltp-upgrade/contrib/ltp/src/testcases/open_hpi_testsuite//configure.ac.orig 2009-08-19
> 16:04:08.000000000 -0700
> +++ /nfs.mac/ltp-upgrade/contrib/ltp/src/testcases/open_hpi_testsuite//configure.ac 2009-08-19
> 16:10:47.000000000 -0700
> @@ -44,14 +44,13 @@
> AC_PROG_LN_S
> AC_PROG_MAKE_SET
>
> -dnl die on int != 32bits. This is too instrumental to our code right now.
> +dnl Warn when int != 32bits. This is too instrumental to our code right now.
> dnl AC_MSG_CHECKING(int is 4 bytes)
> OH_SET_SIZES
> -if test "x$OH_SIZEOF_INT" != "x4"; then
> - AC_MSG_ERROR([
> +if test x$cross_compiling != xyes && test "x$OH_SIZEOF_INT" != "x4"; then
> + AC_MSG_WARN([
> *** int is not 4 bytes, it is $OH_SIZEOF_INT bytes on this platform
> -*** undefined behavior will result
> -*** please contact the openhpi development team to fix this
> +*** undefined behavior may result from this.
> ])
> fi
>
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
> trial. Simplify your report design, integration and deployment - and focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now. http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Openhpi-devel mailing list
> Openhpi-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/openhpi-devel
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-08-25 1:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 23:11 [LTP] [PATCH] Cross-compile configure bug Garrett Cooper
2009-08-23 7:28 ` Subrata Modak
2009-08-25 1:15 ` Ric White [this message]
2009-08-25 5:42 ` [LTP] [Openhpi-devel] " anton.pak
2009-08-25 15:12 ` Shuah Khan
2009-08-25 15:19 ` Anton Pak
2009-08-25 17:42 ` Shuah Khan
2009-08-26 0:16 ` Garrett Cooper
2009-08-27 0:51 ` Ric White
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=1251162918.4388.33.camel@OSLORic \
--to=richard.white@hp.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=openhpi-devel@lists.sourceforge.net \
--cc=yanegomi@gmail.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