VOGONS


Reply 20 of 30, by James-F

User metadata
Rank Oldbie
Rank
Oldbie

Windows path: C:\MinGW\msys\1.0\home\First Last\libogg-1.3.2

./configure --prefix="/home/First Last/libogg-1.3.2"
Alright, I've seen new files created and deleted in the libogg-1.3.2 directory while the ./configure command was running.

make: alright.

make install:

/bin/install: target `Last/libogg-1.3.2/lib/libogg.la' is not a directory make[2]: *** [install-libLTLIBRARIES] Error 1 make[2]: […]
Show full quote

/bin/install: target `Last/libogg-1.3.2/lib/libogg.la' is not a directory
make[2]: *** [install-libLTLIBRARIES] Error 1
make[2]: Leaving directory `/home/First Last/libogg-1.3.2/src'
make[1]: *** [install-am] Error 2


my important / useful posts are here

Reply 21 of 30, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

That's not your prefix. The prefix is where the stuff gets copied to.

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 23 of 30, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Seems the best way to do things is putting everything somewhere without spaces. So instead of your userspace, put it into c:/compile or something like that.
A quick search found that.

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 24 of 30, by Yesterplay80

User metadata
Rank Oldbie
Rank
Oldbie
James-F wrote:

For anti-frustration sake, can someone fix the WIKI? Please.
I'm a Copy-paster not a programmer.

You already found out that the problem is the space in the user name, so why don't you just use the test user you created? No need to get frustrated, at least not here, this looks more like a MinGW error (or issue) to me, since it happens with SDL_net as well.

James-F wrote:

Yet still I get the same error.

And you will keep getting this error, I can reproduce the error with another test user on a vm here:

/bin/sh: [b]/home/test[/b]: No such file or directory
make[2]: *** [install-libLTLIBRARIES] Error 127
make[2]: Leaving directory `[b]/home/test user[/b]/libogg-1.3.2/src'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/home/test user/libogg-1.3.2/src'
make: *** [install-recursive] Error 1

My full-featured DOSBox SVN builds for Windows & Linux: Vanilla DOSBox and DOSBox ECE (Google Drive Mirror)

Reply 26 of 30, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

But I now see in the wiki that stuff gets put inside mingw to a folder named after the user. I don't know an easy way yet. Somone on Windows needs to step up.

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 27 of 30, by James-F

User metadata
Rank Oldbie
Rank
Oldbie

I need help creating a diff file from two dosbox directories.

Now I use the following commnad:

diff -Nurb dosbos(original directory) dosbox(altered directory) > patch.diff […]
Show full quote

diff -Nurb dosbos(original directory) dosbox(altered directory) > patch.diff

-N treat missing files as empty, to create new files.
-u unify to single diff file.
-r directories (don't use if diff'ing individual files).
-b ignore white space.

The resulting diff file includes "--- dosbox/src/...", but on all patches I see --- +++ without the dosbox/ path and they are identical.
I have to manually remove the "--- dosbox/src/.." and change it to "--- src/.."
How do you create --- and +++ from the same place? I get an empty diff file (obviously).

Can anyone point me to the file which responsible for dosbox sound blaster Lowpass filer? I'd like to make it a little steeper to resemble a real SB more.
I looked in sblaster.cpp but nothing resembles a lowpass filter code.


my important / useful posts are here

Reply 28 of 30, by Ant_222

User metadata
Rank Oldbie
Rank
Oldbie
James-F wrote:

I need help creating a diff file from two dosbox directories.

Now I use the following commnad:

diff -Nurb dosbos(original directory) dosbox(altered directory) > patch.diff […]
Show full quote

diff -Nurb dosbos(original directory) dosbox(altered directory) > patch.diff

-N treat missing files as empty, to create new files.
-u unify to single diff file.
-r directories (don't use if diff'ing individual files).
-b ignore white space.

Not quite:

-u output NUM (default 3) lines of unified context
-r recursively traverse subdirectories. diff will
still check the individual files in the directory
specified on the command line, but won't enter its
subdirectories.
-b ignore white space--never do it, for programmers will
often use deliberately to separate code fragments or
or aling their code beautifully, e.g.

h_in = 200;
w_in = 320;
h_out = 480;
w_out = 640;

The resulting diff file includes "--- dosbox/src/...", but on all patches I see --- +++ without the dosbox/ path and they are identical.
I have to manually remove the "--- dosbox/src/.." and change it to "--- src/.."

I did not manually edit my latest pixel-perfect patch. To generate it, I changed into the directory with the patched version of DOSBox and executed:

diff -uprN ../dosbox-code-3989/ . > pixel-perfect-alpha2.patch

This way, diff will insert the correct relative paths to the new files.

How do you create --- and +++ from the same place? I get an empty diff file (obviously).

No idea, but I will find it out!

Can anyone point me to the file which responsible for dosbox sound blaster Lowpass filer? I'd like to make it a little steeper to resemble a real SB more.
I looked in sblaster.cpp but nothing resembles a lowpass filter code.

I can only suggest that you first locate the code that outputs sound (should be some SDL calls) and ascend the call tree from that. The documentation for SDL 1.2 is supplied with the source.

Reply 29 of 30, by Ant_222

User metadata
Rank Oldbie
Rank
Oldbie
Ant_222 wrote:
James-F wrote:

How do you create --- and +++ from the same place? I get an empty diff file (obviously).

No idea, but I will find it out!

The version-control system SVN does it.