Author Topic: Have questions about porting software to eCS?  (Read 11633 times)

Paul Smedley

  • Sr. Member
  • ****
  • Thank You
  • -Given: 11
  • -Receive: 46
  • Posts: 353
    • View Profile
Re: Have questions about porting software to eCS?
« Reply #15 on: December 29, 2012, 08:53:09 pm »
Quote
Fairly trivial.

For you maybe.  :)

Anyway, now I need to find the time to figure out what you just said, and get this thing to build.

Thanks...

OK, diff format is pretty simple:
diff -ur wget-1.14-o/lib/spawn.in.h wget-1.14/lib/spawn.in.h <== the source files that are being looked at for differences
-#if !(defined __GLIBC__ && !defined __UCLIBC__)     <== the source line that is being taken out (-)
+#if !(defined __GLIBC__ && !defined __UCLIBC__) && !defined __KLIBC__ <== the source line that is replacing the line being taken out (+)

What is the error you are getting when trying to compile wget?

Doug Bissett

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 38
  • Posts: 925
    • View Profile
Re: Have questions about porting software to eCS?
« Reply #16 on: December 31, 2012, 05:45:04 am »
Thanks to Paul, I updated to his latest build environment, and applied the DIFF to the WGET 1.14 source (not sure that I did it right, but it works), and now I can build WGET 1.11.1 and WGET 1.14.  :-*

Unfortunately, I broke building PMMail when I did the update. I obviously deleted something that was added to something that got replaced.  :(

Oh well, you win some, and you lose some. Now, to sort out the PMMail build problem.

Andi B.

  • Sr. Member
  • ****
  • Thank You
  • -Given: 1
  • -Receive: 12
  • Posts: 311
    • View Profile
Re: Have questions about porting software to eCS?
« Reply #17 on: January 01, 2013, 02:40:17 pm »
One issue for me is that building from 4os2 prompt does not work/gives different problems as with standard cmd. F.i. 4os2 -
Code: [Select]
{0}[u:\dev\dhcp-3.1-esv-r3] ash ./configure
System Type: os2
make[1]: Entering directory `U:/dev/dhcp-3.1-esv-r3/work.os2'
Making links in common
make[2]: Entering directory `U:/dev/dhcp-3.1-esv-r3/common'
make[2]: *** No rule to make target `links'.  Stop.
make[2]: Leaving directory `U:/dev/dhcp-3.1-esv-r3/common'
make[1]: *** [links] Error 1
make[1]: Leaving directory `U:/dev/dhcp-3.1-esv-r3/work.os2'
make: *** [links] Error 2

while cmd.exe gaves -
Code: [Select]
[U:\dev\dhcp-3.1-esv-r3]ash ./configure
System Type: os2
make[1]: Entering directory `U:/dev/dhcp-3.1-esv-r3/work.os2'
Making links in common
make[2]: Entering directory `U:/dev/dhcp-3.1-esv-r3/work.os2/common'
make[2]: Leaving directory `U:/dev/dhcp-3.1-esv-r3/work.os2/common'
Making links in minires
make[2]: Entering directory `U:/dev/dhcp-3.1-esv-r3/work.os2/minires'
.....

I do not see what problem is with 4os2 in "make[2]: *** No rule to make target `links'.  Stop." If someone else like me ever uses 4os2 you like to test with cmd.exe instead. On the other hand I really want to know why it does not work/work different with 4os2. Any clues?

-------------------------------------------
20130103 EDIT:
Solved above problem. It was the line '@if not defined CDPATH set CDPATH=..;..\..;' in 4start.cmd. Changed to '@if not defined CDPATH set CDPATH=.;..;..\..;' solves the problem (.; in front). As this is also in the sample 4start.cmd.sample I think I better post it here for future reference. No clue who ever have added this to 4start.cmd....
« Last Edit: January 03, 2013, 06:16:18 pm by Andi B. »

TeLLie

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 6
  • Posts: 47
    • View Profile
Re: Have questions about porting software to eCS?
« Reply #18 on: January 01, 2013, 07:36:31 pm »
Hi Andy,

First to all the Best wishes for 2013 :)

You have in 4os2.ini this:
UnixPaths = Yes

I often use 4os2 instead of the plain cmd

Andi B.

  • Sr. Member
  • ****
  • Thank You
  • -Given: 1
  • -Receive: 12
  • Posts: 311
    • View Profile
Re: Have questions about porting software to eCS?
« Reply #19 on: January 01, 2013, 11:14:43 pm »
Elbert, I think it was me who told you that, wasn't it? ;)

Since this day I've it in my 4os2.ini too. But unfortunately dhcp behaves still different with 4os2. Maybe the ` in front of `links' is the problem...

TeLLie

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 6
  • Posts: 47
    • View Profile
Re: Have questions about porting software to eCS?
« Reply #20 on: January 01, 2013, 11:51:10 pm »
Hihi,

Now you mention it , yes thats true :P
But since i have set that, i don't see problems with 4os2


Andi B.

  • Sr. Member
  • ****
  • Thank You
  • -Given: 1
  • -Receive: 12
  • Posts: 311
    • View Profile
Re: Have questions about porting software to eCS?
« Reply #21 on: January 02, 2013, 12:15:42 am »
Paul, did you made the dhconf.cmd in dhcp-3.1-esv-r3?

Paul Smedley

  • Sr. Member
  • ****
  • Thank You
  • -Given: 11
  • -Receive: 46
  • Posts: 353
    • View Profile
Re: Have questions about porting software to eCS?
« Reply #22 on: January 02, 2013, 02:53:31 am »
Paul, did you made the dhconf.cmd in dhcp-3.1-esv-r3?

Pretty sure Allan Holm is (ir)responsible or that :)

Doug Bissett

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 38
  • Posts: 925
    • View Profile
Re: Have questions about porting software to eCS?
« Reply #23 on: January 05, 2013, 04:11:55 am »
Thanks to Paul, I updated to his latest build environment, and applied the DIFF to the WGET 1.14 source (not sure that I did it right, but it works), and now I can build WGET 1.11.1 and WGET 1.14.  :-*

Unfortunately, I broke building PMMail when I did the update. I obviously deleted something that was added to something that got replaced.  :(

Oh well, you win some, and you lose some. Now, to sort out the PMMail build problem.

Well, it took a lot of time, but I got PMMail to build, and I can build WGET 1.14, using the DIFF described earlier by Paul.

I was going to restart a thread about building WGET 1.14, but it seems that all you need is Paul's latest build package, download the WGET package of choice from:

http://ftp.gnu.org/gnu/wget/

(I took the 1.14 tar.gz package), unzip it, and follow Paul's instructions.

Once you get that far, you know that the build environment is basically working, so you can then progress to other projects. It is probably best to pick something relatively simple, that has been done before, so it will be easier to get help when something doesn't go as expected, before going on to building more advanced things (like VirtualBox).   ;D

Have fun... ;)