Re: using autoconf to create build scripts for Assembly language programs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jun 7, 2018 at 10:03 PM, Eric Blake <eblake@xxxxxxxxxx> wrote:

> On 06/07/2018 11:23 AM, mallapadi niranjan wrote:
>
>> Thanks for the reply, that did help  a bit but  was not able to remove the
>>>
>> -c option
>>
>> I passed./configure CCAS=/usr/bin/as CFLAGS=''
>>
>>
>>   [ashok@mydevel foobar]$ make
>> make  all-am
>> make[1]: Entering directory
>> `/home/ashok/practice/ia32/myasm/autotools/foobar'
>> /usr/bin/as --gstabs+  -c -o hello.o hello.s
>>
>
> The automake documentation states that when you use AM_PROG_AS, your
> assembler MUST behave like a C compiler, in that it MUST accept -c and -o.
> If /usr/bin/as does not accept -c, then you'll have to provide a
> shell-script wrapper that adds that functionality on top of /usr/bin/as, at
> least according to the automake documentation.
>
> But again, the autoconf list is not the best list to be asking this;
> you'll (hopefully) get better response on the automake list, since it is an
> automake feature you are trying to use.


I was able to resolve it now using gcc itself instead of /usr/binas to
compile and link the assembler  using below method

Makefile.am

bin_PROGRAMS = hello
hello_SOURCES = hello.s
hello_LDFLAGS=-nostdlib -lgcc -Wl,-e_start




>
>
> --
> Eric Blake, Principal Software Engineer
> Red Hat, Inc.           +1-919-301-3266
> Virtualization:  qemu.org | libvirt.org
>
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
https://lists.gnu.org/mailman/listinfo/autoconf



[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux