From schuan2 at gmail.com  Mon Aug  8 17:40:09 2005
From: schuan2 at gmail.com (Shih-Che Huang)
Date: Mon, 8 Aug 2005 20:40:09 -0400
Subject: [cAos] Intel Fortran Compiler 9.0 installation Problem!!
Message-ID: <af13f5190508081740316907d1@mail.gmail.com>

Hi,
I am running cAos-2 on my AMD Athlon  64 Processor 3200+ PC.
When I insalled Intel Fortran Compiler 9.0 on it, it showed following message.
I maked sure my license file was in the correct location.

I have a same PC running CentOS-4.1 and I can install Intel Fortran
Compiler 9.0 without any license problem. These files were copied from
cAos-2 PC. Those are the same files.

I am wondering if I didn't install some packages when I installed cAos-2.
Any suggestions?

Thanks,

Shih-Che Huang


Press Enter key to continue...

======================================================================
"Intel(R) Fortran Compiler 9.0 for Linux*" Serial Number Required

Please enter your serial number for this Product or select a different option.
Your Serial Number is in XXXX-XXXXXXXX format.

        1. Where do I find my Serial Number?
        2. Intel Privacy Policy
        x. Exit.

Please type your selection or Serial Number  :   NJ24-479Z8FJX

Setup may attempt to connect to the Intel(R) Registration Center to
validate your Serial Number.
This may take several minutes depending on your network.  Please wait...
You may press Ctrl+C to cancel.

Checking RPM version ...

Checking Dependencies ...
Checking Kernel and glibc dependencies ...


A valid FLEXlm license is required to install this product.
No valid license was found in $INTEL_LICENSE_FILE (/opt/l_fc_p_9.0.021:/opt/inte
l/licenses:/opt/intel/licenses:/licenses).

Where is a valid FLEXlm license for this product?
Enter path to directory or file, or port at host for counted licenses, or just pres
s 'Enter' to exit   :


-- 
Shih-Che Huang


From kulick at gmail.com  Wed Aug 10 08:31:29 2005
From: kulick at gmail.com (Matt Kulick)
Date: Wed, 10 Aug 2005 11:31:29 -0400
Subject: [cAos] cAos-2 vnc and lam-mpi (compiled w/ fortran support?)
Message-ID: <650e5e40050810083120aeb00d@mail.gmail.com>

I was wondering if the cAos-2 community could get a build of some 
vnc-server/vnc-client (server especially) for the x86_64 platform, or a 
.src.rpm. I've noticed there are no vnc packages on the cAos repositories, 
and building from the latest realvnc source throws some errors when 
compiling Xvnc. I'm not an expert, but I think either (real)vnc or tightVNC 
would work great for this! I also tried rebuilding the FC4 x86_64 vnc 
package, but after installing it the Xvnc server had some path resolution 
problems. I'd love to hear about any of your experiences getting a vnc 
server running under cAos-2...

Also, one of my users tried compiling a lam-mpi / fortran program under my 
cAos-2 install (with all package groups selected), and he got the following 
error message:

<code>
make compile 
/lib/cpp -DTLB=128 -DUNROLL_I=4 -DUNROLL_J=4 -DUNROLL_K=4 -P -traditional 
advx1.F | tr -s "" "\012" > advx1.f 
/usr/bin/hf77 -c -g -O3 -D_REENTRANT -I/usr/include -static advx1.f 
----------------------------------------------------------------------------- 
Sorry, LAM/MPI was not compiled with FORTRAN support. 

You will need to re-compile LAM and be sure that either ./configure 
finds a FORTRAN compiler, or that you explicitly specify a FORTRAN 
compiler with the --with-fc switch to ./configure. 
----------------------------------------------------------------------------- 
make: *** [advx1.o] Error 1
 
</code>
 
I downloaded the source tarball of the latest lam-mpi, 7.1.1, and I ran 
./configure, where it successfully detected and configured fortran support. 
Would it be an easy fix to update the lam-mpi binary/src (for x86_64, or all 
platforms) so that I can use the cAos-2 repo to install w/ fortran support?
 

Basically, I'd love to hear your comments and experiences on vnc and lam-mpi 
w/ fortran under cAos-2. I'd also really like to know if we, as a community, 
could get:
 
1. a vnc package
2. a lam-mpi compiled w/ fortran support, by default (since the everything 
install already includes g77, i think)
 
On a separate note, which Fedora Core / Redhat distribution is cAos-2 most 
similar to?
 

-matt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.infiscale.org/pipermail/caos/attachments/20050810/35be78e4/attachment.html 

From gmk at runlevelzero.net  Thu Aug 11 06:39:07 2005
From: gmk at runlevelzero.net (Greg M. Kurtzer)
Date: Thu, 11 Aug 2005 06:39:07 -0700
Subject: [cAos] cAos-2 vnc and lam-mpi (compiled w/ fortran support?)
In-Reply-To: <650e5e40050810083120aeb00d@mail.gmail.com>
References: <650e5e40050810083120aeb00d@mail.gmail.com>
Message-ID: <20050811133907.GB27294@titan.runlevelzero.net>

On Wed, Aug 10, 2005 at 11:31:29AM -0400, Matt Kulick wrote:
> I was wondering if the cAos-2 community could get a build of some 
> vnc-server/vnc-client (server especially) for the x86_64 platform, or a 
> .src.rpm. I've noticed there are no vnc packages on the cAos repositories, 
> and building from the latest realvnc source throws some errors when 
> compiling Xvnc. I'm not an expert, but I think either (real)vnc or tightVNC 
> would work great for this! I also tried rebuilding the FC4 x86_64 vnc 
> package, but after installing it the Xvnc server had some path resolution 
> problems. I'd love to hear about any of your experiences getting a vnc 
> server running under cAos-2...

Sorry, this I am not familiar with.

> Also, one of my users tried compiling a lam-mpi / fortran program under my 
> cAos-2 install (with all package groups selected), and he got the following 
> error message:
> 
> <code>
> make compile 
> /lib/cpp -DTLB=128 -DUNROLL_I=4 -DUNROLL_J=4 -DUNROLL_K=4 -P -traditional 
> advx1.F | tr -s "" "\012" > advx1.f 
> /usr/bin/hf77 -c -g -O3 -D_REENTRANT -I/usr/include -static advx1.f 
> ----------------------------------------------------------------------------- 
> Sorry, LAM/MPI was not compiled with FORTRAN support. 
> 
> You will need to re-compile LAM and be sure that either ./configure 
> finds a FORTRAN compiler, or that you explicitly specify a FORTRAN 
> compiler with the --with-fc switch to ./configure. 
> ----------------------------------------------------------------------------- 
> make: *** [advx1.o] Error 1
>  
> </code>

The cAos2 LAM is not compiled with Fortran support (as you noticed) but
it still installs a non functioning mpif77 and links hf77 back to mpif77.

What fortran compiler are you using?

> I downloaded the source tarball of the latest lam-mpi, 7.1.1, and I ran 
> ./configure, where it successfully detected and configured fortran support. 
> Would it be an easy fix to update the lam-mpi binary/src (for x86_64, or all 
> platforms) so that I can use the cAos-2 repo to install w/ fortran support?

Yes. Please make a feature request at http://bugs.caosity.org

The reason that I didn't do this before is because Fortran libraries are
not portable between different compiler versions and I didn't think many
people used g77. Easier to debug a fortran compile error with the above
output, rather then library portability issues. But I apparently
assumed that people weren't using g77 which was apparently inaccurate.

> Basically, I'd love to hear your comments and experiences on vnc and lam-mpi 
> w/ fortran under cAos-2. I'd also really like to know if we, as a community, 
> could get:
>  
> 1. a vnc package

I tried a quick build of vnc from fedora core 4, and it errored out at
the end with a missing file (Xvnc). I really am not familiar with vnc
and didn't have time to debug. If you can get a version to compile,
perhaps we can grant you a CVS account so you can maintain it.

> 2. a lam-mpi compiled w/ fortran support, by default (since the everything 
> install already includes g77, i think)

Now, this I can help with. :)

> On a separate note, which Fedora Core / Redhat distribution is cAos-2 most 
> similar to?

Hard to answer this. If you are looking for binary compatibility you
are probably safe with Fedora 3, but as I don't use it, I can't tell for
sure.

Best of luck, and don't forget the bug report! :)
-- 
Greg M. Kurtzer
http://runlevelzero.net/
http://caosity.org/
http://warewulf-cluster.org/

Do not look anywhere for truth, for all that is needed is to refrain from
allowing concepts to arise.


From kulick at gmail.com  Fri Aug 12 09:46:18 2005
From: kulick at gmail.com (Matt Kulick)
Date: Fri, 12 Aug 2005 12:46:18 -0400
Subject: [cAos] Re: cAos-2 vnc and lam-mpi (compiled w/ fortran support?)
Message-ID: <650e5e40050812094640332d23@mail.gmail.com>

I have submitted a feature request on
bugs.caosity.org<http://bugs.caosity.org>for the rpm of lam with
fortran compiled in, and I have news regarding vnc.
I am not sure about how well this will work for everyone, but these are the 
steps I took to get vnc working on cAos-2:

# download and rebuild the fedora core 4 vnc rpm
1. download 
ftp://download.fedora.redhat.com/pub/fedora/linux/core/4/SRPMS/vnc-4.1.1-10.src.rpm
2. rpmbuild --rebuild vnc-4.1.1-10.src.rpm (this should write 2 rpms, vnc 
and vnc-server to your /usr/src/caos/RPMS/<arch> directory
3. rpm -ivh vnc-server-4.1.1-10.<arch>.rpm

# copy SecurityPolicy file to where vnc expects it to be (or maybe create a 
link, who knows)
cd /etc/X11R6/lib/X11
mkdir xserver
cp /etc/X11/xserver/SecurityPolicy xserver/SecurityPolicy

...and that should be it!
I also uncommented the two lines at the top of the $HOME/.vnc/xstartup file, 
but that's a personal choice;)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.infiscale.org/pipermail/caos/attachments/20050812/f428f5c3/attachment.html 

From gmk at runlevelzero.net  Fri Aug 12 11:58:01 2005
From: gmk at runlevelzero.net (Greg M. Kurtzer)
Date: Fri, 12 Aug 2005 11:58:01 -0700
Subject: [cAos] Re: cAos-2 vnc and lam-mpi (compiled w/ fortran support?)
In-Reply-To: <650e5e40050812094640332d23@mail.gmail.com>
References: <650e5e40050812094640332d23@mail.gmail.com>
Message-ID: <20050812185801.GB31135@titan.runlevelzero.net>

Can you post the VNC information on the cAos wiki?

   http://wiki.caosity.org

Thanks!

On Fri, Aug 12, 2005 at 12:46:18PM -0400, Matt Kulick wrote:
> I have submitted a feature request on
> bugs.caosity.org<http://bugs.caosity.org>for the rpm of lam with
> fortran compiled in, and I have news regarding vnc.
> I am not sure about how well this will work for everyone, but these are the 
> steps I took to get vnc working on cAos-2:
> 
> # download and rebuild the fedora core 4 vnc rpm
> 1. download 
> ftp://download.fedora.redhat.com/pub/fedora/linux/core/4/SRPMS/vnc-4.1.1-10.src.rpm
> 2. rpmbuild --rebuild vnc-4.1.1-10.src.rpm (this should write 2 rpms, vnc 
> and vnc-server to your /usr/src/caos/RPMS/<arch> directory
> 3. rpm -ivh vnc-server-4.1.1-10.<arch>.rpm
> 
> # copy SecurityPolicy file to where vnc expects it to be (or maybe create a 
> link, who knows)
> cd /etc/X11R6/lib/X11
> mkdir xserver
> cp /etc/X11/xserver/SecurityPolicy xserver/SecurityPolicy
> 
> ...and that should be it!
> I also uncommented the two lines at the top of the $HOME/.vnc/xstartup file, 
> but that's a personal choice;)

> _______________________________________________
> cAos mailing list
> cAos at caosity.org
> http://lists.caosity.org/mailman/listinfo/caos


-- 
Greg M. Kurtzer
http://runlevelzero.net/
http://caosity.org/
http://warewulf-cluster.org/

Do not look anywhere for truth, for all that is needed is to refrain from
allowing concepts to arise.


From gmk at runlevelzero.net  Mon Aug 15 06:59:30 2005
From: gmk at runlevelzero.net (Greg M. Kurtzer)
Date: Mon, 15 Aug 2005 06:59:30 -0700
Subject: [cAos] current repository updates
Message-ID: <20050815135930.GA20794@titan.runlevelzero.net>

#######################################################################
ARCH: SRPMS
   + SRPMS/adns-1.1-5.src.rpm
   + SRPMS/arts-1.4.2-0.caos.src.rpm
   + SRPMS/bash-completion-20050712-1.caos.src.rpm
   + SRPMS/BitchX-1.1-3.caos.src.rpm
   + SRPMS/bitweaver-1.0.1-2.caos.src.rpm
   + SRPMS/clearlooks-engine-0.6.2-0.caos.src.rpm
   + SRPMS/doxygen-1.4.4-1.caos.src.rpm
   + SRPMS/dvdisaster-0.62-1.caos.src.rpm
   + SRPMS/ethereal-0.10.12-1.caos.src.rpm
   + SRPMS/gdk-pixbuf-0.22.0-18.caos.src.rpm
   + SRPMS/glade-2.6.0-4.caos.src.rpm
   + SRPMS/hdup-2.0.9-1.caos.src.rpm
   + SRPMS/hibernate-1.09-1.caos.src.rpm
   + SRPMS/ipmitool-1.8.2-1.src.rpm
   + SRPMS/iptables-1.3.1-4.src.rpm
   + SRPMS/libogg-1.1.2-4.src.rpm
   + SRPMS/perl-Crypt-PasswdMD5-1.3-1.caos.src.rpm
   + SRPMS/perl-Crypt-Salt-0.01-1.caos.src.rpm
   + SRPMS/perl-File-MkTemp-1.0.6-1.caos.src.rpm
   + SRPMS/perl-MIME-Lite-2.117-1.caos.src.rpm
   + SRPMS/perl-Net-Whois-IP-0.50-1.caos.src.rpm
   + SRPMS/perl-Tk-804.027-1.caos.src.rpm
   + SRPMS/rdesktop-1.4.1-1.src.rpm
   + SRPMS/taglib-1.4-0.caos.src.rpm
   + SRPMS/tikiwiki-1.9.0-3.caos.src.rpm
   + SRPMS/tikiwiki-1.9.0-4.caos.src.rpm
   + SRPMS/tre-0.7.2-1.src.rpm
   + SRPMS/vocab-1.33-1.caos.src.rpm
   + SRPMS/xchat-2.4.4-3.src.rpm
   + SRPMS/xjewel-1.6-1.caos.src.rpm

