[rabbitmq-discuss] rabbitmq-c ./configure

[Alan Antonuk]

Yup, if you're building for arm-linux:

./configure --target=arm-linux

-Alan


On Wed, Jan 15, 2014 at 9:17 AM, Roberto Pagliari <roberto at canary.is> wrote:

> This command:
> ./configure --host=arm-linux
>
> is the one I found here:
> https://groups.google.com/forum/#!topic/rabbitmq-discuss/TJcDUubEBFQ
>
> Are you sure it's the right command you ran? It builds, but for x86.
>
> Thanks,
>
>
>
> On Wed, Jan 15, 2014 at 12:02 PM, Alan Antonuk <alan.antonuk at gmail.com>wrote:
>
>> You're confusing host and target I think.  Host is the system you're
>> building the executable on, target is the system that the executables will
>> be run on.
>>
>> Read up on this here:
>> http://www.sourceware.org/autobook/autobook/autobook_259.html
>>
>> -Alan
>>
>>
>> On Wed, Jan 15, 2014 at 8:23 AM, Roberto Pagliari <roberto at canary.is>wrote:
>>
>>> What I'm doing right now is this:
>>>
>>> ./configure CC=/usr/bin/arm-linux-gnueabi-gcc --host=arm-linux LDFLAGS=path_to_ssl_lib_folder
>>>
>>> but somehow it cannot make the compiler work:
>>>
>>>  configure: WARNING: if you wanted to set the --build type, don't use
>>> --host.
>>> If a cross compiler is detected then cross compile mode will be used
>>> checking for a BSD-compatible install... /usr/bin/install -c
>>> checking whether build environment is sane... yes checking for
>>> arm-linux-strip... no
>>> checking for strip... strip
>>> checking for a thread-safe mkdir -p... /bin/mkdir -p checking for
>>> gawk... gawk
>>> checking whether make sets $(MAKE)... yes
>>> checking whether make supports nested variables... yes
>>> checking for style of include used by make... GNU
>>> checking for arm-linux-gcc... /usr/bin/arm-linux-gnueabi-gcc
>>> checking whether the C compiler works... no
>>> configure: error: in /home/username/rabbitmq-c-master-arm': configure:
>>> error: C compiler cannot create executables
>>> Seeconfig.log' for more details
>>>
>>> but my arm c compiler is working, so I don't know why it does not work
>>> with this.
>>>
>>>
>>> On Wed, Jan 15, 2014 at 10:45 AM, Roberto Pagliari <roberto at canary.is>wrote:
>>>
>>>> Hi,
>>>> I'm getting this warning message when running ./configure
>>>> --host=arm-linux
>>>>
>>>> $ ./configure --host=arm-linux
>>>> configure: WARNING: if you wanted to set the --build type, don't use
>>>> --host.
>>>>     If a cross compiler is detected then cross compile mode will be used
>>>>
>>>> and this message to the end:
>>>> rabbitmq-c build options:
>>>> Host: arm-unknown-linux-gnu
>>>>  Version: 0.4.1
>>>> SSL/TLS: openssl
>>>> Tools: no
>>>> Documentation: no
>>>>  Examples: yes
>>>>
>>>> Any way I can pass the right compiler to ./configure? I tried with
>>>> export CC but it still does not get it.
>>>>
>>>> Thank you,
>>>>
>>>>
>>>>
>>>> On Tue, Jan 14, 2014 at 11:43 PM, Alan Antonuk <alan.antonuk at gmail.com>wrote:
>>>>
>>>>> Yes, those changes were merged in over 2 years ago. The library is not
>>>>> consistently tested on the ARM architecture so I cannot guarantee that it
>>>>> still works, but I also have no reason to believe otherwise.
>>>>>
>>>>> You need to run autoreconf -i before trying to run the configure
>>>>> script.
>>>>>
>>>>> -Alan
>>>>>
>>>>>
>>>>> On Tue, Jan 14, 2014 at 7:04 PM, Roberto Pagliari <roberto at canary.is>wrote:
>>>>>
>>>>>> Hi Alex/All,
>>>>>> in addition to ./configure and Makefile for building with Autotools,
>>>>>> did you manage to fix the issues discussed over here?
>>>>>>
>>>>>> https://groups.google.com/forum/#!topic/rabbitmq-discuss/TJcDUubEBFQ
>>>>>>
>>>>>> I'm asking because ARM is my target architecture.
>>>>>>
>>>>>> Thank you,
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Tue, Jan 14, 2014 at 5:55 PM, Roberto Pagliari <roberto at canary.is>wrote:
>>>>>>
>>>>>>> I cannot find the ./configure file that can be used to build
>>>>>>> rabbimq-c.
>>>>>>>
>>>>>>> https://github.com/alanxz/rabbitmq-c
>>>>>>>
>>>>>>>
>>>>>>> is there a way I can get the file?
>>>>>>>
>>>>>>> Thank you,
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> rabbitmq-discuss mailing list
>>>>>> rabbitmq-discuss at lists.rabbitmq.com
>>>>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> rabbitmq-discuss mailing list
>>>>> rabbitmq-discuss at lists.rabbitmq.com
>>>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>>>>
>>>>>
>>>>
>>>
>>> _______________________________________________
>>> rabbitmq-discuss mailing list
>>> rabbitmq-discuss at lists.rabbitmq.com
>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>>
>>>
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140115/322703c6/attachment.html>