error on building the windows installer

error on building the windows installer

[Cesar Romani]

I was building the windows installer from the latest update from the git
repository.
On using make-windows-installer.bat I got an error on the line:
cabal-dev install --flags="executable -library blaze_html_0_5" --datasubdir=

the error is:
--------------------
[...]
Linking dist\build\pandoc\pandoc.exe ...
Preprocessing executable 'make-pandoc-man-pages' for pandoc-1.10...
<command line>: cannot satisfy -package-id pandoc-1.10-inplace
     (use -v for more information)
cabal.exe: Error: some packages failed to install:
pandoc-1.10 failed during the building phase. The exception was:
ExitFailure 1
--------------------

Many thanks in advance,

-- 
Cesar

Re: error on building the windows installer

[John MacFarlane]

Because pandoc-types 1.10 isn't released yet, the windows installer
script won't work without modifications.  It might be sufficient to
add cabal-dev add-source DIR, where DIR is the directory containing
the up-to-date code for pandoc-types.

+++ Cesar Romani [Nov 04 12 18:43 ]:
> I was building the windows installer from the latest update from the git
> repository.
> On using make-windows-installer.bat I got an error on the line:
> cabal-dev install --flags="executable -library blaze_html_0_5" --datasubdir=
> 
> the error is:
> --------------------
> [...]
> Linking dist\build\pandoc\pandoc.exe ...
> Preprocessing executable 'make-pandoc-man-pages' for pandoc-1.10...
> <command line>: cannot satisfy -package-id pandoc-1.10-inplace
>     (use -v for more information)
> cabal.exe: Error: some packages failed to install:
> pandoc-1.10 failed during the building phase. The exception was:
> ExitFailure 1
> --------------------
> 
> Many thanks in advance,
> 
> -- 
> Cesar
> 
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 

Re: error on building the windows installer

[Cesar Romani]

On 04/11/2012 09:30 p.m., John MacFarlane wrote:
 > Because pandoc-types 1.10 isn't released yet, the windows installer
 > script won't work without modifications.  It might be sufficient to
 > add cabal-dev add-source DIR, where DIR is the directory containing
 > the up-to-date code for pandoc-types.

Where should I add that line? I added
'cabal-dev add-source pandoc-types' before the line
cabal-dev install --flags="executable -library blaze_html_0_5" --datasubdir=
on the batch file make-windows-installer.bat, but I'm getting the same
error.

Regards,

-- 
Cesar

Re: error on building the windows installer

[John MacFarlane]

+++ Cesar Romani [Nov 06 12 10:11 ]:
> On 04/11/2012 09:30 p.m., John MacFarlane wrote:
> > Because pandoc-types 1.10 isn't released yet, the windows installer
> > script won't work without modifications.  It might be sufficient to
> > add cabal-dev add-source DIR, where DIR is the directory containing
> > the up-to-date code for pandoc-types.
> 
> Where should I add that line? I added
> 'cabal-dev add-source pandoc-types' before the line
> cabal-dev install --flags="executable -library blaze_html_0_5" --datasubdir=
> on the batch file make-windows-installer.bat, but I'm getting the same
> error.

You'd need it before the line that installs citeproc-hs.

Re: error on building the windows installer

[Cesar Romani]

On 06/11/2012 11:11 a.m., John MacFarlane wrote:
 > +++ Cesar Romani [Nov 06 12 10:11 ]:
 >> On 04/11/2012 09:30 p.m., John MacFarlane wrote:
 >>> Because pandoc-types 1.10 isn't released yet, the windows installer
 >>> script won't work without modifications.  It might be sufficient to
 >>> add cabal-dev add-source DIR, where DIR is the directory containing
 >>> the up-to-date code for pandoc-types.
 >>
 >> Where should I add that line? I added
 >> 'cabal-dev add-source pandoc-types' before the line
 >> cabal-dev install --flags="executable -library blaze_html_0_5" 
--datasubdir=
 >> on the batch file make-windows-installer.bat, but I'm getting the same
 >> error.
 >
 > You'd need it before the line that installs citeproc-hs.

I get the same error.

Regards,

-- 
Cesar

Re: error on building the windows installer

[John MacFarlane]

+++ Cesar Romani [Nov 06 12 21:02 ]:
> On 06/11/2012 11:11 a.m., John MacFarlane wrote:
> > +++ Cesar Romani [Nov 06 12 10:11 ]:
> >> On 04/11/2012 09:30 p.m., John MacFarlane wrote:
> >>> Because pandoc-types 1.10 isn't released yet, the windows installer
> >>> script won't work without modifications.  It might be sufficient to
> >>> add cabal-dev add-source DIR, where DIR is the directory containing
> >>> the up-to-date code for pandoc-types.
> >>
> >> Where should I add that line? I added
> >> 'cabal-dev add-source pandoc-types' before the line
> >> cabal-dev install --flags="executable -library blaze_html_0_5"
> --datasubdir=
> >> on the batch file make-windows-installer.bat, but I'm getting the same
> >> error.
> >
> > You'd need it before the line that installs citeproc-hs.
> 
> I get the same error.

Hm.  You could try inserting this line after the add-source:

cabal-dev install --reinstall --force-reinstalls pandoc-types

Re: error on building the windows installer

[Cesar Romani]

On 07/11/2012 12:10 p.m., John MacFarlane wrote:
 > +++ Cesar Romani [Nov 06 12 21:02 ]:
 >> On 06/11/2012 11:11 a.m., John MacFarlane wrote:
 >>> +++ Cesar Romani [Nov 06 12 10:11 ]:
 >>>> On 04/11/2012 09:30 p.m., John MacFarlane wrote:
 >>>>> Because pandoc-types 1.10 isn't released yet, the windows installer
 >>>>> script won't work without modifications.  It might be sufficient to
 >>>>> add cabal-dev add-source DIR, where DIR is the directory containing
 >>>>> the up-to-date code for pandoc-types.
 >>>>
 >>>> Where should I add that line? I added
 >>>> 'cabal-dev add-source pandoc-types' before the line
 >>>> cabal-dev install --flags="executable -library blaze_html_0_5"
 >> --datasubdir=
 >>>> on the batch file make-windows-installer.bat, but I'm getting the same
 >>>> error.
 >>>
 >>> You'd need it before the line that installs citeproc-hs.
 >>
 >> I get the same error.
 >
 > Hm.  You could try inserting this line after the add-source:
 >
 > cabal-dev install --reinstall --force-reinstalls pandoc-types

If I follow these steps on the batch file:
1. cabal-dev install --disable-library-for-ghci highlighting-kate
2. cabal-dev add-source pandoc-types
3. cabal-dev install --reinstall --force-reinstalls pandoc-types
4. cabal-dev install --flags="embed_data_files" citeproc-hs
5. cabal-dev install --flags="executable -library blaze_html_0_5" 
--datasubdir=
...

I always get the same error on the 5. line:

[...]
Linking dist\build\pandoc\pandoc.exe ...
Preprocessing executable 'make-pandoc-man-pages' for pandoc-1.10...
<command line>: cannot satisfy -package-id pandoc-1.10-inplace
     (use -v for more information)
cabal.exe: Error: some packages failed to install:
pandoc-1.10 failed during the building phase. The exception was:
ExitFailure 1

Regards,

-- 
Cesar

Re: error on building the windows installer

[John MacFarlane]

+++ Cesar Romani [Nov 07 12 14:40 ]:
 
> If I follow these steps on the batch file:
> 1. cabal-dev install --disable-library-for-ghci highlighting-kate
> 2. cabal-dev add-source pandoc-types
> 3. cabal-dev install --reinstall --force-reinstalls pandoc-types
> 4. cabal-dev install --flags="embed_data_files" citeproc-hs
> 5. cabal-dev install --flags="executable -library blaze_html_0_5"
> --datasubdir=
> ...
> 
> I always get the same error on the 5. line:
> 
> [...]
> Linking dist\build\pandoc\pandoc.exe ...
> Preprocessing executable 'make-pandoc-man-pages' for pandoc-1.10...
> <command line>: cannot satisfy -package-id pandoc-1.10-inplace
>     (use -v for more information)
> cabal.exe: Error: some packages failed to install:
> pandoc-1.10 failed during the building phase. The exception was:
> ExitFailure 1

Ah.  I see what is going on.

To build make-pandoc-man-pages, we need the library installed.
But we disabled that with the '-library' flag, in order to make
the executable relocatable.

Well, the man pages aren't really needed for Windows anyway,
so maybe I'll add a cabal flag that turns off 'make-pandoc-man-pages';
I can then use this in the windows package creation script.

Thanks.

Re: error on building the windows installer

[andrea rossato]

John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> +++ Cesar Romani [Nov 07 12 14:40 ]:
>  
>> If I follow these steps on the batch file:
>> 1. cabal-dev install --disable-library-for-ghci highlighting-kate
>> 2. cabal-dev add-source pandoc-types
>> 3. cabal-dev install --reinstall --force-reinstalls pandoc-types
>> 4. cabal-dev install --flags="embed_data_files" citeproc-hs
>> 5. cabal-dev install --flags="executable -library blaze_html_0_5"
>> --datasubdir=
>> ...
>> 
>> I always get the same error on the 5. line:
>> 
>> [...]
>> Linking dist\build\pandoc\pandoc.exe ...
>> Preprocessing executable 'make-pandoc-man-pages' for pandoc-1.10...
>> <command line>: cannot satisfy -package-id pandoc-1.10-inplace
>>     (use -v for more information)
>> cabal.exe: Error: some packages failed to install:
>> pandoc-1.10 failed during the building phase. The exception was:
>> ExitFailure 1
>
> Ah.  I see what is going on.
>
> To build make-pandoc-man-pages, we need the library installed.
> But we disabled that with the '-library' flag, in order to make
> the executable relocatable.
>
> Well, the man pages aren't really needed for Windows anyway,
> so maybe I'll add a cabal flag that turns off 'make-pandoc-man-pages';
> I can then use this in the windows package creation script.
>
> Thanks.

In citeproc-hs there also seems to be a bug which shows up when building
with the "embed_data_files" flags. I'm going to fix it later this
afternoon.

Andrea

Re: error on building the windows installer

[John MacFarlane]