#######################################################################
ARCH: i386
   + i386/adns-1.1-5.i386.rpm
   + i386/adns-devel-1.1-5.i386.rpm
   + i386/adns-progs-1.1-5.i386.rpm
   + i386/arts-1.4.2-0.caos.i386.rpm
   + i386/arts-devel-1.4.2-0.caos.i386.rpm
   + i386/bash-completion-20050712-1.caos.noarch.rpm
   + i386/BitchX-1.1-3.caos.i386.rpm
   + i386/bitweaver-1.0.1-2.caos.noarch.rpm
   + i386/clearlooks-engine-0.6.2-0.caos.i386.rpm
   + i386/doxygen-1.4.4-1.caos.i386.rpm
   + i386/doxygen-doxywizard-1.4.4-1.caos.i386.rpm
   + i386/dvdisaster-0.62-1.caos.i386.rpm
   + i386/ethereal-0.10.12-1.caos.i386.rpm
   + i386/ethereal-gnome-0.10.12-1.caos.i386.rpm
   + i386/gdk-pixbuf-0.22.0-18.caos.i386.rpm
   + i386/gdk-pixbuf-devel-0.22.0-18.caos.i386.rpm
   + i386/glade-2.6.0-4.caos.i386.rpm
   + i386/hdup-2.0.9-1.caos.i386.rpm
   + i386/hibernate-1.09-1.caos.noarch.rpm
   + i386/ipmitool-1.8.2-1.i386.rpm
   + i386/iptables-1.3.1-4.i386.rpm
   + i386/iptables-devel-1.3.1-4.i386.rpm
   + i386/iptables-ipv6-1.3.1-4.i386.rpm
   + i386/libogg-1.1.2-4.i386.rpm
   + i386/libogg-devel-1.1.2-4.i386.rpm
   + i386/perl-Crypt-PasswdMD5-1.3-1.caos.noarch.rpm
   + i386/perl-Crypt-Salt-0.01-1.caos.noarch.rpm
   + i386/perl-File-MkTemp-1.0.6-1.caos.noarch.rpm
   + i386/perl-MIME-Lite-2.117-1.caos.noarch.rpm
   + i386/perl-Net-Whois-IP-0.50-1.caos.noarch.rpm
   + i386/perl-Tk-804.027-1.caos.noarch.rpm
   + i386/rdesktop-1.4.1-1.i386.rpm
   + i386/taglib-1.4-0.caos.i386.rpm
   + i386/taglib-devel-1.4-0.caos.i386.rpm
   + i386/tikiwiki-1.9.0-3.caos.noarch.rpm
   + i386/tikiwiki-1.9.0-4.caos.noarch.rpm
   + i386/tre-0.7.2-1.i386.rpm
   + i386/tre-agrep-0.7.2-1.i386.rpm
   + i386/tre-devel-0.7.2-1.i386.rpm
   + i386/vocab-1.33-1.caos.noarch.rpm
   + i386/xchat-2.4.4-3.i386.rpm
   + i386/xchat-perl-2.4.4-3.i386.rpm
   + i386/xchat-python-2.4.4-3.i386.rpm
   + i386/xchat-tcl-2.4.4-3.i386.rpm
   + i386/xjewel-1.6-1.caos.i386.rpm

#######################################################################
ARCH: x86_64
   + x86_64/adns-1.1-5.x86_64.rpm
   + x86_64/adns-devel-1.1-5.x86_64.rpm
   + x86_64/adns-progs-1.1-5.x86_64.rpm
   + x86_64/arts-1.4.2-0.caos.x86_64.rpm
   + x86_64/arts-devel-1.4.2-0.caos.x86_64.rpm
   + x86_64/bash-completion-20050712-1.caos.noarch.rpm
   + x86_64/bitweaver-1.0.1-2.caos.noarch.rpm
   + x86_64/clearlooks-engine-0.6.2-0.caos.x86_64.rpm
   + x86_64/doxygen-1.4.4-1.caos.x86_64.rpm
   + x86_64/doxygen-doxywizard-1.4.4-1.caos.x86_64.rpm
   + x86_64/dvdisaster-0.62-1.caos.x86_64.rpm
   + x86_64/ethereal-0.10.12-1.caos.x86_64.rpm
   + x86_64/ethereal-gnome-0.10.12-1.caos.x86_64.rpm
   + x86_64/gdk-pixbuf-0.22.0-18.caos.x86_64.rpm
   + x86_64/gdk-pixbuf-devel-0.22.0-18.caos.x86_64.rpm
   + x86_64/glade-2.6.0-4.caos.x86_64.rpm
   + x86_64/hdup-2.0.9-1.caos.x86_64.rpm
   + x86_64/hibernate-1.09-1.caos.noarch.rpm
   + x86_64/ipmitool-1.8.2-1.x86_64.rpm
   + x86_64/iptables-1.3.1-4.x86_64.rpm
   + x86_64/iptables-devel-1.3.1-4.x86_64.rpm
   + x86_64/iptables-ipv6-1.3.1-4.x86_64.rpm
   + x86_64/libogg-1.1.2-4.x86_64.rpm
   + x86_64/libogg-devel-1.1.2-4.x86_64.rpm
   + x86_64/perl-Crypt-PasswdMD5-1.3-1.caos.noarch.rpm
   + x86_64/perl-Crypt-Salt-0.01-1.caos.noarch.rpm
   + x86_64/perl-File-MkTemp-1.0.6-1.caos.noarch.rpm
   + x86_64/perl-MIME-Lite-2.117-1.caos.noarch.rpm
   + x86_64/perl-Net-Whois-IP-0.50-1.caos.noarch.rpm
   + x86_64/rdesktop-1.4.1-1.x86_64.rpm
   + x86_64/taglib-1.4-0.caos.x86_64.rpm
   + x86_64/taglib-devel-1.4-0.caos.x86_64.rpm
   + x86_64/tikiwiki-1.9.0-3.caos.noarch.rpm
   + x86_64/tikiwiki-1.9.0-4.caos.noarch.rpm
   + x86_64/vocab-1.33-1.caos.noarch.rpm
   + x86_64/xchat-2.4.4-3.x86_64.rpm
   + x86_64/xchat-perl-2.4.4-3.x86_64.rpm
   + x86_64/xchat-python-2.4.4-3.x86_64.rpm
   + x86_64/xchat-tcl-2.4.4-3.x86_64.rpm
   + x86_64/xjewel-1.6-1.caos.x86_64.rpm


-- 
Greg M. Kurtzer
http://runlevelzero.net/
http://caosity.org/
http://warewulf-cluster.org/

Do not look anywhere for truth, for all that is needed is to refrain from
allowing concepts to arise.


From gmk at runlevelzero.net  Mon Aug 15 07:00:30 2005
From: gmk at runlevelzero.net (Greg M. Kurtzer)
Date: Mon, 15 Aug 2005 07:00:30 -0700
Subject: [cAos] stable repository updates
Message-ID: <20050815140030.GB20794@titan.runlevelzero.net>

(No package updates, only additions to repository)

   + SRPMS/adns-1.1-5.src.rpm
   + SRPMS/BitchX-1.1-3.caos.src.rpm
   + SRPMS/bitweaver-1.0.1-2.caos.src.rpm
   + SRPMS/ipmitool-1.8.2-1.src.rpm
   + SRPMS/perl-Crypt-PasswdMD5-1.3-1.caos.src.rpm
   + SRPMS/perl-Crypt-Salt-0.01-1.caos.src.rpm
   + SRPMS/perl-File-MkTemp-1.0.6-1.caos.src.rpm
   + SRPMS/perl-MIME-Lite-2.117-1.caos.src.rpm
   + SRPMS/perl-Net-Whois-IP-0.50-1.caos.src.rpm
   + SRPMS/perl-Tk-804.027-1.caos.src.rpm
   + SRPMS/tre-0.7.2-1.src.rpm
   + SRPMS/xjewel-1.6-1.caos.src.rpm
   + i386/adns-1.1-5.i386.rpm
   + i386/adns-devel-1.1-5.i386.rpm
   + i386/adns-progs-1.1-5.i386.rpm
   + i386/BitchX-1.1-3.caos.i386.rpm
   + i386/bitweaver-1.0.1-2.caos.noarch.rpm
   + i386/ipmitool-1.8.2-1.i386.rpm
   + i386/perl-Crypt-PasswdMD5-1.3-1.caos.noarch.rpm
   + i386/perl-Crypt-Salt-0.01-1.caos.noarch.rpm
   + i386/perl-File-MkTemp-1.0.6-1.caos.noarch.rpm
   + i386/perl-MIME-Lite-2.117-1.caos.noarch.rpm
   + i386/perl-Net-Whois-IP-0.50-1.caos.noarch.rpm
   + i386/perl-Tk-804.027-1.caos.noarch.rpm
   + i386/tre-0.7.2-1.i386.rpm
   + i386/tre-agrep-0.7.2-1.i386.rpm
   + i386/tre-devel-0.7.2-1.i386.rpm
   + i386/xjewel-1.6-1.caos.i386.rpm
   + x86_64/adns-1.1-5.x86_64.rpm
   + x86_64/adns-devel-1.1-5.x86_64.rpm
   + x86_64/adns-progs-1.1-5.x86_64.rpm
   + x86_64/bitweaver-1.0.1-2.caos.noarch.rpm
   + x86_64/ipmitool-1.8.2-1.x86_64.rpm
   + x86_64/perl-Crypt-PasswdMD5-1.3-1.caos.noarch.rpm
   + x86_64/perl-Crypt-Salt-0.01-1.caos.noarch.rpm
   + x86_64/perl-File-MkTemp-1.0.6-1.caos.noarch.rpm
   + x86_64/perl-MIME-Lite-2.117-1.caos.noarch.rpm
   + x86_64/perl-Net-Whois-IP-0.50-1.caos.noarch.rpm
   + x86_64/xjewel-1.6-1.caos.x86_64.rpm

