Saturday, February 26, 2011

Us Visa Without Confirmation Id

Compile GNU Octave 3.4.0 Compile

On 8 February been released version 3.4.0 of GNU Octave , Deputy free of MATLAB. Find what's new in this version here.

In this post I will explain how to compile this version of GNU Octave. A few months ago we saw how to compile the version 3.2.2. It will not be very different to the 3.4.0 build, indeed, I personally have not encountered many problems in compiling 3.4.0 compared to 3.2.2. The guide was tested on Ubuntu 10.10, there should be no difference in practice to build GNU Octave on Debian Sid. For other Linux distributions will probably be the only things different commands be used to invoke the package manager used.

First install the compiler by installing build-essential metapackage . This can be installed by Synaptic, or from the terminal with the command:
 sudo apt-get install build-essential meta-
install build-essential if the compilers do not already exist, if they are already installed ... does practically nothing. In this way, however, we make sure to have them installed. After that install the dependencies or libraries needed to compile GNU Octave. We can do this very quickly from the terminal with the command: sudo
 apt-get build-dep octave3.2 
This command will install the necessary dependencies to build the 3.2 branch of GNU Octave, but they are almost identical to the 3.4 branch. Only thing missing is a library to be installed. It does not prevent the compilation, but may be useful in some cases. It's called bison and can be installed as usual from Synaptic or from the terminal with the command
 sudo apt-get install bison 
Download the source code for GNU Octave: http://www.gnu. org / software / octave / download.html . Version 3.4.0 can be downloaded from the terminal with the command wget
 ftp://ftp.gnu.org/gnu/octave/octave-3.4.0.tar.bz2 
Unpack the archive. This can be done graphically or from the terminal with the command tar
 xjvf octave-3.4.0.tar.bz2 
We enter the terminal with the root of the source code for GNU Octave: octave-3.4.0
 cdd / 
read the README file INSTALL and explaining how to compile a program. First we need to configure the program using the script configure . You can see the list of configuration options by calling the script with the option - help :
. / Configure - help 
We can now configure GNU Octave:
. / Configure 
If you feel you must, of course, add the options you prefer. If everything goes well you should read to the end of the output of . / Configure something like this:
 Octave is now configured for i686-pc-linux-gnu 

Source directory:.
Installation prefix: / usr / local
C compiler: gcc-mieee-fp-Wall-W-Wshadow-Wformat-Wpointer-arith-Wmissing-prototypes-Wstrict-prototypes-Wwrite-strings-Wcast-align-Wcast-how - g-O2-pthread
C + + compiler: g + +-mieee -I/usr/include/freetype2-fp-Wall-W-Wshadow-Wold-style-cast-Wformat-Wpointer-arith-Wwrite-strings-Wcast-align-Wcast -what-g -O2
Fortran compiler: gfortran -O -mieee-fp
Fortran libraries: -L/usr/lib/gcc/i686-linux-gnu/4.4.5 -L/usr/lib/gcc/i686-linux-gnu/4.4.5/../../../../lib -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/i686-linux-gnu/4.4.5/../../.. -L/usr/lib/i686-linux-gnu -lgfortranbegin -lgfortran -lm
Lex libraries:
LIBS: -lm

AMD CPPFLAGS:
AMD LDFLAGS:
AMD libraries: -lamd
BLAS libraries: -lblas
CAMD CPPFLAGS:
CAMD LDFLAGS:
CAMD libraries: -lcamd
CARBON libraries:
CCOLAMD CPPFLAGS:
CCOLAMD LDFLAGS:
CCOLAMD libraries: -lccolamd
CHOLMOD CPPFLAGS:
CHOLMOD LDFLAGS:
CHOLMOD libraries: -lcholmod
COLAMD CPPFLAGS:
COLAMD LDFLAGS:
COLAMD libraries: -lcolamd
CURL CPPFLAGS:
CURL LDFLAGS:
CURL libraries: -lcurl
CXSPARSE CPPFLAGS:
CXSPARSE LDFLAGS:
CXSPARSE libraries: -lcxsparse
DL libraries: -ldl
FFTW3 CPPFLAGS:
FFTW3 LDFLAGS:
FFTW3 libraries: -lfftw3
FFTW3F CPPFLAGS:
FFTW3F LDFLAGS:
FFTW3F libraries: -lfftw3f
fontconfig CFLAGS:
fontconfig LIBS: -lfontconfig
FT2_CFLAGS: -I/usr/include/freetype2
FT2_LIBS: -lfreetype -lz
GLPK CPPFLAGS:
GLPK LDFLAGS:
GLPK libraries: -lglpk
graphics CFLAGS: -g -O2 -D_THREAD_SAFE -D_REENTRANT
graphics LIBS: -Wl,-Bsymbolic-functions -lfltk_gl -lfltk
Magick++ CPPFLAGS: -I/usr/include/GraphicsMagick
Magick++ LDFLAGS:
Magick++ libraries: -lGraphicsMagick++ -lGraphicsMagick
HDF5 CPPFLAGS:
HDF5 LDFLAGS:
HDF5 libraries: -lhdf5
LAPACK libraries: -llapack
OPENGL libraries: -lfontconfig -lGL -lGLU
PTHREAD flags: -pthread
PTHREAD libraries:
QHULL CPPFLAGS:
QHULL LDFLAGS:
QHULL libraries: -lqhull
QRUPDATE libraries: -lqrupdate
READLINE libraries: -lreadline
REGEX libraries: -L/usr/lib -lpcre
TERM libraries: -lncurses
UMFPACK libraries: -lumfpack
X11 include flags:
X11 libraries: -lX11
Z CPPFLAGS:
Z LDFLAGS:
Z libraries: -lz

Default pager: less
gnuplot: gnuplot

Do internal array bounds checking: false
Build static libraries: false
Build shared libraries: true
Dynamic Linking: true (dlopen)
Include support for GNU readline: true
64-bit array dims and indexing: false
Se non avessimo installato bison avremmo inoltre letto un avviso di questo tipo:
 configure: WARNING: I didn't find bison, but it's only a problem if you need to reconstruct parse.cc 
configure: WARNING: OpenGL libs (GL and GLU) not found. Native graphics will be disabled.
configure: WARNING:
configure: WARNING: I didn't find the necessary libraries to compile native
configure: WARNING: graphics. It isn't necessary to have native graphics,
configure: WARNING: but you will need to have gnuplot installed or you won't
configure: WARNING: be able to use any of Octave's plotting commands
configure: WARNING:
configure:
configure: NOTE: libraries may be skipped if a library is not OR
found configure: NOTE: if the library on your system is missing required features.
This is the message I got after I first set up (though I had not yet installed bison). As you can see I have reported the lack of OpenGL. I solved this "problem" (not a real problem because it is just a warning, not an error) by installing the packages libgl1-mesa-dev and libglu1-mesa-dev :
 sudo apt-get install libgl1-mesa-dev libglu1-mesa-dev 
Normally this problem should not occur because these packages should be installati usando apt-get build-dep octave3.2 , non so bene per quale motivo a me sono stati rimossi.

Dopo aver finalmente configurato GNU Octave possiamo compilarlo con il comando
 make 
Per rendere più veloce la compilazione, chi ha un processore multicore può passare a make l'opzione -j n , dove n è il numero di core del processore (o meglio di job simultanei che può gestire, però per semplificare il discorso parliamo di core). Quindi chi, per esempio, ha un processore con quattro core potrà usare per compilare GNU Octave il comando
 make -j 4 
If the build is successful (depending on the computing power of your computer this could take from a few tens of minutes to several hours) at the end of the transaction on the terminal read a message like this:
 Octave successfully built. Now choose from the Following: 

. / Run-octave - to run in place to test before installing
make check - to run the tests
make install - to install (PREFIX = / usr / local)

make [2] : Leaving directory "/[...]/ octave-3.4.0 "
make [1]: Leaving directory "/[...]/ octave-3.4.0"
As you can see before installing Octave you can start to see if it works with the command
. / run-octave 
Finally we can install it with the command sudo make install
 
If we want a crare. deb package to ease the subsequent installation or removal, we can use checkinstall: sudo checkinstall
 