+++ andrea rossato [Nov 08 12 12:39 ]:
> John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> 
> > +++ Cesar Romani [Nov 07 12 14:40 ]:
> >  
> >> If I follow these steps on the batch file:
> >> 1. cabal-dev install --disable-library-for-ghci highlighting-kate
> >> 2. cabal-dev add-source pandoc-types
> >> 3. cabal-dev install --reinstall --force-reinstalls pandoc-types
> >> 4. cabal-dev install --flags="embed_data_files" citeproc-hs
> >> 5. cabal-dev install --flags="executable -library blaze_html_0_5"
> >> --datasubdir=
> >> ...
> >> 
> >> I always get the same error on the 5. line:
> >> 
> >> [...]
> >> Linking dist\build\pandoc\pandoc.exe ...
> >> Preprocessing executable 'make-pandoc-man-pages' for pandoc-1.10...
> >> <command line>: cannot satisfy -package-id pandoc-1.10-inplace
> >>     (use -v for more information)
> >> cabal.exe: Error: some packages failed to install:
> >> pandoc-1.10 failed during the building phase. The exception was:
> >> ExitFailure 1
> >
> > Ah.  I see what is going on.
> >
> > To build make-pandoc-man-pages, we need the library installed.
> > But we disabled that with the '-library' flag, in order to make
> > the executable relocatable.
> >
> > Well, the man pages aren't really needed for Windows anyway,
> > so maybe I'll add a cabal flag that turns off 'make-pandoc-man-pages';
> > I can then use this in the windows package creation script.
> >
> > Thanks.
> 
> In citeproc-hs there also seems to be a bug which shows up when building
> with the "embed_data_files" flags. I'm going to fix it later this
> afternoon.

My present thought is that pandoc's 'library' and 'executable' flags
create too many problems.  I'm thinking of getting rid of them, and
adding an embed_data_files flag to embed the data files into the binary.
(The added size is fairly insignificant since the binary is already so
large.)  This would allow you to make a relocatable executable, not just
on Windows but on any system.  And it would be fully relocatable --
copy the binary anywhere and it will work, without the need of
supporting data files.

This would also solve the problem with man pages noted above, as
we would no longer need the -library flag.

Anyway, I was going to use citeproc-hs as a model, so let me know what
the problem was!

John

Re: error on building the windows installer

[andrea rossato]

John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

>> In citeproc-hs there also seems to be a bug which shows up when building
>> with the "embed_data_files" flags. I'm going to fix it later this
>> afternoon.
>
> My present thought is that pandoc's 'library' and 'executable' flags
> create too many problems.  I'm thinking of getting rid of them, and
> adding an embed_data_files flag to embed the data files into the binary.
> (The added size is fairly insignificant since the binary is already so
> large.)  This would allow you to make a relocatable executable, not just
> on Windows but on any system.  And it would be fully relocatable --
> copy the binary anywhere and it will work, without the need of
> supporting data files.
>
> This would also solve the problem with man pages noted above, as
> we would no longer need the -library flag.
>
> Anyway, I was going to use citeproc-hs as a model, so let me know what
> the problem was!

The problem was just me: I didn't check if the code compiled with the
"embed_data_files" flag before releasing 0.3.6.

The bug was due to the fact that when moving to hexpat I started using
lazy bytestrings for reading files, while embed-file uses strict
bytestrings, hence a type error -- easily fixed.

Andrea

Re: error on building the windows installer

[Cesar Romani]

On 08/11/2012 01:24 p.m., andrea rossato wrote:
 > John MacFarlane<fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 
  writes:
 >
 >>> In citeproc-hs there also seems to be a bug which shows up when 
building
 >>> with the "embed_data_files" flags. I'm going to fix it later this
 >>> afternoon.
 >>
 >> My present thought is that pandoc's 'library' and 'executable' flags
 >> create too many problems.  I'm thinking of getting rid of them, and
 >> adding an embed_data_files flag to embed the data files into the binary.
 >> (The added size is fairly insignificant since the binary is already so
 >> large.)  This would allow you to make a relocatable executable, not just
 >> on Windows but on any system.  And it would be fully relocatable --
 >> copy the binary anywhere and it will work, without the need of
 >> supporting data files.
 >>
 >> This would also solve the problem with man pages noted above, as
 >> we would no longer need the -library flag.
 >>
 >> Anyway, I was going to use citeproc-hs as a model, so let me know what
 >> the problem was!
 >
 > The problem was just me: I didn't check if the code compiled with the
 > "embed_data_files" flag before releasing 0.3.6.
 >
 > The bug was due to the fact that when moving to hexpat I started using
 > lazy bytestrings for reading files, while embed-file uses strict
 > bytestrings, hence a type error -- easily fixed.

After compiling from the newest update from the git repository, 'make'
and 'make install' work fine, but I'm always getting the same error by
building the windows installer make-windows-installer.bat:

Linking dist\build\pandoc\pandoc.exe ...
Preprocessing executable 'make-pandoc-man-pages' for pandoc-1.10...
<command line>: cannot satisfy -package-id pandoc-1.10-inplace
     (use -v for more information)
cabal.exe: Error: some packages failed to install:
pandoc-1.10 failed during the building phase. The exception was:
ExitFailure 1

The error occurs by the line:
cabal-dev install --flags="executable -library blaze_html_0_5" --datasubdir=

Regards,

-- 
Cesar

Re: error on building the windows installer

[John MacFarlane]

