headers
Anders Nygren | 3 Aug 2012 19:56
Picon

Building on raspberry pi

Hi
I am trying to build yaws from github on a Raspberry Pi, which uses an
ARM11 CPU.
Debian linux, Erlang R15B01

> uname -m
armv61

The problem building is that CFLAGS includes -m32 which apparently is
not supported on the ARM version of gcc.
Removing -m32 from CFLAGS in include.mk solves the problem.
I am not able to figure out how to change the configure script to do
this automatically.

/Anders

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Permalink | Reply | 3 comments |
headers
L. S. | 4 Aug 2012 20:45
Picon

Yaws OS X Startup File Issue

There has been an issue with the Yaws OSX startup script (/Library/StartupItems/Yaws/Yaws) where it
doesn't work as installed unless the line
    yawsid_opts=--id myserverid
is corrected to read
    yawsid_opts='--id myserverid'

It's something I've noticed for some time, but it seems to remain unfixed through each release.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Permalink | Reply | 1 comment |
headers
Steve Vinoski | 6 Aug 2012 04:38
Picon
Gravatar

Re: Yaws OS X Startup File Issue

On Sat, Aug 4, 2012 at 2:45 PM, L. S. <lsearchw@...> wrote:
> There has been an issue with the Yaws OSX startup script (/Library/StartupItems/Yaws/Yaws) where it
doesn't work as installed unless the line
>     yawsid_opts=--id myserverid
> is corrected to read
>     yawsid_opts='--id myserverid'
>
> It's something I've noticed for some time, but it seems to remain unfixed through each release.

Fixed, thanks.

--steve

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Permalink | Reply | 0 comments |
headers
Steve Vinoski | 7 Aug 2012 19:06
Picon
Gravatar

Re: Building on raspberry pi

On Fri, Aug 3, 2012 at 1:56 PM, Anders Nygren
<anders.nygren@...> wrote:
> Hi
> I am trying to build yaws from github on a Raspberry Pi, which uses an
> ARM11 CPU.
> Debian linux, Erlang R15B01
>
>> uname -m
> armv61
>
> The problem building is that CFLAGS includes -m32 which apparently is
> not supported on the ARM version of gcc.
> Removing -m32 from CFLAGS in include.mk solves the problem.
> I am not able to figure out how to change the configure script to do
> this automatically.

Hi Anders, what is $host_cpu set to for ARM11? I assume you'll want to
add a new case for its value around line 239 of configure.in.

--steve

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Permalink | Reply | 2 comments |
headers
Steve Vinoski | 7 Aug 2012 19:44
Picon
Gravatar

Re: test organisation

Sorry for the delayed reply, been on vacation.

On Mon, Jul 30, 2012 at 12:24 PM, JD Bothma <jbothma@...> wrote:
> Hi
>
> How do you decide which tests go into which test directory (t1-7)? Is
> it just grouping tests with similar dependencies?

Yeah, pretty much.

> Is this and some basic introduction to writing tests for yaws written
> down somewhere or shall I add something to the test README when I know
> better? :)

I don't think there's anything written down. If you want to write
something, that would be great.

> Why aren't you using something like common test for setup and stuff? I
> can't immediately see when ct came about but I'm guessing yaws
> predates it :)

I don't know when ct came about either, but I was unaware of it when I
started adding to and enhancing the yaws tests a few years ago. It's
basically grown organically since then, I guess. But you're right, I
think ct could be an improvement.

--steve

------------------------------------------------------------------------------
Live Security Virtual Conference
(Continue reading)

Permalink | Reply | 0 comments |
headers
Anders Nygren | 7 Aug 2012 20:24
Picon

Re: Building on raspberry pi

On Tue, Aug 7, 2012 at 12:06 PM, Steve Vinoski <vinoski@...> wrote:
> On Fri, Aug 3, 2012 at 1:56 PM, Anders Nygren
<anders.nygren@...> wrote:
>> Hi
>> I am trying to build yaws from github on a Raspberry Pi, which uses an
>> ARM11 CPU.
>> Debian linux, Erlang R15B01
>>
>>> uname -m
>> armv61
>>
>> The problem building is that CFLAGS includes -m32 which apparently is
>> not supported on the ARM version of gcc.
>> Removing -m32 from CFLAGS in include.mk solves the problem.
>> I am not able to figure out how to change the configure script to do
>> this automatically.
>
> Hi Anders, what is $host_cpu set to for ARM11? I assume you'll want to
> add a new case for its value around line 239 of configure.in.
>
> --steve