-- 
Greg M. Kurtzer
http://runlevelzero.net/
http://caosity.org/
http://warewulf-cluster.org/

Do not look anywhere for truth, for all that is needed is to refrain from
allowing concepts to arise.


From schuan2 at gmail.com  Mon Aug 15 15:38:47 2005
From: schuan2 at gmail.com (Shih-Che Huang)
Date: Mon, 15 Aug 2005 18:38:47 -0400
Subject: [cAos] Re: Intel Fortran Compiler 9.0 installation Problem!!
In-Reply-To: <af13f5190508081740316907d1@mail.gmail.com>
References: <af13f5190508081740316907d1@mail.gmail.com>
Message-ID: <af13f51905081515385912f451@mail.gmail.com>

Hi, 
I think the problem was the develop library such as libgcc_s.so.1,
libstdc++ ,........didn't install in 32 bit directory (/lib).
I am not sure how many library still missing in /lib.
Is any quick way can fully install all necessary library in /lib?

Any suggestion?

Shih-Che  

On 8/8/05, Shih-Che Huang <schuan2 at gmail.com> wrote:
> Hi,
> I am running cAos-2 on my AMD Athlon  64 Processor 3200+ PC.
> When I insalled Intel Fortran Compiler 9.0 on it, it showed following message.
> I maked sure my license file was in the correct location.
> 
> I have a same PC running CentOS-4.1 and I can install Intel Fortran
> Compiler 9.0 without any license problem. These files were copied from
> cAos-2 PC. Those are the same files.
> 
> I am wondering if I didn't install some packages when I installed cAos-2.
> Any suggestions?
> 
> Thanks,
> 
> Shih-Che Huang
> 
> 
> Press Enter key to continue...
> 
> ======================================================================
> "Intel(R) Fortran Compiler 9.0 for Linux*" Serial Number Required
> 
> Please enter your serial number for this Product or select a different option.
> Your Serial Number is in XXXX-XXXXXXXX format.
> 
>         1. Where do I find my Serial Number?
>         2. Intel Privacy Policy
>         x. Exit.
> 
> Please type your selection or Serial Number  :   NJ24-479Z8FJX
> 
> Setup may attempt to connect to the Intel(R) Registration Center to
> validate your Serial Number.
> This may take several minutes depending on your network.  Please wait...
> You may press Ctrl+C to cancel.
> 
> Checking RPM version ...
> 
> Checking Dependencies ...
> Checking Kernel and glibc dependencies ...
> 
> 
> A valid FLEXlm license is required to install this product.
> No valid license was found in $INTEL_LICENSE_FILE (/opt/l_fc_p_9.0.021:/opt/inte
> l/licenses:/opt/intel/licenses:/licenses).
> 
> Where is a valid FLEXlm license for this product?
> Enter path to directory or file, or port at host for counted licenses, or just pres
> s 'Enter' to exit   :
> 
> 
> --
> Shih-Che Huang
> 


-- 
Shih-Che Huang


From gmk at runlevelzero.net  Mon Aug 15 22:39:50 2005
From: gmk at runlevelzero.net (Greg M. Kurtzer)
Date: Mon, 15 Aug 2005 22:39:50 -0700
Subject: [cAos] Re: Intel Fortran Compiler 9.0 installation Problem!!
In-Reply-To: <af13f51905081515385912f451@mail.gmail.com>
References: <af13f5190508081740316907d1@mail.gmail.com>
	<af13f51905081515385912f451@mail.gmail.com>
Message-ID: <20050816053950.GB21977@titan.runlevelzero.net>

Nice catch.

cAos Linux x86_64 doesn't populate the 32 bit lib path by default. To do
this, you can easily add a 32 bit core repo by creating the following
content in /etc/yum.repos.d/caos-2-core32.repo:

   [core32]
   enabled=0
   name=cAos-2 32 bit core system repository
   baseurl=http://mirror.caosity.org/cAos-2/core/i386

And then running:

   # yum --enablerepo core32 install glibc.i386

Any other 32 bit packages you want to install can be done my enabling
the core32 repo, and adding the architecture that you want to install
(i386). Now, there are many packages that this will cause conflicts
with, but most all libraries will be fine. I can make sidekick
automatically create this on x86_64 based systems.

Good luck, and let me know how it goes.

