mclinker doesn't build on ubuntu

[Daniel Wilkerson]

If this bug report were not critical, I would not also make it an email to the group.  However I think the fact that the source does not even build on a very recent Ubunutu is something you might want to fix right away.

Details: http://code.google.com/p/mclinker/issues/detail?id=172

Daniel

[Pete Chou]

Hello Daniel,

Thanks for reporting this issue! From what I know, there seems no libtool installed in your system? Do you still see this issue in ToT after installing libtool?

Thanks,

Pete

--
You received this message because you are subscribed to the Google Groups "MCLinker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mclinker+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Daniel Wilkerson]

Thanks for fixing that bug.

Now that you added the halt with error into autogen.sh, it stops and
tells me that I need libtoolize. You might want to point out that
libtoolize can be obtained by installing apt package libtool.

After installing libtool, the build and install process seems to
proceed to completion now. Some further points you might want to fix:

(1) autogen.sh still produces quite a few warnings; please find them
attached. If these are real, make them errors; otherwise, perhaps
just turn them off; note that I picked the most boring configuration I
could; I just followed the instructions in the README.

(2) README says:

"7. ${MCLINKER_INSTALL}/ld.mcld is the linker binary."

but I find it in the bin subdirectory.

Daniel

On Fri, Jul 11, 2014 at 8:34 PM, zonr <zonr...@gmail.com> wrote:
> Just uploaded the patches:
>
> d6808c3d0919 Exit immediately when one of the commands in autogen.sh fails.
> 011e7c37fa69 Check `ranlib' tool.
>
> Checkout to see if these help :)
>
>
>
> On Sat, Jul 12, 2014 at 11:12 AM, zonr <zonr...@gmail.com> wrote:
>>
>> Dear,
>>
>>
>>
>> There're some interesting things in your attached log :)
>>
>> First (the first line in your log):
>>
>>> ./autogen.sh: 18: ./autogen.sh: libtoolize: not found
>>
>>
>> It seems that `libtool' is not install on your system. Try `apt-get
>> install libtool' see whether the problem resolved. And yes, it's our fault
>> that `autogen.sh' doesn't stop when errors occurred.
>>
>> Second:
>>
>>> optimized/Makefile.am:313: error: library used but 'RANLIB' is undefined
>>> optimized/Makefile.am:313: The usual way to define 'RANLIB' is to add
>>> 'AC_PROG_RANLIB'
>>> optimized/Makefile.am:313: to 'configure.ac' and run 'autoconf' again.
>>
>>
>> I just uploaded a patch to fix it. Thanks for your finding :)
>>
>>
>> Sincerely,
>> Zonr
>> Jul. 12, 2014
>>
>>
>>
>>
>> On Sat, Jul 12, 2014 at 4:17 AM, Daniel Wilkerson
>> <daniel.w...@gmail.com> wrote:
>>>
>>> From the current tree:
>>> ~/mclinker-212505$ ls include
>>> Makefile.am mcld
>>>
>>> Getting a fresh copy.
>>>
>>> ~$ mkdir mclinker_tmp
>>> ~$ cd mclinker_tmp/
>>> ~/mclinker_tmp$ git clone https://code.google.com/p/mclinker/Cloning
>>> into 'mclinker'...
>>> remote: Counting objects: 41078, done.
>>> Receiving objects: 100% (41078/41078), 91.76 MiB | 3.52 MiB/s, done.
>>> Resolving deltas: 100% (28121/28121), done.
>>> Checking connectivity... done.
>>> ~/mclinker_tmp$ ls
>>> mclinker
>>> ~/mclinker_tmp$ cd mclinker/
>>> ~/mclinker_tmp/mclinker$ nohup ./autogen.sh
>>> nohup: ignoring input and appending output to ‘nohup.out’
>>> ~/mclinker_tmp/mclinker$ mv nohup.out autogen_nohup.out
>>>
>>> Please find attached the autogen_nohup.out.
>>>
>>> ~/mclinker_tmp/mclinker$ ls include/
>>> Makefile.am mcld
>>> ~/mclinker_tmp/mclinker$
>>>
>>> As you can see, no Makefile.in.
>>>
>>> Running autogen again:
>>>
>>> ~/mclinker_tmp/mclinker$ ./autogen.sh; echo $?
>>> . . .
>>> 0
>>>
>>> That is, autogen does not halt with an error. If autogen is failing,
>>> it would help if it would halt with a helpful message at the first
>>> error.
>>>
>>> Also, I tried your latest release: mclinker-Andes.zip
>>> which when unzipped produced a mclinker-ba49115d0aa2
>>> which contains an autogen.sh which is not executable:
>>>
>>> ~/mclinker-ba49115d0aa2$ ls -l autogen.sh
>>> -rw-rw-r-- 1 dsw dsw 381 Dec 31 1979 autogen.sh
>>>
>>> and in fact contains no executables files at all:
>>>
>>> ~/mclinker-ba49115d0aa2$ find . -executable -type f
>>> ~/mclinker-ba49115d0aa2$
>>>
>>> Daniel
>>>
>>> On Fri, Jul 11, 2014 at 12:47 PM, zonr <zonr...@gmail.com> wrote:
>>> > I cannot reproduce the bug reported in the link. From the output, it
>>> > seems
>>> > that `include/Makefile.in' is missing. But it should be there after
>>> > running
>>> > `autogen.sh' (more specifically, the command `automake' in `autogen.sh'
>>> > will
>>> > generate it). Could you help me verify that? I.e., reset to the clean
>>> > tree
>>> > (you shouldn't see `include/Makefile.in' at the time) and then execute
>>> > autogen.sh to see whether include/Makefile.in is generated.
>>> >
>>> > Zonr

>>> >
>>> >
>>> >
>>> > On Sat, Jul 12, 2014 at 2:06 AM, Daniel Wilkerson
>>> > <daniel.w...@gmail.com> wrote:
>>> >>

[Pete Chou]

The subdir-objects warning in automake should be suppressed in ToT now.

https://code.google.com/p/mclinker/issues/detail?id=173

Thanks,

Pete