zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Bugs that have been investigated and resolved somehow.

Moderator: GZDoom Developers

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
User avatar
morbidtwatt
Posts: 136
Joined: Fri Aug 15, 2003 7:56 am
Location: frederick md
Contact:

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by morbidtwatt »

i did the malloc thing and added the stdlib thing but the other stuff i have no clue what im looking for. i have a man page to the thing you said was in bsd

http://www.freebsd.org/cgi/man.cgi?quer ... ormat=html
User avatar
Chris
Posts: 2983
Joined: Thu Jul 17, 2003 12:07 am
Graphics Processor: ATI/AMD with Vulkan/Metal Support

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by Chris »

morbidtwatt wrote:i did the malloc thing and added the stdlib thing but the other stuff i have no clue what im looking for. i have a man page to the thing you said was in bsd
If you tried recompiling after that change and it still complained about malloc_usable_size, also add:

Code: Select all

#include <malloc_np.h>
User avatar
morbidtwatt
Posts: 136
Joined: Fri Aug 15, 2003 7:56 am
Location: frederick md
Contact:

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by morbidtwatt »

now i got this :-(

[ 37%] Building CXX object src/CMakeFiles/zdoom.dir/v_draw.o
/home/morbidtwatt/zdoomsrc/src/v_draw.cpp: In member function 'bool DCanvas::ParseDrawTextureTags(FTexture*, int, int, DWORD, char*, DCanvas::DrawParms*, bool) const':
/home/morbidtwatt/zdoomsrc/src/v_draw.cpp:363: error: '__va_copy' was not declared in this scope
*** Error code 1

Stop in /usr/home/morbidtwatt/zdoomsrc/release.
*** Error code 1

Stop in /usr/home/morbidtwatt/zdoomsrc/release.
*** Error code 1

Stop in /usr/home/morbidtwatt/zdoomsrc/release.
User avatar
Chris
Posts: 2983
Joined: Thu Jul 17, 2003 12:07 am
Graphics Processor: ATI/AMD with Vulkan/Metal Support

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by Chris »

Change the __va_copy to va_copy. Hopefully you're using a somewhat recent GCC version that has C99 support.
User avatar
morbidtwatt
Posts: 136
Joined: Fri Aug 15, 2003 7:56 am
Location: frederick md
Contact:

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by morbidtwatt »

hmm looks like its going well its doing somthing to o files objects?
Last edited by morbidtwatt on Mon Apr 06, 2009 1:47 am, edited 1 time in total.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
Posts: 49252
Joined: Sat Jul 19, 2003 10:19 am
Location: Germany

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by Graf Zahl »

Obviously.
User avatar
morbidtwatt
Posts: 136
Joined: Fri Aug 15, 2003 7:56 am
Location: frederick md
Contact:

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by morbidtwatt »

kill it daddy.. kill it.. fmod keeps haunting me in my dreams

[ 36%] Building CXX object src/CMakeFiles/zdoom.dir/oplsynth/music_opldumper_mididevice.o
In file included from /home/morbidtwatt/zdoomsrc/src/oplsynth/music_opldumper_mididevice.cpp:37:
/home/morbidtwatt/zdoomsrc/src/sound/i_musicinterns.h:17:18: error: fmod.h: No such file or directory
*** Error code 1

Stop in /usr/home/morbidtwatt/zdoomsrc/release.
*** Error code 1

Stop in /usr/home/morbidtwatt/zdoomsrc/release.
*** Error code 1

Stop in /usr/home/morbidtwatt/zdoomsrc/release.
User avatar
Chris
Posts: 2983
Joined: Thu Jul 17, 2003 12:07 am
Graphics Processor: ATI/AMD with Vulkan/Metal Support

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by Chris »

morbidtwatt wrote:/home/morbidtwatt/zdoomsrc/src/sound/i_musicinterns.h:17:18: error: fmod.h: No such file or directory
Missed that one. Edit i_musicinterns.h, and remove the line that includes fmod.h. It's not needed in that file.
User avatar
morbidtwatt
Posts: 136
Joined: Fri Aug 15, 2003 7:56 am
Location: frederick md
Contact:

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by morbidtwatt »

uhhhh ??

[ 38%] Building CXX object src/CMakeFiles/zdoom.dir/sound/music_midi_timidity.o
/home/morbidtwatt/zdoomsrc/src/sound/music_midi_timidity.cpp: In member function 'virtual void TimiditySong::Stop()':
/home/morbidtwatt/zdoomsrc/src/sound/music_midi_timidity.cpp:131: error: 'SIGTERM' was not declared in this scope
/home/morbidtwatt/zdoomsrc/src/sound/music_midi_timidity.cpp:131: error: 'kill' was not declared in this scope
/home/morbidtwatt/zdoomsrc/src/sound/music_midi_timidity.cpp:133: error: 'SIGKILL' was not declared in this scope
*** Error code 1

Stop in /usr/home/morbidtwatt/zdoomsrc/release.
*** Error code 1

Stop in /usr/home/morbidtwatt/zdoomsrc/release.
*** Error code 1

Stop in /usr/home/morbidtwatt/zdoomsrc/release.
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
Posts: 49252
Joined: Sat Jul 19, 2003 10:19 am
Location: Germany

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by Graf Zahl »

Your system headers fail it, apparently... ;)

Just comment out the code for now until someone with more knowledge can tell you how to get around it.
User avatar
Rachael
Posts: 13968
Joined: Tue Jan 13, 2004 1:31 pm
Preferred Pronouns: She/Her
Contact:

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by Rachael »

Ummm... wow... this is the reason why I do not, and never ever will in my entire life, use FreeBSD.

On Linux I got ZDoom to compile in less than 15 minutes worth of work.
User avatar
morbidtwatt
Posts: 136
Joined: Fri Aug 15, 2003 7:56 am
Location: frederick md
Contact:

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by morbidtwatt »

SoulPriestess wrote:Ummm... wow... this is the reason why I do not, and never ever will in my entire life, use FreeBSD.

On Linux I got ZDoom to compile in less than 15 minutes worth of work.
thats cool your a fanboy to linux. but freebsd isn't linux. Lets get back to topic. how do i add comments? is it // or \\? i know in dehacked it was ## lol
User avatar
Graf Zahl
Lead GZDoom+Raze Developer
Lead GZDoom+Raze Developer
Posts: 49252
Joined: Sat Jul 19, 2003 10:19 am
Location: Germany

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by Graf Zahl »

morbidtwatt wrote: but freebsd isn't linux.


Indeed - and therefore it's not a supported OS for ZDoom. I wish you luck getting it to work but this is clearly not the right forum for this thread.
User avatar
Chris
Posts: 2983
Joined: Thu Jul 17, 2003 12:07 am
Graphics Processor: ATI/AMD with Vulkan/Metal Support

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by Chris »

Graf Zahl wrote:Indeed - and therefore it's not a supported OS for ZDoom. I wish you luck getting it to work but this is clearly not the right forum for this thread.
Though I hope you would at least consider some of the needed changes? Those being...
In tools/zipdir/zipdir.c, add:

Code: Select all

#ifndef PATH_MAX
#define PATH_MAX 4096
#endif
In i_net.cpp, add:

Code: Select all

#ifndef IPPORT_USERRESERVED
#define IPPORT_USERRESERVED 5000
#endif
Changing the malloc.h includes to stdlib.h, and removing the unneeded fmod.h include from i_musicinterns.h. Could probably also change the __va_copy in v_draw.cpp to the C99-compatible va_copy (it's not used in MSVC, so it's lack of C99 isn't a problem).
src/sound/music_midi_timidity.cpp also apparently needs

Code: Select all

#include <signal.h>
for non-Win32.

These changes aren't BSD-specific, but are more for cleaning away older-styled code (malloc.h is deprecated, fmod.h shouldn't be included in non-fmod code, __va_copy is an internal function/replaced by va_copy in C99, kill() needs signal.h).
User avatar
Rachael
Posts: 13968
Joined: Tue Jan 13, 2004 1:31 pm
Preferred Pronouns: She/Her
Contact:

Re: zdoom2.3.1 is broken on freebsd7.1 running on wine-1.1.18,1

Post by Rachael »

morbidtwatt wrote:thats cool your a fanboy to linux.
I hardly ever use Linux anymore, so I'm not a "fanboy". It's nice to see you're a "fanboy" of one of the world's least compatible and supported operating systems, though. It's like buying a mac before they switched to Intel processors. Heck, Mac OS X these days has a lot more support and compatibility than FreeBSD does - and the irony here is, they're both Unix-based! Thing is, though, unlike the Macs of their time, you actually have the ability to switch operating systems.
morbidtwatt wrote:but freebsd isn't linux.
If that distinction wasn't clear in my own post, then you clearly did not comprehend what I typed. But then again, if you can't deduce anything from my name, it's no surprise you couldn't figure out what I said.

Like Graf said though... good luck. Your rude response was completely uncalled for, but good luck anyway...
Post Reply

Return to “Closed Bugs [GZDoom]”