+++ Cesar Romani [Dec 22 12 10:02 ]:
> On 08/11/2012 01:24 p.m., andrea rossato wrote:
> > John MacFarlane<fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>  writes:
> >
> >>> In citeproc-hs there also seems to be a bug which shows up when
> building
> >>> with the "embed_data_files" flags. I'm going to fix it later this
> >>> afternoon.
> >>
> >> My present thought is that pandoc's 'library' and 'executable' flags
> >> create too many problems.  I'm thinking of getting rid of them, and
> >> adding an embed_data_files flag to embed the data files into the binary.
> >> (The added size is fairly insignificant since the binary is already so
> >> large.)  This would allow you to make a relocatable executable, not just
> >> on Windows but on any system.  And it would be fully relocatable --
> >> copy the binary anywhere and it will work, without the need of
> >> supporting data files.
> >>
> >> This would also solve the problem with man pages noted above, as
> >> we would no longer need the -library flag.
> >>
> >> Anyway, I was going to use citeproc-hs as a model, so let me know what
> >> the problem was!
> >
> > The problem was just me: I didn't check if the code compiled with the
> > "embed_data_files" flag before releasing 0.3.6.
> >
> > The bug was due to the fact that when moving to hexpat I started using
> > lazy bytestrings for reading files, while embed-file uses strict
> > bytestrings, hence a type error -- easily fixed.
> 
> After compiling from the newest update from the git repository, 'make'
> and 'make install' work fine, but I'm always getting the same error by
> building the windows installer make-windows-installer.bat:
> 
> Linking dist\build\pandoc\pandoc.exe ...
> Preprocessing executable 'make-pandoc-man-pages' for pandoc-1.10...
> <command line>: cannot satisfy -package-id pandoc-1.10-inplace
>     (use -v for more information)
> cabal.exe: Error: some packages failed to install:
> pandoc-1.10 failed during the building phase. The exception was:
> ExitFailure 1
> 
> The error occurs by the line:
> cabal-dev install --flags="executable -library blaze_html_0_5" --datasubdir=

Yes, when you tried this I hadn't yet made the change discussed above.
I have made it now but have not yet tested the windows installer.
You may do so if you wish.

Be sure to do a 'git submodule update' after 'git pull'.

Re: error on building the windows installer

[Cesar Romani]

On 29/12/2012 10:34 p.m., John MacFarlane wrote:
 > +++ Cesar Romani [Dec 22 12 10:02 ]:
 >> On 08/11/2012 01:24 p.m., andrea rossato wrote:
 >>> John 
MacFarlane<fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>   writes:
 >>>
 >>>>> In citeproc-hs there also seems to be a bug which shows up when
 >> building
 >>>>> with the "embed_data_files" flags. I'm going to fix it later this
 >>>>> afternoon.
 >>>>
 >>>> My present thought is that pandoc's 'library' and 'executable' flags
 >>>> create too many problems.  I'm thinking of getting rid of them, and
 >>>> adding an embed_data_files flag to embed the data files into the 
binary.
 >>>> (The added size is fairly insignificant since the binary is already so
 >>>> large.)  This would allow you to make a relocatable executable, 
not just
 >>>> on Windows but on any system.  And it would be fully relocatable --
 >>>> copy the binary anywhere and it will work, without the need of
 >>>> supporting data files.
 >>>>
 >>>> This would also solve the problem with man pages noted above, as
 >>>> we would no longer need the -library flag.
 >>>>
 >>>> Anyway, I was going to use citeproc-hs as a model, so let me know what
 >>>> the problem was!
 >>>
 >>> The problem was just me: I didn't check if the code compiled with the
 >>> "embed_data_files" flag before releasing 0.3.6.
 >>>
 >>> The bug was due to the fact that when moving to hexpat I started using
 >>> lazy bytestrings for reading files, while embed-file uses strict
 >>> bytestrings, hence a type error -- easily fixed.
 >>
 >> After compiling from the newest update from the git repository, 'make'
 >> and 'make install' work fine, but I'm always getting the same error by
 >> building the windows installer make-windows-installer.bat:
 >>
 >> Linking dist\build\pandoc\pandoc.exe ...
 >> Preprocessing executable 'make-pandoc-man-pages' for pandoc-1.10...
 >> <command line>: cannot satisfy -package-id pandoc-1.10-inplace
 >>      (use -v for more information)
 >> cabal.exe: Error: some packages failed to install:
 >> pandoc-1.10 failed during the building phase. The exception was:
 >> ExitFailure 1
 >>
 >> The error occurs by the line:
 >> cabal-dev install --flags="executable -library blaze_html_0_5" 
--datasubdir=
 >
 > Yes, when you tried this I hadn't yet made the change discussed above.
 > I have made it now but have not yet tested the windows installer.
 > You may do so if you wish.
 >
 > Be sure to do a 'git submodule update' after 'git pull'.

I did it, but on 'make' I get:
$ make
cabal-dev configure --enable-tests --enable-benchmarks && cabal-dev build
Configuring pandoc-1.10...
setup.exe: At least the following dependencies are missing:
Diff ==0.2.*
Resolving dependencies...
make: *** [all] Error 1

Then I did 'cabal install Diff' but I get the same result.

Regards,

-- 
Cesar

Re: error on building the windows installer

[John MacFarlane]

+++ Cesar Romani [Jan 02 13 15:41 ]:
> On 29/12/2012 10:34 p.m., John MacFarlane wrote:
> > +++ Cesar Romani [Dec 22 12 10:02 ]:
> >> On 08/11/2012 01:24 p.m., andrea rossato wrote:
> >>> John MacFarlane<fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>   writes:
> >>>
> >>>>> In citeproc-hs there also seems to be a bug which shows up when
> >> building
> >>>>> with the "embed_data_files" flags. I'm going to fix it later this
> >>>>> afternoon.
> >>>>
> >>>> My present thought is that pandoc's 'library' and 'executable' flags
> >>>> create too many problems.  I'm thinking of getting rid of them, and
> >>>> adding an embed_data_files flag to embed the data files into
> the binary.
> >>>> (The added size is fairly insignificant since the binary is already so
> >>>> large.)  This would allow you to make a relocatable executable,
> not just
> >>>> on Windows but on any system.  And it would be fully relocatable --
> >>>> copy the binary anywhere and it will work, without the need of
> >>>> supporting data files.
> >>>>
> >>>> This would also solve the problem with man pages noted above, as
> >>>> we would no longer need the -library flag.
> >>>>
> >>>> Anyway, I was going to use citeproc-hs as a model, so let me know what
> >>>> the problem was!
> >>>
> >>> The problem was just me: I didn't check if the code compiled with the
> >>> "embed_data_files" flag before releasing 0.3.6.
> >>>
> >>> The bug was due to the fact that when moving to hexpat I started using
> >>> lazy bytestrings for reading files, while embed-file uses strict
> >>> bytestrings, hence a type error -- easily fixed.
> >>
> >> After compiling from the newest update from the git repository, 'make'
> >> and 'make install' work fine, but I'm always getting the same error by
> >> building the windows installer make-windows-installer.bat:
> >>
> >> Linking dist\build\pandoc\pandoc.exe ...
> >> Preprocessing executable 'make-pandoc-man-pages' for pandoc-1.10...
> >> <command line>: cannot satisfy -package-id pandoc-1.10-inplace
> >>      (use -v for more information)
> >> cabal.exe: Error: some packages failed to install:
> >> pandoc-1.10 failed during the building phase. The exception was:
> >> ExitFailure 1
> >>
> >> The error occurs by the line:
> >> cabal-dev install --flags="executable -library blaze_html_0_5"
> --datasubdir=
> >
> > Yes, when you tried this I hadn't yet made the change discussed above.
> > I have made it now but have not yet tested the windows installer.
> > You may do so if you wish.
> >
> > Be sure to do a 'git submodule update' after 'git pull'.
> 
> I did it, but on 'make' I get:
> $ make
> cabal-dev configure --enable-tests --enable-benchmarks && cabal-dev build
> Configuring pandoc-1.10...
> setup.exe: At least the following dependencies are missing:
> Diff ==0.2.*
> Resolving dependencies...
> make: *** [all] Error 1
> 
> Then I did 'cabal install Diff' but I get the same result.

Well, the message is telling you that you don't have the Diff 0.2
library, which is a dependency of pandoc.  Try 'make prep' to
install all the dependencies.

('cabal install' won't help anyway, since the Makefile is using
a cabal-dev sandbox.  You could do 'cabal update && cabal-dev install').

Re: error on building the windows installer

[Huashan Chen]

Hi John,

I am wondering if it's possible to re-assign another data directory
with `--data-dir` parameter to pandoc compiled with `embed_data_files`
flag? I ask because all the following commands failed under Windows.

>pandoc readme -o readme.docx --reference-docx=ref.docx  --data-dir=d:\pandoc\data\
>pandoc readme -o readme.docx --reference-docx=ref.docx  --data-dir=data
>pandoc readme -o readme.docx --reference-docx=ref.docx  --data-dir=.\data\


Best,

Chen, Huashan


On Thu, Jan 3, 2013 at 7:55 AM, John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> +++ Cesar Romani [Jan 02 13 15:41 ]:
>> On 29/12/2012 10:34 p.m., John MacFarlane wrote:
>> > +++ Cesar Romani [Dec 22 12 10:02 ]:
>> >> On 08/11/2012 01:24 p.m., andrea rossato wrote:
>> >>> John MacFarlane<fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>   writes:
>> >>>
>> >>>>> In citeproc-hs there also seems to be a bug which shows up when
>> >> building
>> >>>>> with the "embed_data_files" flags. I'm going to fix it later this
>> >>>>> afternoon.
>> >>>>
>> >>>> My present thought is that pandoc's 'library' and 'executable' flags
>> >>>> create too many problems.  I'm thinking of getting rid of them, and
>> >>>> adding an embed_data_files flag to embed the data files into
>> the binary.
>> >>>> (The added size is fairly insignificant since the binary is already so
>> >>>> large.)  This would allow you to make a relocatable executable,
>> not just
>> >>>> on Windows but on any system.  And it would be fully relocatable --
>> >>>> copy the binary anywhere and it will work, without the need of
>> >>>> supporting data files.
>> >>>>
>> >>>> This would also solve the problem with man pages noted above, as
>> >>>> we would no longer need the -library flag.
>> >>>>
>> >>>> Anyway, I was going to use citeproc-hs as a model, so let me know what
>> >>>> the problem was!
>> >>>
>> >>> The problem was just me: I didn't check if the code compiled with the
>> >>> "embed_data_files" flag before releasing 0.3.6.
>> >>>
>> >>> The bug was due to the fact that when moving to hexpat I started using
>> >>> lazy bytestrings for reading files, while embed-file uses strict
>> >>> bytestrings, hence a type error -- easily fixed.
>> >>
>> >> After compiling from the newest update from the git repository, 'make'
>> >> and 'make install' work fine, but I'm always getting the same error by
>> >> building the windows installer make-windows-installer.bat:
>> >>
>> >> Linking dist\build\pandoc\pandoc.exe ...
>> >> Preprocessing executable 'make-pandoc-man-pages' for pandoc-1.10...
>> >> <command line>: cannot satisfy -package-id pandoc-1.10-inplace
>> >>      (use -v for more information)
>> >> cabal.exe: Error: some packages failed to install:
>> >> pandoc-1.10 failed during the building phase. The exception was:
>> >> ExitFailure 1
>> >>
>> >> The error occurs by the line:
>> >> cabal-dev install --flags="executable -library blaze_html_0_5"
>> --datasubdir=
>> >
>> > Yes, when you tried this I hadn't yet made the change discussed above.
>> > I have made it now but have not yet tested the windows installer.
>> > You may do so if you wish.
>> >
>> > Be sure to do a 'git submodule update' after 'git pull'.
>>
>> I did it, but on 'make' I get:
>> $ make
>> cabal-dev configure --enable-tests --enable-benchmarks && cabal-dev build
>> Configuring pandoc-1.10...
>> setup.exe: At least the following dependencies are missing:
>> Diff ==0.2.*
>> Resolving dependencies...
>> make: *** [all] Error 1
>>
>> Then I did 'cabal install Diff' but I get the same result.
>
> Well, the message is telling you that you don't have the Diff 0.2
> library, which is a dependency of pandoc.  Try 'make prep' to
> install all the dependencies.
>
> ('cabal install' won't help anyway, since the Makefile is using
> a cabal-dev sandbox.  You could do 'cabal update && cabal-dev install').
>
> --
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Re: error on building the windows installer

