> From: Jared Rypka-Hauer [mailto:[EMAIL PROTECTED]
> My problem was the wording of the error message I was getting. I
> interpreted
> "gcc: file not found" to mean that gcc was reporting a missing file...
> which
> I began to search for. Spent a whole day on getting this working. Pete,
> once
> I installed gcc (and realized that the script itself was telling me that
> the
> error was reporting gcc AS THE MISSING FILE), it worked perfectly.
>
Since you seemed to have accidentally misquoted the error twice here, I'd
just like to point out that the error message was actually "gcc: command not
found", rather than file not found. To me this seems a little more obvious.
I know from experience its very easy to misread error messages. Even for
plain jane Linux installs its recommended to have gcc installed for
situations where software must be built from source on the local system
rather than from RPM or other package.
> Incidentally, MM provides the exact command line and the names of the
> variables in order to create a simple shell script to do the compiling.
> Since I use Homesite+ via Samba to do all of my shell script and perl
> editing (it even color codes it all :D ) I just copied/pasted from the web
> page into the shell script and saved it to the wsconfig/1 directory on the
> SuSE box, flipped the KVM over to the Linux box and ran it and BOOM. In
> fact, I used Winzip and Samba to unzip the module sources into the dir on
> the SuSE box.
>
I once created a shell script based on those instructions in order to
facilitate backing up any existing connector and recompiling a new one with
-DEAPI, which was a minor issue when using Apache 1.3.x, found here:
http://www.talkingtree.com/blog/index.cfm?data="">
> All done. And it works. Quite nicely!
> Spread the word, it WILL run on SuSE... just needs a bit o'tinkering.
ColdFusion MX is already supported on Suse 7 and 8. ColdFusion MX is not
supported on Suse 9.
-Steven Erat
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
