Menu ▾ ▴

#560 path problems with msys-1.0.10

closed
Earnie Boyd
MSYS (75)
2004-05-14
2004-04-29
Stefan Sauer
No

I noticed a strange behaviour when accessing files.
When e.g. building software I have to rewrite include
path so that gcc find includes although the -I params
to gcc are correct (and the package builds under e.g.
linux). Apart the probelm also happens when
applications access files. If this is not easy to
locate or already fixed in CVS, then I'll try to come
up with e.g. a shell script or a little c-source to
show the effect.

Discussion

  • Earnie Boyd

    Earnie Boyd - 2004-04-29

    Logged In: YES
    user_id=15438

    You'll have to come up with the example. I don't have
    problems building software. Note, be sure to read the
    /doc/msys files, especially the README.rtf. You can't put
    the mingw gcc in the /bin or /usr/bin directories for
    version 1.0.10. The MSYS-1.0.11 snapshot does support this
    scenario as I've eliminated the need for that restriction.

    Earnie

     

  • Stefan Sauer

    Stefan Sauer - 2004-05-03

    Logged In: YES
    user_id=250654

    okay - here is an example :
    make[1]: Entering directory
    `E:/msys/home/ensonic/projects/ffmpeg/libavformat'
    gcc -I.. -I/home/ensonic/projects/ffmpeg
    -I/home/ensonic/projects/ffmpeg/libavcodec -c -o utils.o
    utils.c
    In file included from utils.c:19:
    avformat.h:16:21: avcodec.h: No such file or directory

    so it is not finding the file even though there has been
    -I/home/ensonic/projects/ffmpeg/libavcodec
    supplied. It is puzzling me as this works :

    $ ls /home/ensonic/projects/ffmpeg/libavcodec/avcodec.h
    /home/ensonic/projects/ffmpeg/libavcodec/avcodec.h

    Any idea?

     

  • Earnie Boyd

    Earnie Boyd - 2004-05-03

    Logged In: YES
    user_id=15438

    What is the output of ``msysinfo all''?

    Earnie

     

  • Stefan Sauer

    Stefan Sauer - 2004-05-03

    Logged In: YES
    user_id=250654

    see attached (uploaded) file

     

  • Stefan Sauer

    Stefan Sauer - 2004-05-03

    output of msysinfo all >msysinfo.txt

     
    msysinfo.txt

  • Earnie Boyd

    Earnie Boyd - 2004-05-13

    Logged In: YES
    user_id=15438

    You're not using the MSYS version of make. You need to
    rename the /mingw/bin/make.exe to /mingw/bin/mingw32-make.exe.

    Earnie.

     

  • Earnie Boyd

    Earnie Boyd - 2004-05-13
    • status: open --> pending
     

  • Stefan Sauer

    Stefan Sauer - 2004-05-14

    Logged In: YES
    user_id=250654

    I had renmaed /mingw/bin/make.exe to /mingw/bin/make-mingw.exe.
    Maybe you should write in the docs, that it had to be
    exactly this name.

    Anyway it makes no difference here. You can reproduce it
    with the cvs of ffmpeg (http://www.ffmpeg.org).

     

  • Stefan Sauer

    Stefan Sauer - 2004-05-14
    • priority: 5 --> 6
    • status: pending --> open
     

  • Earnie Boyd

    Earnie Boyd - 2004-05-14
    • status: open --> closed
     

  • Earnie Boyd

    Earnie Boyd - 2004-05-14

    Logged In: YES
    user_id=15438

    Your ``msysinfo all'' output told me your make.exe was in
    the /mingw/bin directory. The name you rename it too
    doesn't matter as long as it isn't make.exe so that
    /bin/make.exe will be used instead of /mingw/bin/make.exe
    when you type make. The version data should read:

    $ make --version
    GNU Make version 3.79.1, by Richard Stallman and Roland McGrath.
    Built for i686-pc-msys

    I may give your package a go later.

    Earnie

     

  • Luke Dunstan

    Luke Dunstan - 2004-05-14

    Logged In: YES
    user_id=30442

    Earnie must be correct. ffmpeg builds with no trouble for me
    using MSYS make.