[John MacFarlane]

Yes, it should be.  The code only uses the embedded data if
the data file is not found under the specified data-dir.
I've tested it on Windows and it seems to work.

Maybe you could say more about the nature of the "failure"
you're seeing.

(By the way, if you specify --reference-doc=PATH, it will use
PATH, not data-dir\PATH.  Could that be the confusion?)

+++ Huashan Chen [Jan 10 13 22:48 ]:
> Hi John,
> 
> I am wondering if it's possible to re-assign another data directory
> with `--data-dir` parameter to pandoc compiled with `embed_data_files`
> flag? I ask because all the following commands failed under Windows.
> 
> >pandoc readme -o readme.docx --reference-docx=ref.docx  --data-dir=d:\pandoc\data\
> >pandoc readme -o readme.docx --reference-docx=ref.docx  --data-dir=data
> >pandoc readme -o readme.docx --reference-docx=ref.docx  --data-dir=.\data\
> 
> 
> Best,
> 
> Chen, Huashan
> 
> 
> On Thu, Jan 3, 2013 at 7:55 AM, John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > +++ Cesar Romani [Jan 02 13 15:41 ]:
> >> On 29/12/2012 10:34 p.m., John MacFarlane wrote:
> >> > +++ Cesar Romani [Dec 22 12 10:02 ]:
> >> >> On 08/11/2012 01:24 p.m., andrea rossato wrote:
> >> >>> John MacFarlane<fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>   writes:
> >> >>>
> >> >>>>> In citeproc-hs there also seems to be a bug which shows up when
> >> >> building
> >> >>>>> with the "embed_data_files" flags. I'm going to fix it later this
> >> >>>>> afternoon.
> >> >>>>
> >> >>>> My present thought is that pandoc's 'library' and 'executable' flags
> >> >>>> create too many problems.  I'm thinking of getting rid of them, and
> >> >>>> adding an embed_data_files flag to embed the data files into
> >> the binary.
> >> >>>> (The added size is fairly insignificant since the binary is already so
> >> >>>> large.)  This would allow you to make a relocatable executable,
> >> not just
> >> >>>> on Windows but on any system.  And it would be fully relocatable --
> >> >>>> copy the binary anywhere and it will work, without the need of
> >> >>>> supporting data files.
> >> >>>>
> >> >>>> This would also solve the problem with man pages noted above, as
> >> >>>> we would no longer need the -library flag.
> >> >>>>
> >> >>>> Anyway, I was going to use citeproc-hs as a model, so let me know what
> >> >>>> the problem was!
> >> >>>
> >> >>> The problem was just me: I didn't check if the code compiled with the
> >> >>> "embed_data_files" flag before releasing 0.3.6.
> >> >>>
> >> >>> The bug was due to the fact that when moving to hexpat I started using
> >> >>> lazy bytestrings for reading files, while embed-file uses strict
> >> >>> bytestrings, hence a type error -- easily fixed.
> >> >>
> >> >> After compiling from the newest update from the git repository, 'make'
> >> >> and 'make install' work fine, but I'm always getting the same error by
> >> >> building the windows installer make-windows-installer.bat:
> >> >>
> >> >> Linking dist\build\pandoc\pandoc.exe ...
> >> >> Preprocessing executable 'make-pandoc-man-pages' for pandoc-1.10...
> >> >> <command line>: cannot satisfy -package-id pandoc-1.10-inplace
> >> >>      (use -v for more information)
> >> >> cabal.exe: Error: some packages failed to install:
> >> >> pandoc-1.10 failed during the building phase. The exception was:
> >> >> ExitFailure 1
> >> >>
> >> >> The error occurs by the line:
> >> >> cabal-dev install --flags="executable -library blaze_html_0_5"
> >> --datasubdir=
> >> >
> >> > Yes, when you tried this I hadn't yet made the change discussed above.
> >> > I have made it now but have not yet tested the windows installer.
> >> > You may do so if you wish.
> >> >
> >> > Be sure to do a 'git submodule update' after 'git pull'.
> >>
> >> I did it, but on 'make' I get:
> >> $ make
> >> cabal-dev configure --enable-tests --enable-benchmarks && cabal-dev build
> >> Configuring pandoc-1.10...
> >> setup.exe: At least the following dependencies are missing:
> >> Diff ==0.2.*
> >> Resolving dependencies...
> >> make: *** [all] Error 1
> >>
> >> Then I did 'cabal install Diff' but I get the same result.
> >
> > Well, the message is telling you that you don't have the Diff 0.2
> > library, which is a dependency of pandoc.  Try 'make prep' to
> > install all the dependencies.
> >
> > ('cabal install' won't help anyway, since the Makefile is using
> > a cabal-dev sandbox.  You could do 'cabal update && cabal-dev install').
> >
> > --
> > You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> > To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> >
> 
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> For more options, visit https://groups.google.com/groups/opt_out.
> 
> 

Re: error on building the windows installer

[Huashan Chen]

Oops, I forgot to post the error messages, here it is (for all the
three commands mentioned above)

pandoc: Duplicate link reference `[PHP markdown extra]' "source" (line
1519, column 1)
pandoc: reference.docx: openBinaryFile: does not exist (No such file
or directory)

--reference-doc=PATH works fine though. However, in some
circumstances, --data-dir is much convient.



Best,

Chen, Huashan


On Fri, Jan 11, 2013 at 1:26 AM, John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> Yes, it should be.  The code only uses the embedded data if
> the data file is not found under the specified data-dir.
> I've tested it on Windows and it seems to work.
>
> Maybe you could say more about the nature of the "failure"
> you're seeing.
>
> (By the way, if you specify --reference-doc=PATH, it will use
> PATH, not data-dir\PATH.  Could that be the confusion?)
>
> +++ Huashan Chen [Jan 10 13 22:48 ]:
>> Hi John,
>>
>> I am wondering if it's possible to re-assign another data directory
>> with `--data-dir` parameter to pandoc compiled with `embed_data_files`
>> flag? I ask because all the following commands failed under Windows.
>>
>> >pandoc readme -o readme.docx --reference-docx=ref.docx  --data-dir=d:\pandoc\data\
>> >pandoc readme -o readme.docx --reference-docx=ref.docx  --data-dir=data
>> >pandoc readme -o readme.docx --reference-docx=ref.docx  --data-dir=.\data\
>>
>>
>> Best,
>>
>> Chen, Huashan
>>
>>
>> On Thu, Jan 3, 2013 at 7:55 AM, John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> > +++ Cesar Romani [Jan 02 13 15:41 ]:
>> >> On 29/12/2012 10:34 p.m., John MacFarlane wrote:
>> >> > +++ Cesar Romani [Dec 22 12 10:02 ]:
>> >> >> On 08/11/2012 01:24 p.m., andrea rossato wrote:
>> >> >>> John MacFarlane<fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>   writes:
>> >> >>>
>> >> >>>>> In citeproc-hs there also seems to be a bug which shows up when
>> >> >> building
>> >> >>>>> with the "embed_data_files" flags. I'm going to fix it later this
>> >> >>>>> afternoon.
>> >> >>>>
>> >> >>>> My present thought is that pandoc's 'library' and 'executable' flags
>> >> >>>> create too many problems.  I'm thinking of getting rid of them, and
>> >> >>>> adding an embed_data_files flag to embed the data files into
>> >> the binary.
>> >> >>>> (The added size is fairly insignificant since the binary is already so
>> >> >>>> large.)  This would allow you to make a relocatable executable,
>> >> not just
>> >> >>>> on Windows but on any system.  And it would be fully relocatable --
>> >> >>>> copy the binary anywhere and it will work, without the need of
>> >> >>>> supporting data files.
>> >> >>>>
>> >> >>>> This would also solve the problem with man pages noted above, as
>> >> >>>> we would no longer need the -library flag.
>> >> >>>>
>> >> >>>> Anyway, I was going to use citeproc-hs as a model, so let me know what
>> >> >>>> the problem was!
>> >> >>>
>> >> >>> The problem was just me: I didn't check if the code compiled with the
>> >> >>> "embed_data_files" flag before releasing 0.3.6.
>> >> >>>
>> >> >>> The bug was due to the fact that when moving to hexpat I started using
>> >> >>> lazy bytestrings for reading files, while embed-file uses strict
>> >> >>> bytestrings, hence a type error -- easily fixed.
>> >> >>
>> >> >> After compiling from the newest update from the git repository, 'make'
>> >> >> and 'make install' work fine, but I'm always getting the same error by
>> >> >> building the windows installer make-windows-installer.bat:
>> >> >>
>> >> >> Linking dist\build\pandoc\pandoc.exe ...
>> >> >> Preprocessing executable 'make-pandoc-man-pages' for pandoc-1.10...
>> >> >> <command line>: cannot satisfy -package-id pandoc-1.10-inplace
>> >> >>      (use -v for more information)
>> >> >> cabal.exe: Error: some packages failed to install:
>> >> >> pandoc-1.10 failed during the building phase. The exception was:
>> >> >> ExitFailure 1
>> >> >>
>> >> >> The error occurs by the line:
>> >> >> cabal-dev install --flags="executable -library blaze_html_0_5"
>> >> --datasubdir=
>> >> >
>> >> > Yes, when you tried this I hadn't yet made the change discussed above.
>> >> > I have made it now but have not yet tested the windows installer.
>> >> > You may do so if you wish.
>> >> >
>> >> > Be sure to do a 'git submodule update' after 'git pull'.
>> >>
>> >> I did it, but on 'make' I get:
>> >> $ make
>> >> cabal-dev configure --enable-tests --enable-benchmarks && cabal-dev build
>> >> Configuring pandoc-1.10...
>> >> setup.exe: At least the following dependencies are missing:
>> >> Diff ==0.2.*
>> >> Resolving dependencies...
>> >> make: *** [all] Error 1
>> >>
>> >> Then I did 'cabal install Diff' but I get the same result.
>> >
>> > Well, the message is telling you that you don't have the Diff 0.2
>> > library, which is a dependency of pandoc.  Try 'make prep' to
>> > install all the dependencies.
>> >
>> > ('cabal install' won't help anyway, since the Makefile is using
>> > a cabal-dev sandbox.  You could do 'cabal update && cabal-dev install').
>> >
>> > --
>> > You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
>> > To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> > To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> > For more options, visit https://groups.google.com/groups/opt_out.
>> >
>> >
>>
>> --
>> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
>> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>
> --
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Re: error on building the windows installer

[John MacFarlane]

+++ Huashan Chen [Jan 11 13 21:39 ]:
> Oops, I forgot to post the error messages, here it is (for all the
> three commands mentioned above)
> 
> pandoc: Duplicate link reference `[PHP markdown extra]' "source" (line
> 1519, column 1)

