I can't write on file 'foo.aux'












4















I am getting an error when compiling this template with pdflatex -output-directory=./_out thesis.tex:



! I can't write on file `text/abbreviations.aux'.
@include ...immediate openout @partaux #1.aux
immediate write @partau...
l.187 include{text/abbreviations}

(Press Enter to retry, or Control-D to exit; default file extension is `.tex')
Please type another output file name: ^D
! Emergency stop.
@include ...immediate openout @partaux #1.aux
immediate write @partau...
l.187 include{text/abbreviations}

! ==> Fatal error occurred, no output PDF file produced!
Transcript written on _out/thesis.log.


This is usually the way that I use the -output-directory option, and I have never had a problem with that usage before, but I must be doing something wrong because the compiling works fine without this option.





File Tree



Result of ls -R from the project root:



_README.txt     _out            figures         ociamthesis.cls references.bib  splitcolor.py   text            thesis.tex

./_out:
thesis.aux thesis.bcf thesis.lof thesis.mtc thesis.out
thesis.bbl thesis.blg thesis.log thesis.mtc0 thesis.toc

./figures:
beltcrest.pdf sample

./figures/sample:
Gray498.png

./text:
abbreviations.tex abstract.tex acknowledgements.tex appendix-1.tex ch1-intro.tex ch2-litreview.tex


Version



I am on OSX and the manual for pdflatex doesn't show any option -aux_directory, my version is:



pdfTeX 3.14159265-2.6-1.40.16 (TeX Live 2015)
kpathsea version 6.2.1
Copyright 2015 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
There is NO warranty. Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
Compiled with libpng 1.6.17; using libpng 1.6.17
Compiled with zlib 1.2.8; using zlib 1.2.8
Compiled with xpdf version 3.04









share|improve this question




















  • 3





    I think you'd need (at least) a text subdirectory of _out but it's always simpler not to use --output-directory which greatly complicates the processing model and provides no features.

    – David Carlisle
    Aug 8 '16 at 10:59











  • You are right, it was just a matter of creating a subfolder _out/text, sorry for that silly question!

    – Sheljohn
    Aug 8 '16 at 11:14
















4















I am getting an error when compiling this template with pdflatex -output-directory=./_out thesis.tex:



! I can't write on file `text/abbreviations.aux'.
@include ...immediate openout @partaux #1.aux
immediate write @partau...
l.187 include{text/abbreviations}

(Press Enter to retry, or Control-D to exit; default file extension is `.tex')
Please type another output file name: ^D
! Emergency stop.
@include ...immediate openout @partaux #1.aux
immediate write @partau...
l.187 include{text/abbreviations}

! ==> Fatal error occurred, no output PDF file produced!
Transcript written on _out/thesis.log.


This is usually the way that I use the -output-directory option, and I have never had a problem with that usage before, but I must be doing something wrong because the compiling works fine without this option.





File Tree



Result of ls -R from the project root:



_README.txt     _out            figures         ociamthesis.cls references.bib  splitcolor.py   text            thesis.tex

./_out:
thesis.aux thesis.bcf thesis.lof thesis.mtc thesis.out
thesis.bbl thesis.blg thesis.log thesis.mtc0 thesis.toc

./figures:
beltcrest.pdf sample

./figures/sample:
Gray498.png

./text:
abbreviations.tex abstract.tex acknowledgements.tex appendix-1.tex ch1-intro.tex ch2-litreview.tex


Version



I am on OSX and the manual for pdflatex doesn't show any option -aux_directory, my version is:



pdfTeX 3.14159265-2.6-1.40.16 (TeX Live 2015)
kpathsea version 6.2.1
Copyright 2015 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
There is NO warranty. Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
Compiled with libpng 1.6.17; using libpng 1.6.17
Compiled with zlib 1.2.8; using zlib 1.2.8
Compiled with xpdf version 3.04









share|improve this question




















  • 3





    I think you'd need (at least) a text subdirectory of _out but it's always simpler not to use --output-directory which greatly complicates the processing model and provides no features.

    – David Carlisle
    Aug 8 '16 at 10:59











  • You are right, it was just a matter of creating a subfolder _out/text, sorry for that silly question!

    – Sheljohn
    Aug 8 '16 at 11:14














4












4








4








I am getting an error when compiling this template with pdflatex -output-directory=./_out thesis.tex:



! I can't write on file `text/abbreviations.aux'.
@include ...immediate openout @partaux #1.aux
immediate write @partau...
l.187 include{text/abbreviations}

(Press Enter to retry, or Control-D to exit; default file extension is `.tex')
Please type another output file name: ^D
! Emergency stop.
@include ...immediate openout @partaux #1.aux
immediate write @partau...
l.187 include{text/abbreviations}

! ==> Fatal error occurred, no output PDF file produced!
Transcript written on _out/thesis.log.


This is usually the way that I use the -output-directory option, and I have never had a problem with that usage before, but I must be doing something wrong because the compiling works fine without this option.





File Tree



Result of ls -R from the project root:



_README.txt     _out            figures         ociamthesis.cls references.bib  splitcolor.py   text            thesis.tex

./_out:
thesis.aux thesis.bcf thesis.lof thesis.mtc thesis.out
thesis.bbl thesis.blg thesis.log thesis.mtc0 thesis.toc

./figures:
beltcrest.pdf sample

./figures/sample:
Gray498.png

./text:
abbreviations.tex abstract.tex acknowledgements.tex appendix-1.tex ch1-intro.tex ch2-litreview.tex


Version



I am on OSX and the manual for pdflatex doesn't show any option -aux_directory, my version is:



pdfTeX 3.14159265-2.6-1.40.16 (TeX Live 2015)
kpathsea version 6.2.1
Copyright 2015 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
There is NO warranty. Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
Compiled with libpng 1.6.17; using libpng 1.6.17
Compiled with zlib 1.2.8; using zlib 1.2.8
Compiled with xpdf version 3.04









share|improve this question
















I am getting an error when compiling this template with pdflatex -output-directory=./_out thesis.tex:



! I can't write on file `text/abbreviations.aux'.
@include ...immediate openout @partaux #1.aux
immediate write @partau...
l.187 include{text/abbreviations}

(Press Enter to retry, or Control-D to exit; default file extension is `.tex')
Please type another output file name: ^D
! Emergency stop.
@include ...immediate openout @partaux #1.aux
immediate write @partau...
l.187 include{text/abbreviations}

! ==> Fatal error occurred, no output PDF file produced!
Transcript written on _out/thesis.log.


This is usually the way that I use the -output-directory option, and I have never had a problem with that usage before, but I must be doing something wrong because the compiling works fine without this option.





File Tree



Result of ls -R from the project root:



_README.txt     _out            figures         ociamthesis.cls references.bib  splitcolor.py   text            thesis.tex

./_out:
thesis.aux thesis.bcf thesis.lof thesis.mtc thesis.out
thesis.bbl thesis.blg thesis.log thesis.mtc0 thesis.toc

./figures:
beltcrest.pdf sample

./figures/sample:
Gray498.png

./text:
abbreviations.tex abstract.tex acknowledgements.tex appendix-1.tex ch1-intro.tex ch2-litreview.tex


Version



I am on OSX and the manual for pdflatex doesn't show any option -aux_directory, my version is:



pdfTeX 3.14159265-2.6-1.40.16 (TeX Live 2015)
kpathsea version 6.2.1
Copyright 2015 Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
There is NO warranty. Redistribution of this software is
covered by the terms of both the pdfTeX copyright and
the Lesser GNU General Public License.
For more information about these matters, see the file
named COPYING and the pdfTeX source.
Primary author of pdfTeX: Peter Breitenlohner (eTeX)/Han The Thanh (pdfTeX).
Compiled with libpng 1.6.17; using libpng 1.6.17
Compiled with zlib 1.2.8; using zlib 1.2.8
Compiled with xpdf version 3.04






errors output






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Aug 14 '16 at 8:29









Johannes_B

20.9k351201




20.9k351201










asked Aug 8 '16 at 10:54









SheljohnSheljohn

433418




433418








  • 3





    I think you'd need (at least) a text subdirectory of _out but it's always simpler not to use --output-directory which greatly complicates the processing model and provides no features.

    – David Carlisle
    Aug 8 '16 at 10:59











  • You are right, it was just a matter of creating a subfolder _out/text, sorry for that silly question!

    – Sheljohn
    Aug 8 '16 at 11:14














  • 3





    I think you'd need (at least) a text subdirectory of _out but it's always simpler not to use --output-directory which greatly complicates the processing model and provides no features.

    – David Carlisle
    Aug 8 '16 at 10:59











  • You are right, it was just a matter of creating a subfolder _out/text, sorry for that silly question!

    – Sheljohn
    Aug 8 '16 at 11:14








3




3





I think you'd need (at least) a text subdirectory of _out but it's always simpler not to use --output-directory which greatly complicates the processing model and provides no features.

– David Carlisle
Aug 8 '16 at 10:59





I think you'd need (at least) a text subdirectory of _out but it's always simpler not to use --output-directory which greatly complicates the processing model and provides no features.

– David Carlisle
Aug 8 '16 at 10:59













You are right, it was just a matter of creating a subfolder _out/text, sorry for that silly question!

– Sheljohn
Aug 8 '16 at 11:14





You are right, it was just a matter of creating a subfolder _out/text, sorry for that silly question!

– Sheljohn
Aug 8 '16 at 11:14










2 Answers
2






active

oldest

votes


















3














@DavidCarlisle proposed a solution in comment of the OP. It seems to be sufficient to create a subdirectory _out/text for the compilation to succeed.






share|improve this answer































    0














    I had the same issue and solved it by writing a build script that creates subdirectories in my build folder that mirror the subdirectories in my source folder before compiling:



    #!/bin/sh

    for OUTPUT in $(find src -type d)
    do
    mkdir dist/$OUTPUT
    done

    pdflatex -output-directory=./dist ./src/main.tex


    This saves you having to manually create subdirectories every time you add one.





    share








    New contributor




    Kyle Meenehan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.




















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "85"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f323820%2fi-cant-write-on-file-foo-aux%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      3














      @DavidCarlisle proposed a solution in comment of the OP. It seems to be sufficient to create a subdirectory _out/text for the compilation to succeed.






      share|improve this answer




























        3














        @DavidCarlisle proposed a solution in comment of the OP. It seems to be sufficient to create a subdirectory _out/text for the compilation to succeed.






        share|improve this answer


























          3












          3








          3







          @DavidCarlisle proposed a solution in comment of the OP. It seems to be sufficient to create a subdirectory _out/text for the compilation to succeed.






          share|improve this answer













          @DavidCarlisle proposed a solution in comment of the OP. It seems to be sufficient to create a subdirectory _out/text for the compilation to succeed.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Aug 8 '16 at 11:13









          SheljohnSheljohn

          433418




          433418























              0














              I had the same issue and solved it by writing a build script that creates subdirectories in my build folder that mirror the subdirectories in my source folder before compiling:



              #!/bin/sh

              for OUTPUT in $(find src -type d)
              do
              mkdir dist/$OUTPUT
              done

              pdflatex -output-directory=./dist ./src/main.tex


              This saves you having to manually create subdirectories every time you add one.





              share








              New contributor




              Kyle Meenehan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.

























                0














                I had the same issue and solved it by writing a build script that creates subdirectories in my build folder that mirror the subdirectories in my source folder before compiling:



                #!/bin/sh

                for OUTPUT in $(find src -type d)
                do
                mkdir dist/$OUTPUT
                done

                pdflatex -output-directory=./dist ./src/main.tex


                This saves you having to manually create subdirectories every time you add one.





                share








                New contributor




                Kyle Meenehan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.























                  0












                  0








                  0







                  I had the same issue and solved it by writing a build script that creates subdirectories in my build folder that mirror the subdirectories in my source folder before compiling:



                  #!/bin/sh

                  for OUTPUT in $(find src -type d)
                  do
                  mkdir dist/$OUTPUT
                  done

                  pdflatex -output-directory=./dist ./src/main.tex


                  This saves you having to manually create subdirectories every time you add one.





                  share








                  New contributor




                  Kyle Meenehan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.










                  I had the same issue and solved it by writing a build script that creates subdirectories in my build folder that mirror the subdirectories in my source folder before compiling:



                  #!/bin/sh

                  for OUTPUT in $(find src -type d)
                  do
                  mkdir dist/$OUTPUT
                  done

                  pdflatex -output-directory=./dist ./src/main.tex


                  This saves you having to manually create subdirectories every time you add one.






                  share








                  New contributor




                  Kyle Meenehan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.








                  share


                  share






                  New contributor




                  Kyle Meenehan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  answered 6 mins ago









                  Kyle MeenehanKyle Meenehan

                  11




                  11




                  New contributor




                  Kyle Meenehan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.





                  New contributor





                  Kyle Meenehan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






                  Kyle Meenehan is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f323820%2fi-cant-write-on-file-foo-aux%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Accessing regular linux commands in Huawei's Dopra Linux

                      Can't connect RFCOMM socket: Host is down

                      Kernel panic - not syncing: Fatal Exception in Interrupt