Of course... couldn't expect them to fix it if they didn't know about it...
https://issues.asterisk.org/view.php?id=16266
On 12/16/2009 02:19 AM, Julian Lyndon-Smith wrote:
> That's a bummer. Is there a bug number in mantis I can look at ?
>
> Julian
>
> 2009/12/16 Philip A. Prindeville :
>
On 12/16/2009 08:23 AM, Michael Keuter wrote:
>> Hello Lonnie,
>>
>> We have checked 0.7 images and found that a new
>> build was created (3548). Unfortunately there is
>> no "img" file there and maybe it was missed when
>> the upload was performed.
>> Could you check it?
>>
>> Best regards,
>> Ioa
>Hello Lonnie,
>
>We have checked 0.7 images and found that a new
>build was created (3548). Unfortunately there is
>no "img" file there and maybe it was missed when
>the upload was performed.
>Could you check it?
>
>Best regards,
>Ioan.
You could use that older image and then upgrade
via WebG
Hello Lonnie,
We have checked 0.7 images and found that a new build was created
(3548). Unfortunately there is no "img" file there and maybe it was
missed when the upload was performed.
Could you check it?
Best regards,
Ioan.
On 08-Dec-09 11:14 PM, Lonnie Abelbeck wrote:
Ioan,
The R6040 eth
Thanks. Seems to be working now.
Julian
2009/12/15 Michael Keuter :
>>Hmm, enabled the option.
>>
>>Now, I get
>>
>>checking for gcc...
>>/usr/src/astlinux/trunk/build_i586/staging_dir/bin/i586-linux-uclibc-gcc
>>checking for C compiler default output file name... a.out
>>checking whether the C c
That's a bummer. Is there a bug number in mantis I can look at ?
Julian
2009/12/16 Philip A. Prindeville :
> Well, you can definitely try... but it won't build.
>
> We support building it. But there are known issues with cross-compilation
> that have been reported to Digium that they haven't fe
