Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Peter Seebach <peter.seebach@windriver.com>
To: "openembedded-core@"
	<lists.openembedded.org.openembedded-core@lists.openembedded.org>
Subject: site/mips64-common (not a review-ready patch)
Date: Thu, 11 Oct 2012 18:34:42 -0500	[thread overview]
Message-ID: <20121011183442.0a79735e@e6410-2> (raw)

So, turns out that siteinfo.bbclass is looking for mips64-common, but
there isn't one. The way this bit me was screen failing to compile
because stuff like screen_cv_sys_fifo_usable wasn't defined. So I've
drafted up and lightly tested a version of this... but it's been tested
against a several month old oe-core, and the only stuff I have to test
it again isn't going to work with modern oe-core until I do some
catching up and synchronizing.

So I'm sending the data (it's not large) in case anyone needs it and
has better resources for testing it. Only a couple of differences from
mips-common; long and ssize_t are 8 bytes in mips64 land, at least
with our compiler.

# general
ac_cv_va_val_copy=${ac_cv_va_val_copy=yes}

# cvs
cvs_cv_func_printf_ptr=${cvs_cv_func_printf_ptr=yes}

# screen
screen_cv_sys_bcopy_overlap=${screen_cv_sys_bcopy_overlap=no}
screen_cv_sys_memcpy_overlap=${screen_cv_sys_memcpy_overlap=no}
screen_cv_sys_memmove_overlap=${screen_cv_sys_memmove_overlap=no}
screen_cv_sys_fifo_broken_impl=${screen_cv_sys_fifo_broken_impl=yes}
screen_cv_sys_fifo_usable=${screen_cv_sys_fifo_usable=yes}
screen_cv_sys_select_broken_retval=${screen_cv_sys_select_broken_retval=no}
screen_cv_sys_sockets_nofs=${screen_cv_sys_sockets_nofs=no}
screen_cv_sys_sockets_usable=${screen_cv_sys_sockets_usable=yes}
screen_cv_sys_terminfo_used=${screen_cv_sys_terminfo_used=yes}

# ORBit2
ac_cv_alignof_CORBA_octet=1
ac_cv_alignof_CORBA_boolean=1
ac_cv_alignof_CORBA_char=1
ac_cv_alignof_CORBA_wchar=2
ac_cv_alignof_CORBA_short=2
ac_cv_alignof_CORBA_long=8
ac_cv_alignof_CORBA_long_long=8
ac_cv_alignof_CORBA_float=4
ac_cv_alignof_CORBA_double=8
ac_cv_alignof_CORBA_long_double=8
ac_cv_alignof_CORBA_pointer=8
ac_cv_alignof_CORBA_struct=1

# apache
ac_cv_func_pthread_key_delete=${ac_cv_func_pthread_key_delete=yes}
apr_cv_process_shared_works=${apr_cv_process_shared_works=no}
ac_cv_sizeof_ssize_t=${ac_cv_sizeof_ssize_t=8}
apr_cv_tcp_nodelay_with_cork=${apr_cv_tcp_nodelay_with_cork=yes}

# glib
glib_cv_va_val_copy=${glib_cv_va_val_copy=yes}
ac_cv_alignof_guint32=4
ac_cv_alignof_guint64=8
ac_cv_alignof_unsigned_long=8


# slrn
slrn_cv_va_val_copy=${slrn_cv_va_val_copy=yes}


-- 
Listen, get this.  Nobody with a good compiler needs to be justified.



                 reply	other threads:[~2012-10-11 23:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20121011183442.0a79735e@e6410-2 \
    --to=peter.seebach@windriver.com \
    --cc=lists.openembedded.org.openembedded-core@lists.openembedded.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox