Canīt run command "make" in OSX, posted by Mats McLund on Fri Jun 30 13:35:03 2006
|
Hello.
I think to test Elog in Mac G5 with OSX 10.4.6.
In the manual is following installationtext:
"Installation from the tarball:
Download the latest elog-x.x.x.tar.gz package.
Expand the compressed TAR file with tar -xzvf elog-x.x.x.tar.gz. This creates a subdirectory elog-x.x.x where x.x.x is the version number. In that directory execute make, which creates the executables elogd, elog and elconv."
The problem is when i try to run the command "make" in ~/elog-2.6.1 subdirectory. I get following message:
-bash: make: command not found
Now, Im not an "UNIX-hacker" so I will be glad if anyone maybe can help me?
Best regardīs
Mats McLund |
Re: Canīt run command "make" in OSX, posted by Mats McLund on Tue Jul 4 08:46:15 2006
|
| Steve Jones wrote: |
| Mats McLund wrote: | Hello.
I think to test Elog in Mac G5 with OSX 10.4.6.
In the manual is following installationtext:
"Installation from the tarball:
Download the latest elog-x.x.x.tar.gz package.
Expand the compressed TAR file with tar -xzvf elog-x.x.x.tar.gz. This creates a subdirectory elog-x.x.x where x.x.x is the version number. In that directory execute make, which creates the executables elogd, elog and elconv."
The problem is when i try to run the command "make" in ~/elog-2.6.1 subdirectory. I get following message:
-bash: make: command not found
Now, Im not an "UNIX-hacker" so I will be glad if anyone maybe can help me?
Best regardīs
Mats McLund |
| Quote: | | Typically one would install the Gnu compiler series and with that come 'gmake'. Barring that, and not knowing anything about OSx, if OSx comes with its own compiler series then make might be somewhere on the system but not in your path. Go to http://gcc.gnu.org/ and see if you an find a pre-built version of gcc -- all I found mentioned "darwin". Perhaps Apple has something in the way of a development colleciton? |
|
Hi Steve.
I have now found a compiler on Apples Developer Tools --- they came as a CD from Apple with my Mac G5.
Great thanks to mr Thomas R. Vilberg for that tips!
I have now the "make"-commands to work as you see.
McLunds-G5:~/elog-2.6.1 admin$ ls -al
total 3984
drwxr-xr-x 21 1093 110 714 Jun 30 14:55 .
drwxrwxr-x 45 admin staff 1530 Jun 30 14:52 ..
-rwxr-xr-x 1 1093 110 17982 Oct 7 2005 COPYING
-rw-r--r-- 1 1093 110 3702 Mar 6 20:32 Makefile
-rw-r--r-- 1 1093 110 327 Oct 7 2005 README
drwxr-xr-x 11 1093 110 374 Apr 1 15:29 contrib
drwxr-xr-x 19 1093 110 646 Apr 1 15:29 doc
-rwxr-xr-x 1 root 110 35020 Jun 30 14:55 elconv
-rwxr-xr-x 1 root 110 43152 Jun 30 14:53 elog
-rwxr-xr-x 1 root 110 1806608 Jun 30 14:54 elogd
-rwxr-xr-x 1 1093 110 412 Mar 28 17:19 elogd.cfg
-rwxr-xr-x 1 1093 110 1256 Jan 19 09:19 elogd.init_template
drwxr-xr-x 3 1093 110 102 Apr 1 15:29 logbooks
drwxr-xr-x 5 1093 110 170 Apr 1 15:29 man
-rw-r--r-- 1 root 110 56868 Jun 30 14:53 mxml.o
-rw-r--r-- 1 root 110 46844 Jun 30 14:53 regex.o
drwxr-xr-x 31 1093 110 1054 Apr 1 15:29 resources
drwxr-xr-x 3 1093 110 102 Apr 1 15:29 scripts
drwxr-xr-x 8 1093 110 272 Apr 1 15:29 src
-rw-r--r-- 1 root 110 1672 Jun 30 14:53 strlcpy.o
drwxr-xr-x 3 1093 110 102 Apr 1 15:29 themes
But....
When I try to run "elogd -p 8080" or just "elogd" after installation I get message "-bash: elogd: command not found" 
You maybe have some other trick to start elogd?
Best regards and thanks for all help.
Mats McLund |
|
Re: Canīt run command "make" in OSX, posted by Mats McLund on Tue Jul 4 13:07:53 2006
|
| Gerald Ebberink wrote: |
| Mats McLund wrote: |
But....
When I try to run "elogd -p 8080" or just "elogd" after installation I get message "-bash: elogd: command not found"
You maybe have some other trick to start elogd?
Best regards and thanks for all help.
Mats McLund |
Mats,
What you might want to try is the following (it works for linux which has bash)
in the elog directory run "./elogd -p 8080" you see the dot slash in there that means it should run the file in the local directory.
of that works you could try run "make install" in which case it will be installed in the directory where it can be found as a command.
these are just my 2 cents. |
Hello Gerald.
Tank you for your help!
But.....
When I run ./elogd -p 8080 I get "Bus error" message.
Best regards
Mats McLund |
|
Problem with special character "č", posted by Matej Sedej on Fri Feb 16 09:18:56 2018
|
Hello!
First of all, thank you for this great piece of software! For now it seems to perfectly cover our need to log very basic events, there was a setting for everything we wanted to set.
However we have one problem and that is the saving of the letter "č" (Slovenian) into the log files. That is unicode character U+010C and U+010CD https://unicode-table.com/en/010C/. When writing to the log file it is replaced with "Č" and "č". Is there a known fix for this?
Thank you and best regards,
Matej |
|
Re: Problem with special character "č", posted by Matej Sedej on Fri Feb 16 09:36:18 2018
|
I see the same problem exists on this board as well. Actuall it appears only the attribute fields are affected. The č character was incorrectly written to the log file from the subject field above, but correctly from the body text below.
| Matej Sedej wrote: |
|
Hello!
First of all, thank you for this great piece of software! For now it seems to perfectly cover our need to log very basic events, there was a setting for everything we wanted to set.
However we have one problem and that is the saving of the letter "č" (Slovenian) into the log files. That is unicode character U+010C and U+010CD https://unicode-table.com/en/010C/. When writing to the log file it is replaced with "Č" and "č". Is there a known fix for this?
Thank you and best regards,
Matej
|
|
|
Re: Problem with special character "č", posted by Matej Sedej on Tue Mar 6 15:29:38 2018
|
Hello Stefan,
thank you for the reply. The explanation does not solve my problem though.
1) Could you elaborate, why the body text field CORRECTLY writes the character while the attribute fields write and display the HTML code?
2) If I understand you correctly the problem also contradicts your statement: "When an existing elog entry gets shown by the browser, the code is translated back to the character." and is visible in this very post. The subject field writes and displays it incorrectly, while the body text writes and displays it perfectly OK. See: Č č ?
3) We do not use any scripts. If we were to use a script to replace the HTML code with the actual character, the attribute fields would still display È instead of Č. Also, I have no idea how to write such a script. :)
Thanks,
Matej
| Stefan Ritt wrote: |
|
Actually unicode characters are converted by your browser into HTML code (such as Č) where 268 decimal = 10C hex. elog just writes to file what it gets from the browser. When an existing elog entry gets shown by the browser, the code is translated back to the character. Why do you care what is written to the log file? If you use scripts or so to parse your log files, you have to adapt them to correctly decode HTML encoded characters. This is necessary since log files are ASCII and thus encode one charecter in one byte. Your Slovenian characters require two bytes in unicode, so some kind of "special" encoding is necessary.
Stefan
|
|
|
Re: Problem with special character "č", posted by Matej Sedej on Tue Mar 6 16:09:05 2018
|
This tag does not change the behaviour, but I have noticed that I only have the problem in Chrome and Firefox but not in Internet explorer.
Matej
| Stefan Ritt wrote: |
|
In the attribe filed, HTML code is not allowed for security reasons. If you want to bypass this (on your own risk), put
allow html = 1
into your config file.
Stefan
|
|
|
Re: Problem with special character "č", posted by Matej Sedej on Wed Mar 7 15:15:27 2018
|
So this is the result in the log file:
Opis: Test č Č
Attachment:
Encoding: HTML
========================================
<p>Test č Č body</p>
This is displayed as
Opis: Test č Č
Test Ä Ä body
| Stefan Ritt wrote: |
|
In the attribe filed, HTML code is not allowed for security reasons. If you want to bypass this (on your own risk), put
allow html = 1
into your config file.
Stefan
| Matej Sedej wrote: |
|
Hello Stefan,
thank you for the reply. The explanation does not solve my problem though.
1) Could you elaborate, why the body text field CORRECTLY writes the character while the attribute fields write and display the HTML code?
2) If I understand you correctly the problem also contradicts your statement: "When an existing elog entry gets shown by the browser, the code is translated back to the character." and is visible in this very post. The subject field writes and displays it incorrectly, while the body text writes and displays it perfectly OK. See: Ä Ä ?
3) We do not use any scripts. If we were to use a script to replace the HTML code with the actual character, the attribute fields would still display È instead of Ä. Also, I have no idea how to write such a script. :)
Thanks,
Matej
| Stefan Ritt wrote: |
|
Actually unicode characters are converted by your browser into HTML code (such as Č) where 268 decimal = 10C hex. elog just writes to file what it gets from the browser. When an existing elog entry gets shown by the browser, the code is translated back to the character. Why do you care what is written to the log file? If you use scripts or so to parse your log files, you have to adapt them to correctly decode HTML encoded characters. This is necessary since log files are ASCII and thus encode one charecter in one byte. Your Slovenian characters require two bytes in unicode, so some kind of "special" encoding is necessary.
Stefan
|
|
|
|