public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Cross compiling crda and SSL word size
Date: Thu, 16 Jul 2009 15:25:41 -0400	[thread overview]
Message-ID: <9e4733910907161225m7322b5dcidf9271cb45c07657@mail.gmail.com> (raw)
In-Reply-To: <1247772250.30529.42.camel@johannes.local>

On Thu, Jul 16, 2009 at 3:24 PM, Johannes Berg<johannes@sipsolutions.net> wrote:
> On Thu, 2009-07-16 at 21:09 +0200, Johannes Berg wrote:
>> On Thu, 2009-07-16 at 15:04 -0400, Jon Smirl wrote:
>> > When cross compiling crda the Makefile asks the python system what the
>> > word size is. This gets the word size from the host. Is there a way to
>> > ask the word size using gcc? In my environment the Makefile is
>> > automatically using the correct gcc cross compiler.
>>
>> Can you just use gnutls instead? it has no such issue :)
>>
>> Otherwise you can probably parse it out of "gcc -dumpspecs", but that
>> format doesn't look too nice, especially with multilib gcc...
>
> C99 says this works, I think:
>
> echo -e '#include <limits.h>\n#if ULONG_MAX == 4294967295\n32\n#elif ULONG_MAX == 18446744073709551615U\n64\n#else\n0\n#endif' | gcc -E - | sed 's/^\(#.*\|\)$//;T;d'

The problem test is in key2pub.py

def print_ssl(output, name, val):
    import struct
    if len(struct.pack('@L', 0)) == 8:
        return print_ssl_64(output, name, val)
    else:
        return print_ssl_32(output, name, val)


>
> johannes
>



-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2009-07-16 19:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-16 19:04 Cross compiling crda and SSL word size Jon Smirl
2009-07-16 19:09 ` Johannes Berg
2009-07-16 19:24   ` Johannes Berg
2009-07-16 19:25     ` Jon Smirl [this message]
2009-07-16 19:27       ` Johannes Berg

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=9e4733910907161225m7322b5dcidf9271cb45c07657@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.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