... and closed as a dupe of COUCHDB-1329 :)

B.

On 3 November 2011 12:12, Mike Kimber <[email protected]> wrote:
> Done:
>
> https://issues.apache.org/jira/browse/COUCHDB-1331
>
> Mike
>
>
>
>
>
> -----Original Message-----
> From: Robert Newson [mailto:[email protected]]
> Sent: 02 November 2011 16:22
> To: [email protected]
> Subject: Re: CouchDB 1.1.1 build - couch_js/utf8.h:19:7: error: no newline at 
> end of file
>
> someone file a ticket so I don't forget? will get to this today
>
> On 2 November 2011 16:17, Dave Cottlehuber <[email protected]> wrote:
>> On 2 November 2011 16:29, Robert Newson <[email protected]> wrote:
>>> What platform is this?
>>>
>>> On 2 November 2011 14:17, CGS <[email protected]> wrote:
>>>> No problem.
>>>>
>>>> I hope the developers following this mail list will correct the problem in
>>>> the repository.
>>>>
>>>> Cheers,
>>>> CGS
>>>>
>>>>
>>>>
>>>>
>>>> On 11/02/2011 03:01 PM, Mike Kimber wrote:
>>>>>
>>>>> CGS,
>>>>>
>>>>> That did the trick
>>>>>
>>>>> Thanks
>>>>>
>>>>> Mike
>>>>>
>>>>>
>>>>> -----Original Message-----
>>>>> From: CGS [mailto:[email protected]]
>>>>> Sent: 02 November 2011 13:56
>>>>> To: [email protected]
>>>>> Subject: Re: CouchDB 1.1.1 build - couch_js/utf8.h:19:7: error: no newline
>>>>> at end of file
>>>>>
>>>>> Hi,
>>>>>
>>>>> Just add a new line in
>>>>> /opt/software/apache-couchdb-1.1.1/src/couchdb/priv/couch_js/utf8.h
>>>>> (press ENTER in any editor you may use to open it) and try again.
>>>>>
>>>>> Cheers,
>>>>> CGS
>>>>>
>>>>>
>>>>>
>>>>> On 11/02/2011 02:34 PM, Mike Kimber wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I'm currently trying to build the latest release of CouchDB 1.1.1 which I
>>>>>> downloaded from the Couchdb website. I've built Curl and Erlang to get 
>>>>>> the
>>>>>> correct versions and ./configure has passed and told be me to Relax :).
>>>>>> However when I run Make I get the following error:
>>>>>>
>>>>>> make[4]: Entering directory
>>>>>> `/opt/software/apache-couchdb-1.1.1/src/couchdb/priv'
>>>>>> gcc -DHAVE_CONFIG_H -I. -I../../..   -D_XOPEN_SOURCE  -L/usr/local/lib
>>>>>> -L/opt/local/lib -I/usr/local/lib/erlang/usr/include
>>>>>> -I/usr/lib/erlang/usr/include -I/usr/local/lib/erlang/usr/include
>>>>>> -I/opt/local/lib/erlang/usr/include -I/usr/include -I/usr/include/js
>>>>>> -I/usr/include/mozjs -I/usr/local/include -I/opt/local/include
>>>>>> -I/usr/local/include/js -I/opt/local/include/js -DXP_UNIX   -g -Wall 
>>>>>> -Werror
>>>>>> -D_BSD_SOURCE -I/usr/local/include -g -O2 -MT couchjs-http.o -MD -MP -MF
>>>>>> .deps/couchjs-http.Tpo -c -o couchjs-http.o `test -f 'couch_js/http.c' ||
>>>>>> echo './'`couch_js/http.c
>>>>>> In file included from couch_js/http.c:18:
>>>>>> couch_js/utf8.h:19:7: error: no newline at end of file
>>>>>> make[4]: *** [couchjs-http.o] Error 1
>>>>>> make[4]: Leaving directory
>>>>>> `/opt/software/apache-couchdb-1.1.1/src/couchdb/priv'
>>>>>> make[3]: *** [all-recursive] Error 1
>>>>>> make[3]: Leaving directory
>>>>>> `/opt/software/apache-couchdb-1.1.1/src/couchdb'
>>>>>> make[2]: *** [all-recursive] Error 1
>>>>>> make[2]: Leaving directory `/opt/software/apache-couchdb-1.1.1/src'
>>>>>> make[1]: *** [all-recursive] Error 1
>>>>>> make[1]: Leaving directory `/opt/software/apache-couchdb-1.1.1'
>>>>>> make: *** [all] Error 2
>>>>>>
>>>>>> I've done a Google on this, but and references to this issue seem to be
>>>>>> related to Couchdb 1.0.1 and not 1.1.1 and the fix is a) not clear and a 
>>>>>> b)
>>>>>> seems
>>>>>>
>>>>>> Anyone any ideas?
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Mike
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>
>>
>> It seems it is required by the standard:
>> http://c0x.coding-guidelines.com/5.1.1.2.html vis
>> "123 A source file that is not empty shall end in a new-line
>> character, which shall not be immediately preceded by a backslash
>> character before any such splicing takes place. "
>>
>> No doubt there are reasons related to the dawn of time, such as
>> bootstrap loaders using paper tape that use this to represent the
>> sellotape joins for longer programs.
>>
>> A+
>> Dave
>>
>

Reply via email to