Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 279 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  1866   Tue Jul 4 07:04:19 2006 Reply Steve Jonessteve.jones@freescale.comQuestionMac OSX2.6.1Re: Canīt run command "make" in OSX

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?
  1867   Tue Jul 4 08:46:15 2006 Reply Mats McLundmats.lund@nassjotryckeriet.seQuestionMac OSX2.6.1Re: Canīt run command "make" in OSX

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" Frown

You maybe have some other trick to start elogd?

Best regards and thanks for all help.

Mats McLund
  1868   Tue Jul 4 08:52:47 2006 Reply Gerald Ebberinkg.h.p.ebberink@nclr.nlQuestionMac OSX2.6.1Re: Canīt run command "make" in OSX

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" Frown

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.
  1869   Tue Jul 4 13:07:53 2006 Reply Mats McLundmats.lund@nassjotryckeriet.seQuestionMac OSX2.6.1Re: Canīt run command "make" in OSX

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" Frown

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..... Frown

When I run ./elogd -p 8080 I get "Bus error" message.

Best regards

Mats McLund
  1872   Mon Jul 10 11:14:12 2006 Reply Gerald Ebberinkg.h.p.ebberink@nclr.nlQuestionMac OSX2.6.1Re: Canīt run command "make" in OSX

Mats McLund wrote:


Hello Gerald.

Tank you for your help!

But..... Frown

When I run ./elogd -p 8080 I get "Bus error" message.

Best regards

Mats McLund


Hello Mats,

This sounds like something I have not encountered, so I think you'll need to wait for Mr. Ritt to solve this.
  1873   Mon Jul 10 11:15:25 2006 Reply Stefan Rittstefan.ritt@psi.chQuestionMac OSX2.6.1Re: Canīt run command "make" in OSX

Gerald Ebberink wrote:
This sounds like something I have not encountered, so I think you'll need to wait for Mr. Ritt to solve this.


No, I can't solve this becaue I have no MAC.

Sorry,

Stefan
  65677   Mon Dec 17 02:17:20 2007 Question Val Schmidtvschmidt@ccom.unh.eduQuestionMac OSX2.6.1Moving a logbook from one installation to another

I've attempted to move a logbook from an old elog installation to a new one on another system. The version of elog is the same (2.6.1) in both. Both systems have the same name and the logbooks are and installation are going in the same place. So all paths are identical. Also, for the new installation, I've simply recompiled the same sources used to install the original one. The only difference is an upgrade in the OS.
 
I've rsync'd the directory and contents from the old installation to the logbooks/ directory for the new one. I then over-wrote the standard config file with the new one. I then started elogd in the new place.
 
What I find is 
 
a) The default entry from the demo logbook is inserted into my logbook. This I can live with but it was unexpected.
b) The dates for all my entries as shown in my browser have years starting in 1946, rather than 2006. This is particularly odd since all of the actual log files have the correct dates. 
c) The numbering of entries has been reset to 1.
 
 
Can anyone explain what I've done to mucky this up and how to fix it?
 
Thanks in advance,
 
Val
 

  65678   Mon Dec 17 08:13:22 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionMac OSX2.6.1Re: Moving a logbook from one installation to another

Val Schmidt wrote:

I've attempted to move a logbook from an old elog installation to a new one on another system. The version of elog is the same (2.6.1) in both. Both systems have the same name and the logbooks are and installation are going in the same place. So all paths are identical. Also, for the new installation, I've simply recompiled the same sources used to install the original one. The only difference is an upgrade in the OS.
 
I've rsync'd the directory and contents from the old installation to the logbooks/ directory for the new one. I then over-wrote the standard config file with the new one. I then started elogd in the new place.
 
What I find is 
 
a) The default entry from the demo logbook is inserted into my logbook. This I can live with but it was unexpected.
b) The dates for all my entries as shown in my browser have years starting in 1946, rather than 2006. This is particularly odd since all of the actual log files have the correct dates. 
c) The numbering of entries has been reset to 1.
 

That sounds really strange. The only thing I can think of is that the demo entry conflicted with your other entries and two of them have the same entry ID. The entry ID is a unique key which identifies each entry. If you look into the raw logbook file 011108a.log with a text editor, you will see them as

$@Mid@$: 1
Date: Thu Nov 08 18:37:57 2001
Author: Stefan Ritt
Type: Routine
Category: General
Subject: Welcome
Attachment:
Encoding: ELCode
========================================
[B]Congratulations for installing ELOG sucessfully!
[/B]

This is a demo entry to ensure the elogd server is working correctly.
Click [I]"New"[/I] to add new pages and [I]"Delete"[/I] to delete this page.

so in this case the ID is 1. When you rsync'ed your entries into the demo logbook directory, you probably got two entries with the ID 1, which screws up elogd. Try to delete the file 011108a.log before you do the rsync. If you start elogd interactively with the "-v" flag, you will see some debugging output which can you help identify some problems:

[ritt@pc5082 ~/elog]$ ./elogd -v
elogd 2.7.0 built Dec 13 2007, 08:05:12 revision 1977
Config file  : /afs/psi.ch/user/r/ritt/elog/elogd.cfg
Resource dir : /afs/psi.ch/user/r/ritt/elog
Logbook dir  : /afs/psi.ch/user/r/ritt/elog/logbooks/
Indexing logbook "demo" in "logbooks/demo/" ...

Config [demo],                           MD5=F2E39262960C779517FEE576C17B1ED0

Entries:
  ID   1, 011108a.log, ofs     0, thead, MD5=81D89C3C94C6626BB7FF191026040E83
After sort:
  ID   1, 011108a.log, ofs     0
ok
Server listening on port 8080 ...

 

ELOG V3.1.5-3fb85fa6