BTW, it would probably be helpful to others to document your findings on
our wiki (http://wiki.caosity.org).

Thanks!




On Mon, Aug 15, 2005 at 06:38:47PM -0400, Shih-Che Huang wrote:
> Hi, 
> I think the problem was the develop library such as libgcc_s.so.1,
> libstdc++ ,........didn't install in 32 bit directory (/lib).
> I am not sure how many library still missing in /lib.
> Is any quick way can fully install all necessary library in /lib?
> 
> Any suggestion?
> 
> Shih-Che  
> 
> On 8/8/05, Shih-Che Huang <schuan2 at gmail.com> wrote:
> > Hi,
> > I am running cAos-2 on my AMD Athlon  64 Processor 3200+ PC.
> > When I insalled Intel Fortran Compiler 9.0 on it, it showed following message.
> > I maked sure my license file was in the correct location.
> > 
> > I have a same PC running CentOS-4.1 and I can install Intel Fortran
> > Compiler 9.0 without any license problem. These files were copied from
> > cAos-2 PC. Those are the same files.
> > 
> > I am wondering if I didn't install some packages when I installed cAos-2.
> > Any suggestions?
> > 
> > Thanks,
> > 
> > Shih-Che Huang
> > 
> > 
> > Press Enter key to continue...
> > 
> > ======================================================================
> > "Intel(R) Fortran Compiler 9.0 for Linux*" Serial Number Required
> > 
> > Please enter your serial number for this Product or select a different option.
> > Your Serial Number is in XXXX-XXXXXXXX format.
> > 
> >         1. Where do I find my Serial Number?
> >         2. Intel Privacy Policy
> >         x. Exit.
> > 
> > Please type your selection or Serial Number  :   NJ24-479Z8FJX
> > 
> > Setup may attempt to connect to the Intel(R) Registration Center to
> > validate your Serial Number.
> > This may take several minutes depending on your network.  Please wait...
> > You may press Ctrl+C to cancel.
> > 
> > Checking RPM version ...
> > 
> > Checking Dependencies ...
> > Checking Kernel and glibc dependencies ...
> > 
> > 
> > A valid FLEXlm license is required to install this product.
> > No valid license was found in $INTEL_LICENSE_FILE (/opt/l_fc_p_9.0.021:/opt/inte
> > l/licenses:/opt/intel/licenses:/licenses).
> > 
> > Where is a valid FLEXlm license for this product?
> > Enter path to directory or file, or port at host for counted licenses, or just pres
> > s 'Enter' to exit   :
> > 
> > 
> > --
> > Shih-Che Huang
> > 
> 
> 
> -- 
> Shih-Che Huang

-- 
Greg M. Kurtzer
http://runlevelzero.net/
http://caosity.org/
http://warewulf-cluster.org/

Do not look anywhere for truth, for all that is needed is to refrain from
allowing concepts to arise.


From gmk at runlevelzero.net  Thu Aug 18 23:31:05 2005
From: gmk at runlevelzero.net (Greg M. Kurtzer)
Date: Thu, 18 Aug 2005 23:31:05 -0700
Subject: [cAos] cAos-2 Repository updates
Message-ID: <20050819063105.GA31323@titan.runlevelzero.net>

Current:
   + SRPMS/abiword-2.2.9-7.caos.src.rpm
   + SRPMS/devhelp-0.9.3-6.caos.src.rpm
   + SRPMS/epiphany-1.4.7-6.caos.src.rpm
   + SRPMS/evolution-1.5.93-5.caos.src.rpm
   + SRPMS/galeon-1.3.18-9.caos.src.rpm
   + SRPMS/gnomebaker-0.4.1-0.caos.src.rpm
   + SRPMS/gstreamer-0.8.10-1.caos.src.rpm
   + SRPMS/gstreamer-ffmpeg-0.8.6-0.caos.src.rpm
   + SRPMS/mozilla-1.7.10-0.caos.src.rpm
   + SRPMS/xmms-1.2.10-10.caos.src.rpm
   - SRPMS/mozilla-1.7.8-0.caos.src.rpm
   - SRPMS/xmms-1.2.10-9.caos.src.rpm

Stable:
   + SRPMS/mozilla-1.7.10-0.caos.src.rpm
   + SRPMS/xmms-1.2.10-10.caos.src.rpm
   - SRPMS/mozilla-1.7.8-0.caos.src.rpm
   - SRPMS/xmms-1.2.10-9.caos.src.rpm

-- 
Greg M. Kurtzer
http://runlevelzero.net/
http://caosity.org/
http://warewulf-cluster.org/

Do not look anywhere for truth, for all that is needed is to refrain from
allowing concepts to arise.


From gmk at runlevelzero.net  Fri Aug 19 12:42:24 2005
From: gmk at runlevelzero.net (Greg M. Kurtzer)
Date: Fri, 19 Aug 2005 12:42:24 -0700
Subject: [cAos] Re: cAos-2 Repository updates
In-Reply-To: <20050819063105.GA31323@titan.runlevelzero.net>
References: <20050819063105.GA31323@titan.runlevelzero.net>
Message-ID: <20050819194224.GA595@titan.runlevelzero.net>

In order to resolve a dependancy issue with packages that were linked
against the older mozilla, the following changes were also done:

Current:
   - SRPMS/devhelp-0.9.3-5.caos.src.rpm
   - SRPMS/epiphany-1.4.7-5.caos.src.rpm
   - SRPMS/galeon-1.3.18-8.caos.src.rpm

Stable:
   + SRPMS/devhelp-0.9.3-6.caos.src.rpm
   + SRPMS/epiphany-1.4.7-6.caos.src.rpm
   + SRPMS/galeon-1.3.18-9.caos.src.rpm
   - SRPMS/devhelp-0.9.3-5.caos.src.rpm
   - SRPMS/epiphany-1.4.7-5.caos.src.rpm
   - SRPMS/galeon-1.3.18-8.caos.src.rpm


On Thu, Aug 18, 2005 at 11:31:05PM -0700, Greg M. Kurtzer wrote:
> Current:
>    + SRPMS/abiword-2.2.9-7.caos.src.rpm
>    + SRPMS/devhelp-0.9.3-6.caos.src.rpm
>    + SRPMS/epiphany-1.4.7-6.caos.src.rpm
>    + SRPMS/evolution-1.5.93-5.caos.src.rpm
>    + SRPMS/galeon-1.3.18-9.caos.src.rpm
>    + SRPMS/gnomebaker-0.4.1-0.caos.src.rpm
>    + SRPMS/gstreamer-0.8.10-1.caos.src.rpm
>    + SRPMS/gstreamer-ffmpeg-0.8.6-0.caos.src.rpm
>    + SRPMS/mozilla-1.7.10-0.caos.src.rpm
>    + SRPMS/xmms-1.2.10-10.caos.src.rpm
>    - SRPMS/mozilla-1.7.8-0.caos.src.rpm
>    - SRPMS/xmms-1.2.10-9.caos.src.rpm
> 
> Stable:
>    + SRPMS/mozilla-1.7.10-0.caos.src.rpm
>    + SRPMS/xmms-1.2.10-10.caos.src.rpm
>    - SRPMS/mozilla-1.7.8-0.caos.src.rpm
>    - SRPMS/xmms-1.2.10-9.caos.src.rpm
> 
> -- 
> Greg M. Kurtzer
> http://runlevelzero.net/
> http://caosity.org/
> http://warewulf-cluster.org/
> 
> Do not look anywhere for truth, for all that is needed is to refrain from
> allowing concepts to arise.

-- 
Greg M. Kurtzer
http://runlevelzero.net/
http://caosity.org/
http://warewulf-cluster.org/

Do not look anywhere for truth, for all that is needed is to refrain from
allowing concepts to arise.


From gmk at runlevelzero.net  Tue Aug 23 13:39:22 2005
From: gmk at runlevelzero.net (Greg M. Kurtzer)
Date: Tue, 23 Aug 2005 13:39:22 -0700
Subject: [cAos] cAos-2 Repository updates
Message-ID: <20050823203922.GA1184@titan.runlevelzero.net>

Current:
   + SRPMS/gaim-1.5.0-1.caos.src.rpm
   + SRPMS/gdb-6.3.0.0-2.caos.src.rpm
   + SRPMS/gnomebaker-0.4.2-0.caos.src.rpm
   + SRPMS/mediawiki-1.4.7-1.caos.src.rpm
   + SRPMS/nut-2.0.1-3.caos.src.rpm
   + SRPMS/octave-2.1.71-9.caos.src.rpm
   - SRPMS/gdb-5.2-4.caos.src.rpm

Stable:
   + SRPMS/gdb-6.3.0.0-2.caos.src.rpm
   + SRPMS/octave-2.1.71-9.caos.src.rpm
   - SRPMS/gdb-5.2-4.caos.src.rpm

-- 
Greg M. Kurtzer
http://runlevelzero.net/
http://caosity.org/
http://warewulf-cluster.org/

Do not look anywhere for truth, for all that is needed is to refrain from
allowing concepts to arise.


From gmk at runlevelzero.net  Mon Aug 29 22:19:37 2005
From: gmk at runlevelzero.net (Greg M. Kurtzer)
Date: Mon, 29 Aug 2005 22:19:37 -0700
Subject: [cAos] cAos-2 Repository updates
Message-ID: <20050830051937.GA23055@titan.runlevelzero.net>

Current:
   + SRPMS/joe-3.1-7.src.rpm
   + SRPMS/udev-050-5.src.rpm
   - SRPMS/udev-050-4.src.rpm

Stable:
   + SRPMS/joe-3.1-7.src.rpm
   + SRPMS/udev-050-5.src.rpm
   - SRPMS/udev-050-4.src.rpm

-- 
Greg M. Kurtzer
http://runlevelzero.net/
http://caosity.org/
http://warewulf-cluster.org/

Do not look anywhere for truth, for all that is needed is to refrain from
allowing concepts to arise.