Saturday, February 19, 2011

Do Women Like Shaved Legs?

qtiplot 0.9.8.4

NOTE: Renato Rivoira, and I thank him, he edited the Italian translation of qtiplot and its manual. In comments on this post asks, who is able to do so, to help him revise his translations. You can contact him by sending an email to renatoriv AT ​libero PUNTO it .

Il 18 febbraio 2011 è stata rilasciata la versione finale di QtiPlot 0.9.8.4, un programma per l'analisi dei dati, equivalente libero di Origin . Questa versione porta con sé numerose novità che potete leggere qui .

QtiPlot è un programma un po' particolare perché il codice sorgente è rilasciato con licenza GPL ma lo sviluppatore distribuisce i binari precompilati a pagamento . Ciò non è in alcun modo in contrasto con il concetto di software libero perché nella sua definizione non si parla di prezzo. La confusione di "software libero" con "software free "is more prevalent in English-speaking people, since this is the word" free "has the double meaning of" free "and" free. "Even if you use this software, having compiled by itself can make a donation to the project to 'Address http://soft.proindependent.com/why_donate.html to allow the developer to carry out his project.

In this post I will explain how to fill qtiplot. This guide is for Ubuntu Maverick Meerkat 10.10 (and probably work without too many problems for Debian), other distributions there may be small differences in the commands that invoke the package manager, the names dei pacchetti e la disponibilità di questi.

Innanzitutto cominciamo con l'installare tutte le dipendenze necessarie per la compilazione. In un terminale dare
 sudo apt-get install build-essential 
sudo apt-get build-dep qtiplot
Il primo comando installa (se non già presente, ma è difficile che non lo sia già) le utility necessarie per compilare la maggior parte dei programmi, il secondo installa le principali librerie che necessita QtiPlot per essere compilato. Nelle ultime versioni QtiPlot ha aggiunto altre dipendenze i cui pacchetti non sono disponibili nella versione di Ubuntu considerata, quindi prima di procedere con la compilazione di QtiPlot stesso dovremo compilare altri programmi.

Scarichiamo il codice sorgente di QtiPlot all'indirizzo http://download.berlios.de/qtiplot/qtiplot-0.9.8.4.tar.bz2 . Da terminale si può usare
 wget http://download.berlios.de/qtiplot/qtiplot-0.9.8.4.tar.bz2 
Scompattiamo l'archivio dove ci pare (se non siete in grado di farlo da terminale, vi ricordo che è possibile farlo attraverso interfaccia grafica) e spostiamoci con il terminale nella cartella in cui si trova il sorgente:
 tar xjvf qtiplot-0.9.8.4.tar.bz2 
cd qtiplot-0.9.8.4/
Aprite il file README.html presente nella cartella del sorgente (è sempre buona norma leggere i file README e/o INSTALL , or the like, before proceeding with the compilation of a program). As you can see the dependencies that are required are as follows: Qt (> = 4.5.0), GSL, muParser (1.32), libpng and zlib. All of these packages were installed (if not already present) with the command sudo apt-get build-dep qtiplot . Also, we need slightly different versions of the libraries QWT (5.2) and QwtPlot3D, but these are in sub 3rdparty / qtiplot source code, so no need to download anything new for this list so far. Other libraries are suggested QTeXEngine , ALGLIB (2.6) and TAMUANOVA .

Compiliamo queste librerie. Salveremo i codici sorgenti di queste nella sottocartella 3rdparty/ , per comodità, quindi spostiamoci in questa cartella:
 cd 3rdparty/ 
Scarichiamo e scompattiamo l'archivio contenente il codice sorgente di QTeXEngine:
 wget http://download.berlios.de/qtiplot/QTeXEngine-0.3-opensource.zip 
