> From: Norberto Lopes <nlopes...@gmail.com>
> Subject: [Etoile-dev] Slackware 13 issues
> To: etoile-dev@gna.org
> Message-ID:
>        <8c4ce4111002120531y4a7e71c3m937395b45ca9e...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi all.
> I tried to get Etoile from trunk up and running in my slackware 13.
> I had only 1 issue with the etoile.make.
>
> Attached is the svn diff to patch it to make it compile successfully.
> Let me know if I missed something here as this looks kinda hacky.
>
> Cheers,
>    Norberto
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: etoile.make.diff
> Type: application/octet-stream
> Size: 3027 bytes
> Desc: not available
> Url : /public/etoile-dev/attachments/20100212/8ff59042/attachment.obj
>
> From: Quentin Math? <qma...@gmail.com>
> Subject: Re: [Etoile-dev] Slackware 13 issues
> To: Developers list for ??toil?? desktop environment
>        <etoile-dev@gna.org>
> Message-ID: <9c027b27-16d9-4333-b95c-4caff29bd...@gmail.com>
> Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes
>
> Hi Noberto,
>
> Le 12 f?vr. 2010 ? 14:31, Norberto Lopes a ?crit :
>
>> Hi all.
>> I tried to get Etoile from trunk up and running in my slackware 13.
>> I had only 1 issue with the etoile.make.
>>
>> Attached is the svn diff to patch it to make it compile successfully.
>> Let me know if I missed something here as this looks kinda hacky.
>
>
> I cannot commit the patch as is, since it's going to break etoile.make
> on Solaris.
> The backquotes around the comments were the only trick that seemed to
> work everywhere until now :-/
>
Yeah, I had a pretty good idea it would be something like this.
As for the patch, I'm ok not having the patch committed to the tree as
it is a fairly simple one.

Maybe it'll help others compile in Slackware if they have the same issues.

>  From etoile.make:
>> # WARNING: Don't use sh comments without backquoting them in command
>> scripts,
>> # otherwise the next lines will be interpreted as belonging to the
>> comment on
>> # some platform such as Solaris. sh concatenates all the lines with
>> a trailing
>> # '\' without inserting any a line break. However some sh versions
>> (FreeBSD,
>> # GNU) will consider each comment line to be implicitly ended by a
>> line break.
>
> I think I'm going to remove the comments and refactor each code piece
> into a standalone rule or define. It's probably not a bad thing since
> backquoting comments as I do is a ugly hack.
>
That seems nice to have :)

> Cheers,
> Quentin.

Thanks,
    Norberto

_______________________________________________
Etoile-dev mailing list
Etoile-dev@gna.org
https://mail.gna.org/listinfo/etoile-dev

Reply via email to