This shows that you're not using the latest version, since the
README was fixed to avoid this duplicate reference.

> pandoc: reference.docx: openBinaryFile: does not exist (No such file
> or directory)
> 
> --reference-doc=PATH works fine though. However, in some
> circumstances, --data-dir is much convient.

I still don't see any evidence of a change in functionality.
I think you are assuming that

--reference-docx=FILE --data-dir=DIR

will look for the reference-docx in DIR/FILE.  I don't think
that was ever the case.  You can either do

--reference-docx=PATH

or put reference.docx in DIR and do

--data-dir=DIR

(with --reference-docx).

John

Re: error on building the windows installer

[Huashan Chen]

Hi, John,

Do you mean that I couldn't place my customized docx file in `data`
directory and use

--reference-docx=MYFILE --data-dir=DIR

together? According to the manual, I'd thought that pandoc will look
for MYFILE in DIR.


Best,

Chen, Huashan


On Fri, Jan 11, 2013 at 11:43 PM, John MacFarlane
<fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> +++ Huashan Chen [Jan 11 13 21:39 ]:
>> Oops, I forgot to post the error messages, here it is (for all the
>> three commands mentioned above)
>>
>> pandoc: Duplicate link reference `[PHP markdown extra]' "source" (line
>> 1519, column 1)
>
> This shows that you're not using the latest version, since the
> README was fixed to avoid this duplicate reference.
>
>> pandoc: reference.docx: openBinaryFile: does not exist (No such file
>> or directory)
>>
>> --reference-doc=PATH works fine though. However, in some
>> circumstances, --data-dir is much convient.
>
> I still don't see any evidence of a change in functionality.
> I think you are assuming that
>
> --reference-docx=FILE --data-dir=DIR
>
> will look for the reference-docx in DIR/FILE.  I don't think
> that was ever the case.  You can either do
>
> --reference-docx=PATH
>
> or put reference.docx in DIR and do
>
> --data-dir=DIR
>
> (with --reference-docx).
>
> John
>
> --
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

Re: error on building the windows installer

[John MacFarlane]

+++ Huashan Chen [Jan 13 13 00:45 ]:
> Hi, John,
> 
> Do you mean that I couldn't place my customized docx file in `data`
> directory and use
> 
> --reference-docx=MYFILE --data-dir=DIR
> 
> together? According to the manual, I'd thought that pandoc will look
> for MYFILE in DIR.

No.  If you leave off --reference-docx, it will look for reference.docx
in DIR, but if you specify --reference-docx, it will assume that you're
giving the whole path to the file.

John

Re: error on building the windows installer

[Huashan Chen]

[-- Attachment #1: Type: text/plain, Size: 1440 bytes --]

Thank you, that solves my puzzle.
在 2013-1-13 AM1:42，"John MacFarlane" <fiddlosopher-Re5JQEeQqe8@public.gmane.orgm>写道：

> +++ Huashan Chen [Jan 13 13 00:45 ]:
> > Hi, John,
> >
> > Do you mean that I couldn't place my customized docx file in `data`
> > directory and use
> >
> > --reference-docx=MYFILE --data-dir=DIR
> >
> > together? According to the manual, I'd thought that pandoc will look
> > for MYFILE in DIR.
>
> No.  If you leave off --reference-docx, it will look for reference.docx
> in DIR, but if you specify --reference-docx, it will assume that you're
> giving the whole path to the file.
>
> John
>
> --
> You received this message because you are subscribed to the Google Groups
> "pandoc-discuss" group.
> To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To unsubscribe from this group, send email to
> pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To unsubscribe from this group, send email to pandoc-discuss+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



[-- Attachment #2: Type: text/html, Size: 2093 bytes --]