unzip QTeXEngine-0.3-opensource.zip
cd QTeXEngine
Compiliamo la libreria (le istruzioni sono presenti nel file README.txt :
 qmake 
make
Se tutto è andato bene (lo potete controllare guardando l'exit status con il comando echo $? , se è 0 then the operation has been completed correctly) back to the parent directory, download the source code and ALGLIB compiliamolo:
 cd .. 
http://www.alglib.net/translator/re/alglib-2.6.0.cpp.zip
unzip wget-alglib 2.6.0.cpp.zip; mv cpp alglib
cd alglib
The instructions for filling of this library are in the file manual.cpp.html . We must run the build script passing as argument the compiler to use, in our case, GCC. The script builds has execute permissions, so before we start to make the file executable :
 chmox 
+ x build. / Build gcc
If this operation has been completed successfully (check the exit status with echo $? : if we get 0 then it was fine) we go forward we can build TAMUANOVA. Let's move to the parent directory, download the source code TAMUANOVA, unpack the archive folder and enter the source code of this library:
 cd .. 
http://www.stat.tamu.edu/ wget tar xzvf ~ aredd/tamuanova/tamu_anova-0.2.tar.gz
tamu_anova-0.2.tar.gz; tamu_anova-0.2 mv / tamu_anova /
tamu_anova cd /
compile this library (instructions are included in the INSTALL file ):
. / configure make 

Check the exit status with echo $? . If you get 0 compilation is successful. No need to install the library (as even earlier), just completed it. Before we change a file: 3rdparty/qwtplot3d/qwtplot3d.pro . This file contains instructions for building the library QwtPlot3D (which will happen later when you compile qtiplot). At the end of this file you should add the following line:
  unix: CONFIG + =  staticlib 
to be compiled statically (hint taken from here ).

return to the terminal nella cartella principale del codice sorgente di QtiPlot (che si trova due cartelle superiori rispetto alla carella di ALGLIB in cui ci trovavamo prima):
 cd ../.. 
Prima di iniziare la compilazione vera e propria ci sono ancora diverse operazioni da fare. Prima di tutto dobbiamo creare un file chiamato build.conf da posizionare nella cartella del codice sorgente di QtiPlot e che contiene alcune istruzioni che servono per la compilazione. Questo file dovrà essere realizzato sulla base del modello build.conf.example che si trova nella stessa cartella. Per la precisione, build.conf contiene alcune opzioni e variabili per la compilazione e i percorsi delle librerie da utilizzare (oppure le corrispondenti compilation options). In this file the variable QTI_ROOT is equal to the root folder path of the source code qtiplot. I edited build.conf.example based on real locations and libraries used here is my build.conf :
  isEmpty (QTI_ROOT) { 
message ( "each Including this config file needs to Set QTI_ROOT to the dir containing this file! ")}


################################### #######################
# # System specific configuration
##########################################################

# Global include path which is always added at the end of the INCLUDEPATH
SYS_INCLUDEPATH = /opt/local/include
# Global lib path and libs which is ls always added at the end of LIBS
SYS_LIBS = -L/opt/local/lib

##########################################################
## zlib (http://www.zlib.net/)
##########################################################

# include path. leave it blank to use SYS_INCLUDE
ZLIB_INCLUDEPATH = $$QTI_ROOT/3rdparty/zlib/

##########################################################
## muParser (http://muparser.sourceforge.net/)
##########################################################

# include path. leave it blank to use SYS_INCLUDE
MUPARSER_INCLUDEPATH = /usr/include/muParser/
# link statically against a copy in 3rdparty/
MUPARSER_LIBS = /usr/lib/libmuparser.so
# or dynamically against a system-wide installation
# MUPARSER_LIBS = -lmuparser

##########################################################
## GNU Sientific Library (http://www.gnu.org/software/gsl/)
##########################################################

# include path. leave it blank to use SYS_INCLUDE
# GSL_INCLUDEPATH = $$QTI_ROOT/3rdparty/gsl/include
# link statically against a copy in 3rdparty/
# GSL_LIBS = $$QTI_ROOT/3rdparty/gsl/lib/libgsl.a \
# $$QTI_ROOT/3rdparty/gsl/lib/libgslcblas.a
# or dynamically against a system-wide installation
GSL_LIBS = -lgsl -lgslcblas

##########################################################
## QWT - use local copy till upstream catches up
# http://qwt.sourceforge.net/index.html
##########################################################

# include path.
QWT_INCLUDEPATH = $$QTI_ROOT/3rdparty/qwt/src
# link locally against a copy in 3rdparty/
QWT_LIBS = $$QTI_ROOT/3rdparty/qwt/lib/libqwt.a

##########################################################
## QwtPlot3D - use local copy till upstream catches up
# http://qwtplot3d.sourceforge.net/
##########################################################

# include path.
QWT3D_INCLUDEPATH = $$QTI_ROOT/3rdparty/qwtplot3d/include
# link locally against a copy in 3rdparty/
win32:QWT3D_LIBS = $$QTI_ROOT/3rdparty/qwtplot3d/lib/qwtplot3d.dll
unix:QWT3D_LIBS = $$QTI_ROOT/3rdparty/qwtplot3d/lib/libqwtplot3d.a

##########################################################
## libpng - optional. you don't have to set these variables
##########################################################

# include path. leave it blank to use SYS_INCLUDE
# LIBPNG_INCLUDEPATH = $$QTI_ROOT/3rdparty/libpng/
# link statically against a copy in 3rdparty/
# LIBPNG_LIBS = $$QTI_ROOT/3rdparty/libpng/libpng.a
# or dynamically against a system-wide installation
LIBPNG_LIBS = -lpng

##########################################################
## QTeXEngine - optional. you don't have to set these variables
# http://soft.proindependent.com/qtexengine/
##########################################################

# include path.
TEX_ENGINE_INCLUDEPATH = $$QTI_ROOT/3rdparty/QTeXEngine/src
# link locally against a copy in 3rdparty/
TEX_ENGINE_LIBS = $$QTI_ROOT/3rdparty/QTeXEngine/libQTeXEngine.a

##########################################################
## ALGLIB (2.6) - optional. you don't have to set these variables
# http://www.alglib.net/
##########################################################

# include path.
ALGLIB_INCLUDEPATH = $$QTI_ROOT/3rdparty/alglib/src
# link locally against a copy in 3rdparty/
ALGLIB_LIBS = $$QTI_ROOT/3rdparty/alglib/out/libalglib.a

##########################################################
## TAMUANOVA - optional. you don't have to set these variables
# http://www.stat.tamu.edu/~aredd/tamuanova/
##########################################################

# include path.
TAMUANOVA_INCLUDEPATH = $$QTI_ROOT/3rdparty/tamu_anova/
# link locally against a copy in 3rdparty/
TAMUANOVA_LIBS = $$QTI_ROOT/3rdparty/tamu_anova/libtamuanova.a

##########################################################
## python - only used if python is needed
##########################################################

# the python interpreter to use
# (unix only, windows will use what ever is configured to execute .py files!)
PYTHON = python

##########################################################
## Qt tools - allows to use specific versions
##########################################################

LUPDATE = lupdate
LRELEASE = lrelease

############################################################
## Target specific configuration: configure Qtiplot itself
############################################################

contains( TARGET, qtiplot ) {
# building without muParser doesn't work yet
SCRIPTING_LANGS + = muParser
SCRIPTING_LANGS + = Python

# a console displaying output of scripts; particularly useful on Windows
# where running QtiPlot from a terminal is inconvenient
DEFINES + = SCRIPTING_CONSOLE

# DEFINES += QTIPLOT_DEMO

# Uncomment the following line if you want to perform a custom installation using the *.path variables defined in ./qtiplot.pro.
# CONFIG += CustomInstall

# Uncomment The following line If You Want to Build qtiplot as a browser plugin (not working on Internet Explorer).
# CONFIG + = BrowserPlugin

CONFIG + = release
# CONFIG + = debug

Uncomment # The following line If You Want to link statically Against Qt.
# CONFIG + = StaticBuild
# win32: CONFIG + = console}


We have not finished yet, we have to do one last thing. Edit the file qtiplot.pro che si trova nella cartella principale del codice sorgente. Questo contiene il nome di quali cartelle contengono del codice che dovrà essere compilato. Togliamo dall'elenco fitPlugins e manual (eventualmente potranno essere compilati successivamente), quindi il file apparirà più o meno così:
 TEMPLATE = subdirs 

SUBDIRS = 3rdparty/qwt \
3rdparty/qwtplot3d \
qtiplot
A questo punto dovremmo essere in grado, finalmente di compilare QtiPlot. Come spiegato nel file README.html i comandi da dare sono
 qmake 
make
Per rendere più veloce la compilazione, chi ha un processore multicore può passare a make l'opzione -j n , dove n è il numero di core del processore (o meglio di job simultanei che può gestire, però per semplificare il discorso parliamo di core). Quindi chi, per esempio, ha un processore con quattro core potrà usare per compilare QtiPlot il comando
 make -j 4 
Se la compilazione va a buon fine (come al solito possiamo controllarlo con echo $? ) possiamo direttamente avviare QtiPlot, per vedere se funziona, inserendo il percorso relativo dell'eseguibile appena generato:
 qtiplot/qtiplot 
Finally you can, if desired, install the program with
 sudo make install or by using 
checkinstall: sudo checkinstall
 
that creates a simple package. Deb (the result, however, is "professional").

Bes Hairspray For Teasing

Emacs: open the file manager folder in the current buffer

In Emacs is a mode called Dired that acts as a file manager . However, in some cases you may want to open the file manager 's desktop environment in use (or an external file manager) directly to the folder where the file currently being edited (or rather, the corresponding buffer). To do what you can add the following code in your initialization file (unless this function is not already present in Emacs and I am not able to find it):
 (defun    open-buffer -path () 
"Run Nautilus on the directory of the current buffer."
(interactive)
(shell-command (concat "nautilus" default-directory)))
This code defines the function open-path buffer that will open the file manager Nautilus (the GNOME default) in the default folder (which normally corresponds to the folder where the file is in use, or to your home if the buffer is not an open file). If you want to use a file manager other than just replace the command as an argument to concat (and perhaps even the Nautilus line that appears in the description of the function).

If you wish you can assign a keyboard shortcut to this feature by adding to your initialization file:
 (global-set-key (kbd  "\u0026lt;M-f3>" ) 'open-path-buffer ) 
This code will be associated with the combination M-f3 function open-path buffer, if you want to use a different combination just replace the occurrence of M-f3 nel codice precedente.

Questo post prende spunto da http://zhangda.wordpress.com/2010/02/03/open-the-path-of-the-current-buffer-within-emacs/ in cui è definita una funzione per aprire il file manager Explorer in Windows. A questo proposito trovate un codice alternativo qui: http://www.factsandpeople.com/facts-mainmenu-5/2-editor-emacs/80-switching-between-windows-explorer-and-emacs .

Saturday, February 12, 2011

Full Head Sew In Weave With Side Bang

Wednesday, February 16 LISZT IN ITALY WITH LUCCHESINI




FRANZ LISZT , which we celebrating the anniversary of two hundred years from birth, had a strong connection with Italy and consequently with the music, opera and Italian musicians. He also played cello with the Italian dishes and Braga, which greatly admired, even dedicating his compositions on the cello. But of course the voice of Liszt is the piano and feel like the work of Italian Rossini, Verdi and Doninzetti inspired the composer.
By Andrea Lucchesini piano and Mario Brunello cello, Liszt in Italy.
All ' rust WEDNESDAY' February 16 at 21

PASS THE WORD!

input responsible

Friday, February 4, 2011

Glory Hole Locations In Sac

BRUNELLO AND STRING ORCHESTRA AND THE ITALIAN PURPLE



A welcome return to DANILO ROSSI , principal violist of the Teatro alla

Scala, this time for conduct and play all together ' ITALIAN STRING ORCHESTRA.
listen to the beautiful Concerto for Strings by Nino Rota , but most feel the swing in "Bruderschaft" for viola, piano and strings the composer Giorgio Vato Kakhidze , and the revisiting of themes taken from the fascinating sacred tradition of popular song in the new Stefano Nanni, "Brotherhood" . Along with Danilo Rossi will be back STEFANO Bezziccheri , former host of rust as "flying piano" for an evening where you will see the work of the soloists with the orchestra of sounds and stories.

Sunday, February 6, 2011 AT 21

PASS THE WORD!

input responsible