Hi Steve
$host_cpu is armv6l, (with lowercase L), and not armv61 (with one) as
I originally wrote.
That was the reason I couldn't get it to work.
This fixes the problem with building.

anders <at> raspberrypi ~/src/test/yaws $ git diff
diff --git a/configure.in b/configure.in
(Continue reading)

Permalink | Reply | 1 comment |
headers
Steve Vinoski | 7 Aug 2012 21:55
Picon
Gravatar

Re: Building on raspberry pi

On Tue, Aug 7, 2012 at 2:24 PM, Anders Nygren
<anders.nygren@...> wrote:
> On Tue, Aug 7, 2012 at 12:06 PM, Steve Vinoski <vinoski@...> wrote:
>> On Fri, Aug 3, 2012 at 1:56 PM, Anders Nygren
<anders.nygren@...> wrote:
>>> Hi
>>> I am trying to build yaws from github on a Raspberry Pi, which uses an
>>> ARM11 CPU.
>>> Debian linux, Erlang R15B01
>>>
>>>> uname -m
>>> armv61
>>>
>>> The problem building is that CFLAGS includes -m32 which apparently is
>>> not supported on the ARM version of gcc.
>>> Removing -m32 from CFLAGS in include.mk solves the problem.
>>> I am not able to figure out how to change the configure script to do
>>> this automatically.
>>
>> Hi Anders, what is $host_cpu set to for ARM11? I assume you'll want to
>> add a new case for its value around line 239 of configure.in.
>>
>> --steve
>
> Hi Steve
> $host_cpu is armv6l, (with lowercase L), and not armv61 (with one) as
> I originally wrote.
> That was the reason I couldn't get it to work.
> This fixes the problem with building.
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Martin Dimitrov | 8 Aug 2012 12:53
Picon

Bad value on output port 'efile'

Hello,

I receive this error right after the return of my 'out' function in yaws
page. The request is POST coming from Google spreadsheet.

I know this is quite vague but I really can't find any peculiarities.
Which module is calling the 'out' functions?

Thanks in advance,

Martin

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Permalink | Reply | 7 comments |
headers
Steve Vinoski | 8 Aug 2012 14:44
Picon
Gravatar

Re: Bad value on output port 'efile'

On Wed, Aug 8, 2012 at 6:53 AM, Martin Dimitrov
<mrtndimitrov@...> wrote:
> Hello,
>
> I receive this error right after the return of my 'out' function in yaws
> page. The request is POST coming from Google spreadsheet.
>
> I know this is quite vague but I really can't find any peculiarities.
> Which module is calling the 'out' functions?

The yaws_server module calls the out/1 functions, specifically lines
2271 and 2721.

Your error message is coming from the Erlang VM, not from Yaws itself.
Maybe you have an unexpected term within an iolist somewhere?

--steve

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Permalink | Reply | 6 comments |
headers
Martin Dimitrov | 9 Aug 2012 09:00
Picon

Re: Bad value on output port 'efile'

Hi Steve,

Thanks for the hint.

Things got even stranger. I put some debug messages in
yaws_server:'POST'/3 around yaws_server:body_method/3. My out/1 function
is called without causing any errors. Its return is as simple as {html,
"OK"}. Then after yaws_server:'POST'/3 is done executing, the error
message appears. Which function is calling yaws_server:'POST'/3? Can it
be the HTTP headers Google sends that cause trouble?

Best regards,

Martin

On 8/8/2012 3:44 PM, Steve Vinoski wrote:
> On Wed, Aug 8, 2012 at 6:53 AM, Martin Dimitrov
<mrtndimitrov@...> wrote:
>> Hello,
>>
>> I receive this error right after the return of my 'out' function in yaws
>> page. The request is POST coming from Google spreadsheet.
>>
>> I know this is quite vague but I really can't find any peculiarities.
>> Which module is calling the 'out' functions?
> The yaws_server module calls the out/1 functions, specifically lines
> 2271 and 2721.
>
> Your error message is coming from the Erlang VM, not from Yaws itself.
> Maybe you have an unexpected term within an iolist somewhere?
(Continue reading)

Permalink | Reply | 5 comments |

Gmane