[Solved] Development "methodology"

This is not strictly speaking, a programming question, but this section of the forum seemed the more appropriate. So, say you want to start developing pacman, or vim, or (to stretch the question), KDE. How do you set up your environment? For pacman I would modify the source and do something like makepkg --noextract (but do speak up if there are better ways!). I guess this could also work for vim but, and for KDE? Chroot? Virtual machine?
And even for "simpler" things like vim, I don't think it's possible to install say, vim alongside a vim-devel version... is it? Again, are there better alternatives?
Thanks in advance for the help, and my apologies for such a "broad" question...
Last edited by gauthma (2014-03-25 23:28:22)

Remember, all pacman (and PKGBUILD) files do is automate the installation of software. You can run the same commands yourself just by typing what you see in the PKGBUILD file into Bash. Also, you can alter where you install it in order to test it out.
Let's use Vim as an example: Vim uses the standard "./configure && make && make install" build instructions. So, first get a copy of the Vim source code. (Now, since you have a developer's version of the source instead of a packager's version, you may need to run "autoconf" now.) Next, build and install it into a personal location like this:
./configure --prefix=~/tmp/vim-dev && make && make install
Now, edit the source code, re-run "make && make install", and run it with "~/tmp/vim-dev/bin/vim". That personal copy of Vim will ONLY use the files that are under "~/tmp/vim-dev".
I don't know how to configure, build, and install KDE, but (in theory) it will be a similar process. Just read the PKGBUILD file for it.
Does that help?

Similar Messages

Jdeveloper (ADF) development methodology

Hi,
I am new to Jdeveloper and trying to learn as much as possible from it.
The target is to be able to develop soon web applications based on ADF Faces and ADF BC.
There are lots of useful tutorials in the OTN (also have been testing and analyzing the SRDemoSample). However, I haven't found any formal development methodology I can use as a basis when using ADF Faces together with ADF BC (maybe something like RUP but applied to ADF).
I know Oracle has something called JCDM, but I think it is for internal use and also I don't know if they have a version instantiated for ADF.
Anyone out there with any recommendation / practice in this regard?
Thanks,
Claudio.

Shay,
Thanks for your answer.
Maybe I expressed myself in the wrong way, but I am not looking for implementation details such as i18n and securing an application. Those details are pretty clear in the SRDemo.
What I am really looking for is how Oracle recommends on doing a detailed design of an ADF application. Let's say you have the requirements and use cases of the application, and you are asked to do the detail design of an application that will use JSF and ADF BC (notice I am saying BC: Toplink in our case is not an option).
First thing that comes into my mind is to do UML class diagrams, sequence diagrams, etc and then show that to the developers to give them the starting point for implementation. But will these diagrams be of use for the developers, given the fact that ADF is mostly wizard based?
I mean in a large project you can't just leave the developers only with the use cases and requirements because when the project starts to grow, it will become unmanageable. So I think there should be a detailed design (that is updated as the project evolves) - but how do you match this design with ADF wizards, I know Jdeveloper has UML support, but is there a tutorial (or documentation) that starts with the detail design and then builds the application from there ?
Thanks again,
Claudio.

Standard Development Methodology

I work as a software development team leader in Oracle platform.
We have been using Developer/2000 and Oracle Workgroup server for
most of our projects. As a team leader I always tried to
implemented a standard software development mothodology in our
team's work. However, as I have not gone through any such
standards that is recommended by Oracle or any other
International bodies, I have always tried to make our software
development suitable for my self and our team which, I wonder,
may not meet any standards recommended by Oracle.
I am thus looking for some resources, books, magazines that
describe, in detail, standard methods of software development in
Oracle platform. Starting from naming an entity, naming a form,
report, a block in a form, naming variables, using color schemes,
etc., I would like to use standard names/methods to all objects
of our application and implement standard software development
methodology in our development.
Please suggest me such methods or resources and let me know where
I can find them.
null

Bal Ram (guest) wrote:
: I work as a software development team leader in Oracle
platform.
: We have been using Developer/2000 and Oracle Workgroup server
for
: most of our projects. As a team leader I always tried to
: implemented a standard software development mothodology in our
: team's work. However, as I have not gone through any such
: standards that is recommended by Oracle or any other
: International bodies, I have always tried to make our software
: development suitable for my self and our team which, I wonder,
: may not meet any standards recommended by Oracle.
: I am thus looking for some resources, books, magazines that
: describe, in detail, standard methods of software development
in
: Oracle platform. Starting from naming an entity, naming a form,
: report, a block in a form, naming variables, using color
schemes,
: etc., I would like to use standard names/methods to all objects
: of our application and implement standard software development
: methodology in our development.
: Please suggest me such methods or resources and let me know
where
: I can find them.
My suggestion on this would be.
1. Check the Developer's manual in which Oracle has given certain
guidelines in application development.
2. Naming convention can be used as per your convenience, but
should follow the same pattern throughout.
3. Most big companies make their Methodology book, but that is
changed or reviewed every two year or later.
4. If you find such book do let me know as well
-bj
null

Development Methodology

Hi Friends and Experts,
Can any one please let me know what is Development methodology used in ABAP.

***********Please reward points ,if found useful
Hi,
ASAP: Accelerated Systems Application and Products in Data Processing
ASAP methodoligy means nothing but standard process for implementation of SAP, It consists of 5 phases.
1. Project preperation - consists of identifying team members and developing strategy as how to go.
2. Business Blue print - consists of identifying the client current process, reqeirement and how SAP provides solution.
Consists of detailed documentaion
3. Realization -The purpose of this phase is to implement all the business and process requirements based on the
Business Blueprint.
4 Final Preparation - The purpose of this phase is to complete testing, end-user training,
5 Go Live and Support
All the functinal consultatns need good rapo with Abapers. right from uploading of legacy data, devoloping customised reports, BDC's, Forms etc, here functinal consultatns need to give guidence as to get the requried data for reports and all.. like the table name, fields etc
All implementation projects have the the following phases:
Scoping - What is to be implemented i.e. which submodules are to be implemented some clients may not require credit management for example. Look at the project scope document carefully it will tell you what SAP sub-modules in SAP you should be prepared for. Usually the sales people along with project manager do it.
As is - Here you understand the existing business processes of the client . Your BPOcollect all the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyse how and when the reports/forms are generated, where the data is coming from. You also do a Level -2 training for your BPO so he is made aware of all the required transactions in SAP.
Once this is over BPO can start learning with the consultants help more about SAP. This is crucial because if you miss out any transactions the BPO may forget about some of his Business processes which may come up later. It is a good practice to ask the BPO to make flow charts to explain business processes.
To-Be - Parallely you map these processes to SAP. Processes that you are not sure of as to whether they are present in SAP or not you try to do a configuration of those processes, and along with the BPO(Business process owner he is the clients employee who knows about the clients business processes probably a middle management guy, ther can more than one), BPO involvement is required as he may be able to tell you his requirements better. Once you do the business modelling you
will also be made aware of the gaps between as-is and to-be , here decisons have to be made as to wether a ABAP development/system modification is required or not and so on. Involve the BPO as much as possible and document everything it is good practice do not be lazy about it.
Business blueprint: Here the as-is and to-be and gap analysis is explained. This is the document that you will be using to do your configuration in the realization phase.
Realization phase: Here you do the configuration in the development server (there are three clients -development,quality, production). You also decide on the master data format, so that BPO can go collect the master data. You also gove ABAP specifications for forms, reports etc, system modifications etc. Unit testing: Your BPOs and a few key users sit down and test your configuration in your module only. It is good to test the BDCs that you need for uploading data at this stage so you have more realistic data and your BDCs are tested.
Integration testing:
Once all modules unit testing is over then the configuration is trasported to the Quality server, where testing for all the modules is done by BPOs and end user, this is to check if any problems are there in integration between various modules. Once all is okay from the QA server config is transported to the production server.
Go live preparation
Data uploading: The collected master data is checked and the uploaded into production server(sever and client I have used interchangeably). Now you are ready for go live i.e. users can now use the production server.
With Regards,
BVS

Development Methodology: urgent

what is development methodology in sap development.

ASAP methodology
AcceleratedSAP (i.e. ASAP) methodology/roadmap is a proven, repeatable and successful approach to implement SAP solutions across industries and customer environments. ASAP is widely used for SAP Business Suite (SAP ERP, SAP CRM, SAP SCM, SAP PLM, SAP SRM), SAP xApps, SAP NetWeaver and SAP Solutions for Mobile Business among many other solutions. The methodology covers the necessary project management, the configuration of business processes, testing and training aspects as well as technical implementation activities.
In order to ensure central data access, the ASAP roadmap and tools have become a standard component in SAP Solution Manager (service.sap.com/solutionmanager) - the implementation and operations platform. In addition, ASAP is available for browsing and offline use on Service Market Place. From tool perspective, the SAP Solution Manager implementation function is the successor to the ASAP tools, hence some tools such as the Implementation Assistant, Q&Adb, and the Master Lists are replaced by Solution Manager Implementation Function.
ASAP Roadmap
Use
The ASAP Roadmap provides the methodology for implementing and continuously optimizing
your SAP software. It divides the implementation process into five phases and offers detailed
Project Plans to assist you (in Microsoft Project format). The documentation stored at each level
of the Roadmap tree structure contains recommendations on implementing your SAP software
and links to helpful tools and accelerators.
Purpose
When you install the Implementation Assistant you can choose from several Roadmap types and
flavors. You can select one of the following flavors:
R/3 - Implementation and Continuous Improvement
APO - Advanced Planner & Optimizer
BW - Business Information Warehouse
B2B - Business to Business
CRM - Customer Relationship Management
Features
Implementation of SAP software covers the following phases:
1. Project Preparation
In this phase you plan your project and lay the foundations for successful implementation. It
is at this stage that you make the strategic decisions crucial to your project:
− Define your project goals and objectives
− Clarify the scope of your implementation
− Define your project schedule, budget plan, and implementation sequence
− Establish the project organization and relevant committees and assign resources
2. Business Blueprint
In this phase you create a blueprint, which documents your enterprises requirements and
establishes how your business processes and organizational structure are to be represented
in SAP software. You also refine the original project goals and objectives and revise the
overall project schedule in this phase.
3. Realization
In this phase, you configure the requirements contained in the Business Blueprint. Baseline
configuration (major scope) is followed by final configuration (remaining scope), which can
consist of up to four cycles. Other key focal areas of this phase are conducting integration
tests and drawing up end user documentation.
4. Final Preparation
In this phase you complete your preparations, including testing, end user training, system
management, and cutover activities. You also need to resolve all open issues in this phase.
At this stage you need to ensure that all the prerequisites for your system to go live have
been fulfilled.
5. Go Live & Support
In this phase you move from a pre-production environment to the live system. The most
important elements include setting up production support, monitoring system transactions,
and optimizing overall system performance.
After your system has gone live, you can use a separate Roadmap with six work
packages, in order to optimize your R/3 System continuously.
These phases are the main milestones for implementing SAP software. Each phase has:
Work packages, which consist of activities, for which project teams are responsible.
Activities, which consist of tasks, which are processed by one or more team members.
Tasks, which are carried out by a project team member. You can also access the How-to
sections and accelerators at this level.
Also check this AcceleratedSAP document.
http://help.sap.com/printdocu/core/print46b/en/data/en/pdf/SVASAP.pdf
Regards,
Maha

Development Methodology for MI

Hi,
Can anyone have Implementation Methodology document for Mobile Infrastructure or any informaion where I will get the document?
Thanks & Regards
Nileshwar.

hello nileshwar,
there are steps and recommendations regarding MI application
development on <a href="http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/index.htm">Mobile Development Kit</a>.
for MI implemenation you can refer to <a href="http://help.sap.com/saphelp_nw04/helpdata/en/bb/b670bbaa991845924982155b7c3726/content.htm">Configuration of SAP Mobile Infrastructure</a>
in the NW04 help document.
regards
jo

Jdeveloper's own development methodology.

as developers we wonder the methods (not secret ones).
are used to develop J developer IDE.
For example microsoft publish their some of the methods MOF, MS Team system etc.
Maybe Oracle will do it in the future?
if there is no company restriction to mention
Can you explain these methodology briefly? J dev own lifecyle.
Thanks.

Thanks.
We are waiting series next articles.

J2EE development methodology

Hi,
I am preparing a proposal to push J2EE as our enterprise application standard. I don't know what methodology we should use to develop J2EE application, it seems that water-fall is not a good idea here.
Could anybody help? Thanks in advance.

Here is the methodology I used on my latest project (it turned out that by focussing on the first development as waterfall we could produce a set of reusable beans that allow us to now select the most appropriate methodology for future developments).
We focussed on one particular application, used UML to capture the design and then built individual components using a waterfall method.
The design divided the components into a reusable layer, and an application specific layer (effectively a layer that provided various services, and a layer that co-ordinated those services together)
We have effectively built other applications now by using a strong design to identify functionality that can be reused (from the service layer) and functionality required in the application specific layer. Any new service layer components can be built using the most appropriate methodology.
Building a client and the application specific layer we have done using both classical waterfall and RAD approaches, depending upon which is most appropriate. Development times are obviously reduced since we have a pool of service layer bean functionality.
Adam

[Solved] Developer supplied me a patch, but I can't seem to apply it

Hello,
I wanted to make xfce4-indicator-plugin work with the new branch of libindicator, so I emailed the developer on this issue. He supplied me with a patch, but I can't seem to apply it. I customized the xfce4-indicator-plugin PKGBUILD to grab the latest version and apply the patch, but I get the following error:
==> Starting build()...
can't find file to patch at input line 11
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
|From 68b8d6ab2ff0a4e39836a8c3d5f391b745eb5354 Mon Sep 17 00:00:00 2001
|From: Mark Trompell <[email protected]>
|Date: Fri, 09 Sep 2011 07:45:25 +0000
|Subject: allow building with indicator-0.4
|
|---
|diff --git a/configure.in.in b/configure.in.in
|index e0913ba..107ae55 100644
|--- a/configure.in.in
|+++ b/configure.in.in
File to patch:
When I put in configure.in (which I think I need) I get the error that I need to install the older libindicator. Now, either the patch is wrong (which I doubt) or I'm patching the wrong file... Can you help me? The developer hasn't answered my email that I sent a week ago now, so I thought I'd ask here. Here's my PKGBUILD:
pkgname=xfce4-indicator-plugin
pkgver=0.3.1
_pkgbranch=3.0
pkgrel=1
pkgdesc="Display indicators in the xfce4 panel"
arch=(i686 x86_64)
license=('LGPL2.1')
url="http://goodies.xfce.org/projects/panel-plugins/xfce4-indicator-plugin"
groups=('xfce4-goodies')
depends=('xfce4-panel' 'libxfce4util' 'libindicator')
makedepends=('intltool' 'xfce4-dev-tools')
options=('!libtool')
source=(http://archive.xfce.org/src/panel-plugins/$pkgname/$_pkgbranch/$pkgname-$pkgver.tar.bz2
libindicator-fix.patch)
build() {
cd ${srcdir}/${pkgname}-${pkgver}
patch -Np0 -i "${srcdir}/libindicator-fix.patch"
./configure --prefix=/usr \
--sysconfdir=/etc \
--libexecdir=/usr/lib \
--localstatedir=/var \
--disable-static \
--disable-debug
make
package() {
cd ${srcdir}/${pkgname}-${pkgver}
make DESTDIR=${pkgdir} install
md5sums=('c4940695e412f7bac0fdb46be22ab5f2'
'ab714e4bcf5d113f87647ecd20bd88f4')
EDIT: and here's the patch:
From 68b8d6ab2ff0a4e39836a8c3d5f391b745eb5354 Mon Sep 17 00:00:00 2001
From: Mark Trompell <[email protected]>
Date: Fri, 09 Sep 2011 07:45:25 +0000
Subject: allow building with indicator-0.4
diff --git a/configure.in.in b/configure.in.in
index e0913ba..107ae55 100644
--- a/configure.in.in
+++ b/configure.in.in
@@ -67,7 +67,7 @@ dnl ***********************************
XDT_CHECK_PACKAGE([GTK], [gtk+-2.0], [2.6.0])
XDT_CHECK_PACKAGE([LIBXFCE4UTIL], [libxfce4util-1.0], [4.3.99.2])
XDT_CHECK_PACKAGE([LIBXFCE4PANEL], [libxfce4panel-1.0], [4.3.99.2])
-XDT_CHECK_PACKAGE([INDICATOR], [indicator], [0.3.0])
+XDT_CHECK_PACKAGE([INDICATOR], [indicator], [0.3.0], [], [XDT_CHECK_PACKAGE([INDICATOR], [indicator-0.4], [0.3.90])])
dnl ***********************************
dnl *** Check for debugging support ***
cgit
Last edited by Unia (2011-09-13 18:32:08)

There you go:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by xfce4-indicator-plugin configure 0.3.1, which was
generated by GNU Autoconf 2.68. Invocation command line was
$ ./configure --prefix=/usr --sysconfdir=/etc --libexecdir=/usr/lib --localstatedir=/var --disable-static --disable-debug
## Platform. ##
hostname = lappy
uname -m = x86_64
uname -r = 3.0-ARCH
uname -s = Linux
uname -v = #1 SMP PREEMPT Tue Aug 30 08:53:25 CEST 2011
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = x86_64
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /home/jente/bin
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /bin
PATH: /usr/local/sbin
PATH: /usr/sbin
PATH: /sbin
PATH: /opt/java/jre/bin
PATH: /usr/bin/core_perl
## Core tests. ##
configure:2320: checking build system type
configure:2334: result: x86_64-unknown-linux-gnu
configure:2354: checking host system type
configure:2367: result: x86_64-unknown-linux-gnu
configure:2387: checking target system type
configure:2400: result: x86_64-unknown-linux-gnu
configure:2444: checking for a BSD-compatible install
configure:2512: result: /bin/install -c
configure:2523: checking whether build environment is sane
configure:2573: result: yes
configure:2714: checking for a thread-safe mkdir -p
configure:2753: result: /bin/mkdir -p
configure:2766: checking for gawk
configure:2782: found /usr/bin/gawk
configure:2793: result: gawk
configure:2804: checking whether make sets $(MAKE)
configure:2826: result: yes
configure:2901: checking how to create a ustar tar archive
configure:2914: tar --version
tar (GNU tar) 1.26
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by John Gilmore and Jay Fenlason.
configure:2917: $? = 0
configure:2957: tardir=conftest.dir && eval tar --format=ustar -chf - "$tardir" >conftest.tar
configure:2960: $? = 0
configure:2964: tar -xf - <conftest.tar
configure:2967: $? = 0
configure:2980: result: gnutar
configure:2990: checking whether to enable maintainer-specific portions of Makefiles
configure:2999: result: no
configure:3061: checking for gcc
configure:3077: found /usr/bin/gcc
configure:3088: result: gcc
configure:3317: checking for C compiler version
configure:3326: gcc --version >&5
gcc (GCC) 4.6.1 20110819 (prerelease)
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:3337: $? = 0
configure:3326: gcc -v >&5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.6.1/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /build/src/gcc-4.6-20110819/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --enable-gnu-unique-object --enable-linker-build-id --with-ppl --enable-cloog-backend=isl --enable-lto --enable-gold --enable-ld=default --enable-plugin --with-plugin-ld=ld.gold --disable-multilib --disable-libssp --disable-libstdcxx-pch --enable-checking=release
Thread model: posix
gcc version 4.6.1 20110819 (prerelease) (GCC)
configure:3337: $? = 0
configure:3326: gcc -V >&5
gcc: error: unrecognized option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:3337: $? = 1
configure:3326: gcc -qversion >&5
gcc: error: unrecognized option '-qversion'
gcc: fatal error: no input files
compilation terminated.
configure:3337: $? = 1
configure:3357: checking whether the C compiler works
configure:3379: gcc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
configure:3383: $? = 0
configure:3431: result: yes
configure:3434: checking for C compiler default output file name
configure:3436: result: a.out
configure:3442: checking for suffix of executables
configure:3449: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
configure:3453: $? = 0
configure:3475: result:
configure:3497: checking whether we are cross compiling
configure:3505: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
configure:3509: $? = 0
configure:3516: ./conftest
configure:3520: $? = 0
configure:3535: result: no
configure:3540: checking for suffix of object files
configure:3562: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:3566: $? = 0
configure:3587: result: o
configure:3591: checking whether we are using the GNU C compiler
configure:3610: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:3610: $? = 0
configure:3619: result: yes
configure:3628: checking whether gcc accepts -g
configure:3648: gcc -c -g conftest.c >&5
configure:3648: $? = 0
configure:3689: result: yes
configure:3706: checking for gcc option to accept ISO C89
configure:3770: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:3770: $? = 0
configure:3783: result: none needed
configure:3814: checking for style of include used by make
configure:3842: result: GNU
configure:3867: checking dependency style of gcc
configure:3977: result: gcc3
configure:3992: checking for a sed that does not truncate output
configure:4056: result: /bin/sed
configure:4074: checking for grep that handles long lines and -e
configure:4132: result: /bin/grep
configure:4137: checking for egrep
configure:4199: result: /bin/grep -E
configure:4204: checking for fgrep
configure:4266: result: /bin/grep -F
configure:4293: checking how to print strings
configure:4320: result: printf
configure:4353: checking for ld used by gcc
configure:4420: result: /usr/bin/ld
configure:4427: checking if the linker (/usr/bin/ld) is GNU ld
configure:4442: result: yes
configure:4497: checking for BSD- or MS-compatible name lister (nm)
configure:4546: result: /usr/bin/nm -B
configure:4676: checking the name lister (/usr/bin/nm -B) interface
configure:4683: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:4686: /usr/bin/nm -B "conftest.o"
configure:4689: output
0000000000000000 B some_variable
configure:4696: result: BSD nm
configure:4699: checking whether ln -s works
configure:4703: result: yes
configure:4711: checking the maximum length of command line arguments
configure:4836: result: 1572864
configure:4853: checking whether the shell understands some XSI constructs
configure:4863: result: yes
configure:4867: checking whether the shell understands "+="
configure:4873: result: yes
configure:4908: checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format
configure:4948: result: func_convert_file_noop
configure:4955: checking how to convert x86_64-unknown-linux-gnu file names to toolchain format
configure:4975: result: func_convert_file_noop
configure:4982: checking for /usr/bin/ld option to reload object files
configure:4989: result: -r
configure:5063: checking for objdump
configure:5079: found /usr/bin/objdump
configure:5090: result: objdump
configure:5122: checking how to recognize dependent libraries
configure:5324: result: pass_all
configure:5409: checking for dlltool
configure:5439: result: no
configure:5469: checking how to associate runtime and link libraries
configure:5496: result: printf %s\n
configure:5557: checking for ar
configure:5573: found /usr/bin/ar
configure:5584: result: ar
configure:5621: checking for archiver @FILE support
configure:5638: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:5638: $? = 0
configure:5641: ar cru libconftest.a @conftest.lst >&5
configure:5644: $? = 0
configure:5649: ar cru libconftest.a @conftest.lst >&5
ar: conftest.o: No such file or directory
configure:5652: $? = 1
configure:5664: result: @
configure:5722: checking for strip
configure:5738: found /usr/bin/strip
configure:5749: result: strip
configure:5821: checking for ranlib
configure:5837: found /usr/bin/ranlib
configure:5848: result: ranlib
configure:5950: checking command to parse /usr/bin/nm -B output from gcc object
configure:6069: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:6072: $? = 0
configure:6076: /usr/bin/nm -B conftest.o \| sed -n -e 's/^.*[ ]$[ABCDGIRSTW][ABCDGIRSTW]*$[ ][ ]*$[_A-Za-z][_A-Za-z0-9]*$$/\1 \2 \2/p' | sed '/ __gnu_lto/d' \> conftest.nm
configure:6079: $? = 0
configure:6145: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c conftstm.o >&5
configure:6148: $? = 0
configure:6186: result: ok
configure:6223: checking for sysroot
configure:6253: result: no
configure:6330: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:6333: $? = 0
configure:6496: checking for mt
configure:6526: result: no
configure:6546: checking if : is a manifest tool
configure:6552: : '-?'
configure:6560: result: no
configure:7192: checking how to run the C preprocessor
configure:7223: gcc -E conftest.c
configure:7223: $? = 0
configure:7237: gcc -E conftest.c
conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
compilation terminated.
configure:7237: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "xfce4-indicator-plugin"
| #define PACKAGE_TARNAME "xfce4-indicator-plugin"
| #define PACKAGE_VERSION "0.3.1"
| #define PACKAGE_STRING "xfce4-indicator-plugin 0.3.1"
| #define PACKAGE_BUGREPORT "http://bugzilla.xfce.org/"
| #define PACKAGE_URL ""
| #define PACKAGE "xfce4-indicator-plugin"
| #define VERSION "0.3.1"
| /* end confdefs.h. */
| #include <ac_nonexistent.h>
configure:7262: result: gcc -E
configure:7282: gcc -E conftest.c
configure:7282: $? = 0
configure:7296: gcc -E conftest.c
conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
compilation terminated.
configure:7296: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "xfce4-indicator-plugin"
| #define PACKAGE_TARNAME "xfce4-indicator-plugin"
| #define PACKAGE_VERSION "0.3.1"
| #define PACKAGE_STRING "xfce4-indicator-plugin 0.3.1"
| #define PACKAGE_BUGREPORT "http://bugzilla.xfce.org/"
| #define PACKAGE_URL ""
| #define PACKAGE "xfce4-indicator-plugin"
| #define VERSION "0.3.1"
| /* end confdefs.h. */
| #include <ac_nonexistent.h>
configure:7325: checking for ANSI C header files
configure:7345: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:7345: $? = 0
configure:7418: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
configure:7418: $? = 0
configure:7418: ./conftest
configure:7418: $? = 0
configure:7429: result: yes
configure:7442: checking for sys/types.h
configure:7442: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:7442: $? = 0
configure:7442: result: yes
configure:7442: checking for sys/stat.h
configure:7442: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:7442: $? = 0
configure:7442: result: yes
configure:7442: checking for stdlib.h
configure:7442: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:7442: $? = 0
configure:7442: result: yes
configure:7442: checking for string.h
configure:7442: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:7442: $? = 0
configure:7442: result: yes
configure:7442: checking for memory.h
configure:7442: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:7442: $? = 0
configure:7442: result: yes
configure:7442: checking for strings.h
configure:7442: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:7442: $? = 0
configure:7442: result: yes
configure:7442: checking for inttypes.h
configure:7442: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:7442: $? = 0
configure:7442: result: yes
configure:7442: checking for stdint.h
configure:7442: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:7442: $? = 0
configure:7442: result: yes
configure:7442: checking for unistd.h
configure:7442: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:7442: $? = 0
configure:7442: result: yes
configure:7456: checking for dlfcn.h
configure:7456: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:7456: $? = 0
configure:7456: result: yes
configure:7643: checking for objdir
configure:7658: result: .libs
configure:7925: checking if gcc supports -fno-rtti -fno-exceptions
configure:7943: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -fno-rtti -fno-exceptions conftest.c >&5
cc1: warning: command line option '-fno-rtti' is valid for C++/ObjC++ but not for C [enabled by default]
configure:7947: $? = 0
configure:7960: result: no
configure:8270: checking for gcc option to produce PIC
configure:8277: result: -fPIC -DPIC
configure:8285: checking if gcc PIC flag -fPIC -DPIC works
configure:8303: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -fPIC -DPIC -DPIC conftest.c >&5
configure:8307: $? = 0
configure:8320: result: yes
configure:8349: checking if gcc static flag -static works
configure:8377: result: yes
configure:8392: checking if gcc supports -c -o file.o
configure:8413: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -o out/conftest2.o conftest.c >&5
configure:8417: $? = 0
configure:8439: result: yes
configure:8447: checking if gcc supports -c -o file.o
configure:8494: result: yes
configure:8527: checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries
configure:9685: result: yes
configure:9722: checking whether -lc should be explicitly linked in
configure:9730: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:9733: $? = 0
configure:9748: gcc -shared -fPIC -DPIC conftest.o -v -Wl,-soname -Wl,conftest -o conftest 2\>\&1 \| /bin/grep -lc \>/dev/null 2\>\&1
configure:9751: $? = 0
configure:9765: result: no
configure:9930: checking dynamic linker characteristics
configure:10444: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -Wl,-rpath -Wl,/foo conftest.c >&5
configure:10444: $? = 0
configure:10670: result: GNU/Linux ld.so
configure:10777: checking how to hardcode library paths into programs
configure:10802: result: immediate
configure:11342: checking whether stripping libraries is possible
configure:11347: result: yes
configure:11382: checking if libtool supports shared libraries
configure:11384: result: yes
configure:11387: checking whether to build shared libraries
configure:11408: result: yes
configure:11411: checking whether to build static libraries
configure:11415: result: no
configure:11451: checking whether NLS is requested
configure:11460: result: yes
configure:11490: checking for intltool-update
configure:11508: found /usr/bin/intltool-update
configure:11520: result: /usr/bin/intltool-update
configure:11530: checking for intltool-merge
configure:11548: found /usr/bin/intltool-merge
configure:11560: result: /usr/bin/intltool-merge
configure:11570: checking for intltool-extract
configure:11588: found /usr/bin/intltool-extract
configure:11600: result: /usr/bin/intltool-extract
configure:11731: checking for xgettext
configure:11749: found /usr/bin/xgettext
configure:11761: result: /usr/bin/xgettext
configure:11771: checking for msgmerge
configure:11789: found /usr/bin/msgmerge
configure:11801: result: /usr/bin/msgmerge
configure:11811: checking for msgfmt
configure:11829: found /usr/bin/msgfmt
configure:11841: result: /usr/bin/msgfmt
configure:11851: checking for gmsgfmt
configure:11882: result: /usr/bin/msgfmt
configure:11902: checking for perl
configure:11920: found /usr/bin/perl
configure:11932: result: /usr/bin/perl
configure:11943: checking for perl >= 5.8.1
configure:11950: result: 5.14.1
configure:11954: checking for XML::Parser
configure:11957: result: ok
configure:11982: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
configure:11982: $? = 0
configure:12013: checking math.h usability
configure:12013: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:12013: $? = 0
configure:12013: result: yes
configure:12013: checking math.h presence
configure:12013: gcc -E conftest.c
configure:12013: $? = 0
configure:12013: result: yes
configure:12013: checking for math.h
configure:12013: result: yes
configure:12013: checking for memory.h
configure:12013: result: yes
configure:12013: checking for stdlib.h
configure:12013: result: yes
configure:12013: checking for string.h
configure:12013: result: yes
configure:12013: checking for sys/stat.h
configure:12013: result: yes
configure:12013: checking sys/time.h usability
configure:12013: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:12013: $? = 0
configure:12013: result: yes
configure:12013: checking sys/time.h presence
configure:12013: gcc -E conftest.c
configure:12013: $? = 0
configure:12013: result: yes
configure:12013: checking for sys/time.h
configure:12013: result: yes
configure:12013: checking time.h usability
configure:12013: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:12013: $? = 0
configure:12013: result: yes
configure:12013: checking time.h presence
configure:12013: gcc -E conftest.c
configure:12013: $? = 0
configure:12013: result: yes
configure:12013: checking for time.h
configure:12013: result: yes
configure:12027: checking for dummy
configure:12027: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
/tmp/ccuoh8EG.o: In function `main':
conftest.c:(.text.startup+0x7): undefined reference to `dummy'
collect2: ld returned 1 exit status
configure:12027: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "xfce4-indicator-plugin"
| #define PACKAGE_TARNAME "xfce4-indicator-plugin"
| #define PACKAGE_VERSION "0.3.1"
| #define PACKAGE_STRING "xfce4-indicator-plugin 0.3.1"
| #define PACKAGE_BUGREPORT "http://bugzilla.xfce.org/"
| #define PACKAGE_URL ""
| #define PACKAGE "xfce4-indicator-plugin"
| #define VERSION "0.3.1"
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_DLFCN_H 1
| #define LT_OBJDIR ".libs/"
| #define HAVE_MATH_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_SYS_TIME_H 1
| #define HAVE_TIME_H 1
| /* end confdefs.h. */
| /* Define dummy to an innocuous variant, in case <limits.h> declares dummy.
| For example, HP-UX 11i <limits.h> declares gettimeofday. */
| #define dummy innocuous_dummy
|
| /* System header to define __stub macros and hopefully few prototypes,
| which can conflict with char dummy (); below.
| Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
| <limits.h> exists even on freestanding compilers. */
|
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
|
| #undef dummy
|
| /* Override any GCC internal prototype to avoid an error.
| Use char because int might match the return type of a GCC
| builtin and then its argument prototype would still apply. */
| #ifdef __cplusplus
| extern "C"
| #endif
| char dummy ();
| /* The GNU C library defines this for functions which it implements
| to always fail with ENOSYS. Some functions are actually named
| something starting with __ and the normal name is an alias. */
| #if defined __stub_dummy || defined __stub___dummy
| choke me
| #endif
|
| int
| main ()
| {
| return dummy ();
| ;
| return 0;
| }
configure:12027: result: no
configure:12027: checking for perl
configure:12027: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
/tmp/cctkv6BN.o: In function `main':
conftest.c:(.text.startup+0x7): undefined reference to `perl'
collect2: ld returned 1 exit status
configure:12027: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "xfce4-indicator-plugin"
| #define PACKAGE_TARNAME "xfce4-indicator-plugin"
| #define PACKAGE_VERSION "0.3.1"
| #define PACKAGE_STRING "xfce4-indicator-plugin 0.3.1"
| #define PACKAGE_BUGREPORT "http://bugzilla.xfce.org/"
| #define PACKAGE_URL ""
| #define PACKAGE "xfce4-indicator-plugin"
| #define VERSION "0.3.1"
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_DLFCN_H 1
| #define LT_OBJDIR ".libs/"
| #define HAVE_MATH_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_SYS_TIME_H 1
| #define HAVE_TIME_H 1
| /* end confdefs.h. */
| /* Define perl to an innocuous variant, in case <limits.h> declares perl.
| For example, HP-UX 11i <limits.h> declares gettimeofday. */
| #define perl innocuous_perl
|
| /* System header to define __stub macros and hopefully few prototypes,
| which can conflict with char perl (); below.
| Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
| <limits.h> exists even on freestanding compilers. */
|
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
|
| #undef perl
|
| /* Override any GCC internal prototype to avoid an error.
| Use char because int might match the return type of a GCC
| builtin and then its argument prototype would still apply. */
| #ifdef __cplusplus
| extern "C"
| #endif
| char perl ();
| /* The GNU C library defines this for functions which it implements
| to always fail with ENOSYS. Some functions are actually named
| something starting with __ and the normal name is an alias. */
| #if defined __stub_perl || defined __stub___perl
| choke me
| #endif
|
| int
| main ()
| {
| return perl ();
| ;
| return 0;
| }
configure:12027: result: no
configure:12050: checking locale.h usability
configure:12050: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:12050: $? = 0
configure:12050: result: yes
configure:12050: checking locale.h presence
configure:12050: gcc -E conftest.c
configure:12050: $? = 0
configure:12050: result: yes
configure:12050: checking for locale.h
configure:12050: result: yes
configure:12061: checking for LC_MESSAGES
configure:12077: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
configure:12077: $? = 0
configure:12085: result: yes
configure:12102: checking libintl.h usability
configure:12102: gcc -c -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 conftest.c >&5
configure:12102: $? = 0
configure:12102: result: yes
configure:12102: checking libintl.h presence
configure:12102: gcc -E conftest.c
configure:12102: $? = 0
configure:12102: result: yes
configure:12102: checking for libintl.h
configure:12102: result: yes
configure:12110: checking for ngettext in libc
configure:12128: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
configure:12128: $? = 0
configure:12137: result: yes
configure:12141: checking for dgettext in libc
configure:12159: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
configure:12159: $? = 0
configure:12168: result: yes
configure:12175: checking for bind_textdomain_codeset
configure:12175: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
configure:12175: $? = 0
configure:12175: result: yes
configure:12451: checking for msgfmt
configure:12478: result: /usr/bin/msgfmt
configure:12489: checking for dcgettext
configure:12489: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
conftest.c:58:6: warning: conflicting types for built-in function 'dcgettext' [enabled by default]
configure:12489: $? = 0
configure:12489: result: yes
configure:12499: checking if msgfmt accepts -c
configure:12514: $MSGFMT -c -o /dev/null conftest.foo
configure:12517: $? = 0
configure:12519: result: yes
configure:12529: checking for gmsgfmt
configure:12560: result: /usr/bin/msgfmt
configure:12570: checking for xgettext
configure:12597: result: /usr/bin/xgettext
configure:12616: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
configure:12616: $? = 0
configure:12694: checking for catalogs to be installed
configure:12719: result: da de eu fr hr id it nl pl pt_BR ro ru ug uk zh_CN
configure:12752: checking for bind_textdomain_codeset
configure:12752: result: yes
configure:12758: checking for locales directory
configure:12774: result: ${datarootdir}/locale
configure:12778: checking for additional xgettext flags
configure:12786: result: --keyword=Q_ --from-code=UTF-8
configure:12790: checking for X
configure:12898: gcc -E conftest.c
configure:12898: $? = 0
configure:12929: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c -lX11 >&5
configure:12929: $? = 0
configure:12979: result: libraries , headers
configure:13078: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c -lX11 >&5
configure:13078: $? = 0
configure:13176: checking for gethostbyname
configure:13176: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
configure:13176: $? = 0
configure:13176: result: yes
configure:13273: checking for connect
configure:13273: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
configure:13273: $? = 0
configure:13273: result: yes
configure:13322: checking for remove
configure:13322: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
configure:13322: $? = 0
configure:13322: result: yes
configure:13371: checking for shmat
configure:13371: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c >&5
configure:13371: $? = 0
configure:13371: result: yes
configure:13429: checking for IceConnectionNumber in -lICE
configure:13454: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c -lICE >&5
configure:13454: $? = 0
configure:13463: result: yes
configure:13478: checking for main in -lX11
configure:13497: gcc -o conftest -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu conftest.c -lX11 -lSM -lICE >&5
configure:13497: $? = 0
configure:13506: result: yes
configure:13555: checking for pkg-config
configure:13573: found /usr/bin/pkg-config
configure:13586: result: /usr/bin/pkg-config
configure:13608: checking for pkg-config >= 0.9.0
configure:13612: result: 0.26
configure:13629: checking for gtk+-2.0 >= 2.6.0
configure:13633: result: 2.24.6
configure:13636: checking GTK_CFLAGS
configure:13639: result: -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14
configure:13642: checking GTK_LIBS
configure:13645: result: -pthread -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0
configure:13767: checking for libxfce4util-1.0 >= 4.3.99.2
configure:13771: result: 4.8.1
configure:13774: checking LIBXFCE4UTIL_CFLAGS
configure:13777: result: -I/usr/include/xfce4 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
configure:13780: checking LIBXFCE4UTIL_LIBS
configure:13783: result: -lxfce4util -lglib-2.0
configure:13905: checking for libxfce4panel-1.0 >= 4.3.99.2
configure:13909: result: 4.8.5
configure:13912: checking LIBXFCE4PANEL_CFLAGS
configure:13915: result: -pthread -I/usr/include/xfce4/libxfce4panel-1.0 -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/xfce4 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14
configure:13918: checking LIBXFCE4PANEL_LIBS
configure:13921: result: -Wl,--export-dynamic -pthread -lxfce4panel-1.0 -lgtk-x11-2.0 -lxfce4util -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0
configure:14043: checking for indicator >= 0.3.0
configure:14085: result: not found
## Cache variables. ##
ac_cv_build=x86_64-unknown-linux-gnu
ac_cv_c_compiler_gnu=yes
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=set
ac_cv_env_CFLAGS_value='-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2'
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_LDFLAGS_set=set
ac_cv_env_LDFLAGS_value=-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_XMKMF_set=
ac_cv_env_XMKMF_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_func_bind_textdomain_codeset=yes
ac_cv_func_connect=yes
ac_cv_func_dcgettext=yes
ac_cv_func_dummy=no
ac_cv_func_gethostbyname=yes
ac_cv_func_perl=no
ac_cv_func_remove=yes
ac_cv_func_shmat=yes
ac_cv_have_x='have_x=yes ac_x_includes='\'''\'' ac_x_libraries='\'''\'''
ac_cv_header_dlfcn_h=yes
ac_cv_header_inttypes_h=yes
ac_cv_header_libintl_h=yes
ac_cv_header_locale_h=yes
ac_cv_header_math_h=yes
ac_cv_header_memory_h=yes
ac_cv_header_stdc=yes
ac_cv_header_stdint_h=yes
ac_cv_header_stdlib_h=yes
ac_cv_header_string_h=yes
ac_cv_header_strings_h=yes
ac_cv_header_sys_stat_h=yes
ac_cv_header_sys_time_h=yes
ac_cv_header_sys_types_h=yes
ac_cv_header_time_h=yes
ac_cv_header_unistd_h=yes
ac_cv_host=x86_64-unknown-linux-gnu
ac_cv_lib_ICE_IceConnectionNumber=yes
ac_cv_lib_X11_main=yes
ac_cv_objext=o
ac_cv_path_EGREP='/bin/grep -E'
ac_cv_path_FGREP='/bin/grep -F'
ac_cv_path_GMSGFMT=/usr/bin/msgfmt
ac_cv_path_GREP=/bin/grep
ac_cv_path_INTLTOOL_EXTRACT=/usr/bin/intltool-extract
ac_cv_path_INTLTOOL_MERGE=/usr/bin/intltool-merge
ac_cv_path_INTLTOOL_PERL=/usr/bin/perl
ac_cv_path_INTLTOOL_UPDATE=/usr/bin/intltool-update
ac_cv_path_MSGFMT=/usr/bin/msgfmt
ac_cv_path_MSGMERGE=/usr/bin/msgmerge
ac_cv_path_PKG_CONFIG=/usr/bin/pkg-config
ac_cv_path_SED=/bin/sed
ac_cv_path_XGETTEXT=/usr/bin/xgettext
ac_cv_path_install='/bin/install -c'
ac_cv_path_mkdir=/bin/mkdir
ac_cv_prog_AWK=gawk
ac_cv_prog_CPP='gcc -E'
ac_cv_prog_ac_ct_AR=ar
ac_cv_prog_ac_ct_CC=gcc
ac_cv_prog_ac_ct_OBJDUMP=objdump
ac_cv_prog_ac_ct_RANLIB=ranlib
ac_cv_prog_ac_ct_STRIP=strip
ac_cv_prog_cc_c89=
ac_cv_prog_cc_g=yes
ac_cv_prog_make_make_set=yes
ac_cv_target=x86_64-unknown-linux-gnu
am_cv_CC_dependencies_compiler_type=gcc3
am_cv_prog_tar_ustar=gnutar
am_cv_val_LC_MESSAGES=yes
gt_cv_func_dgettext_libc=yes
gt_cv_func_dgettext_libintl=no
gt_cv_func_ngettext_libc=yes
gt_cv_have_gettext=yes
lt_cv_ar_at_file=@
lt_cv_archive_cmds_need_lc=no
lt_cv_deplibs_check_method=pass_all
lt_cv_file_magic_cmd='$MAGIC_CMD'
lt_cv_file_magic_test_file=
lt_cv_ld_reload_flag=-r
lt_cv_nm_interface='BSD nm'
lt_cv_objdir=.libs
lt_cv_path_LD=/usr/bin/ld
lt_cv_path_NM='/usr/bin/nm -B'
lt_cv_path_mainfest_tool=no
lt_cv_prog_compiler_c_o=yes
lt_cv_prog_compiler_pic='-fPIC -DPIC'
lt_cv_prog_compiler_pic_works=yes
lt_cv_prog_compiler_rtti_exceptions=no
lt_cv_prog_compiler_static_works=yes
lt_cv_prog_gnu_ld=yes
lt_cv_sharedlib_from_linklib_cmd='printf %s\n'
lt_cv_shlibpath_overrides_runpath=no
lt_cv_sys_global_symbol_pipe='sed -n -e '\''s/^.*[ ]$[ABCDGIRSTW][ABCDGIRSTW]*$[ ][ ]*$[_A-Za-z][_A-Za-z0-9]*$$/\1 \2 \2/p'\'' | sed '\''/ __gnu_lto/d'\'''
lt_cv_sys_global_symbol_to_c_name_address='sed -n -e '\''s/^: $[^ ]*$[ ]*$/ {\"\1\", (void *) 0},/p'\'' -e '\''s/^[ABCDGIRSTW]* $[^ ]*$ $[^ ]*$$/ {"\2", (void *) \&\2},/p'\'''
lt_cv_sys_global_symbol_to_c_name_address_lib_prefix='sed -n -e '\''s/^: $[^ ]*$[ ]*$/ {\"\1\", (void *) 0},/p'\'' -e '\''s/^[ABCDGIRSTW]* $[^ ]*$ $lib[^ ]*$$/ {"\2", (void *) \&\2},/p'\'' -e '\''s/^[ABCDGIRSTW]* $[^ ]*$ $[^ ]*$$/ {"lib\2", (void *) \&\2},/p'\'''
lt_cv_sys_global_symbol_to_cdecl='sed -n -e '\''s/^T .* $.*$$/extern int \1();/p'\'' -e '\''s/^[ABCDGIRSTW]* .* $.*$$/extern char \1;/p'\'''
lt_cv_sys_max_cmd_len=1572864
lt_cv_to_host_file_cmd=func_convert_file_noop
lt_cv_to_tool_file_cmd=func_convert_file_noop
xdt_cv_PKG_CONFIG_MIN_VERSION=0.9.0
xdt_cv_PKG_CONFIG_VERSION=0.26
## Output variables. ##
ACLOCAL='${SHELL} /home/jente/packages/arch/xfce4-indicator-plugin/src/xfce4-indicator-plugin-0.3.1/missing --run aclocal-1.11'
ALL_LINGUAS='da de eu fr hr id it nl pl pt_BR ro ru ug uk zh_CN '
AMDEPBACKSLASH='\'
AMDEP_FALSE='#'
AMDEP_TRUE=''
AMTAR='${SHELL} /home/jente/packages/arch/xfce4-indicator-plugin/src/xfce4-indicator-plugin-0.3.1/missing --run tar'
AR='ar'
AUTOCONF='${SHELL} /home/jente/packages/arch/xfce4-indicator-plugin/src/xfce4-indicator-plugin-0.3.1/missing --run autoconf'
AUTOHEADER='${SHELL} /home/jente/packages/arch/xfce4-indicator-plugin/src/xfce4-indicator-plugin-0.3.1/missing --run autoheader'
AUTOMAKE='${SHELL} /home/jente/packages/arch/xfce4-indicator-plugin/src/xfce4-indicator-plugin-0.3.1/missing --run automake-1.11'
AWK='gawk'
CATALOGS=' da.gmo de.gmo eu.gmo fr.gmo hr.gmo id.gmo it.gmo nl.gmo pl.gmo pt_BR.gmo ro.gmo ru.gmo ug.gmo uk.gmo zh_CN.gmo'
CATOBJEXT='.gmo'
CC='gcc'
CCDEPMODE='depmode=gcc3'
CFLAGS='-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2'
CPP='gcc -E'
CPPFLAGS=''
CYGPATH_W='echo'
DATADIRNAME='share'
DEFS=''
DEPDIR='.deps'
DLLTOOL='false'
DSYMUTIL=''
DUMPBIN=''
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP='/bin/grep -E'
EXEEXT=''
FGREP='/bin/grep -F'
GETTEXT_PACKAGE='xfce4-indicator-plugin'
GMOFILES=' da.gmo de.gmo eu.gmo fr.gmo hr.gmo id.gmo it.gmo nl.gmo pl.gmo pt_BR.gmo ro.gmo ru.gmo ug.gmo uk.gmo zh_CN.gmo'
GMSGFMT='/usr/bin/msgfmt'
GREP='/bin/grep'
GTK_CFLAGS='-pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14 '
GTK_LIBS='-pthread -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 '
GTK_REQUIRED_VERSION='2.6.0'
GTK_VERSION='2.24.6'
INDICATORDIR=''
INDICATORICONSDIR=''
INDICATOR_CFLAGS=''
INDICATOR_LIBS=''
INDICATOR_REQUIRED_VERSION=''
INDICATOR_VERSION=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
INSTOBJEXT='.mo'
INTLLIBS=''
INTLTOOL_CAVES_RULE='%.caves: %.caves.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_DESKTOP_RULE='%.desktop: %.desktop.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_DIRECTORY_RULE='%.directory: %.directory.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_EXTRACT='/usr/bin/intltool-extract'
INTLTOOL_KBD_RULE='%.kbd: %.kbd.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -x -u -m -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_KEYS_RULE='%.keys: %.keys.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -k -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_MERGE='/usr/bin/intltool-merge'
INTLTOOL_OAF_RULE='%.oaf: %.oaf.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -o -p $(top_srcdir)/po $< $@'
INTLTOOL_PERL='/usr/bin/perl'
INTLTOOL_POLICY_RULE='%.policy: %.policy.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -x -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_PONG_RULE='%.pong: %.pong.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -x -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_PROP_RULE='%.prop: %.prop.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_SCHEMAS_RULE='%.schemas: %.schemas.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -s -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_SERVER_RULE='%.server: %.server.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -o -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_SERVICE_RULE='%.service: %.service.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_SHEET_RULE='%.sheet: %.sheet.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -x -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_SOUNDLIST_RULE='%.soundlist: %.soundlist.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_THEME_RULE='%.theme: %.theme.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -d -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_UI_RULE='%.ui: %.ui.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -x -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_UPDATE='/usr/bin/intltool-update'
INTLTOOL_XAM_RULE='%.xam: %.xml.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -x -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
INTLTOOL_XML_NOMERGE_RULE='%.xml: %.xml.in $(INTLTOOL_MERGE) ; LC_ALL=C $(INTLTOOL_MERGE) -x -u /tmp $< $@'
INTLTOOL_XML_RULE='%.xml: %.xml.in $(INTLTOOL_MERGE) $(wildcard $(top_srcdir)/po/*.po) ; LC_ALL=C $(INTLTOOL_MERGE) -x -u -c $(top_builddir)/po/.intltool-merge-cache $(top_srcdir)/po $< $@'
LD='/usr/bin/ld -m elf_x86_64'
LDFLAGS='-Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu'
LIBOBJS=''
LIBS=''
LIBTOOL='$(SHELL) $(top_builddir)/libtool'
LIBX11_CFLAGS=''
LIBX11_LDFLAGS=''
LIBX11_LIBS=' -lSM -lICE -lX11'
LIBXFCE4PANEL_CFLAGS='-pthread -I/usr/include/xfce4/libxfce4panel-1.0 -I/usr/include/gtk-2.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/xfce4 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14 '
LIBXFCE4PANEL_LIBS='-Wl,--export-dynamic -pthread -lxfce4panel-1.0 -lgtk-x11-2.0 -lxfce4util -lgdk-x11-2.0 -latk-1.0 -lgio-2.0 -lpangoft2-1.0 -lpangocairo-1.0 -lgdk_pixbuf-2.0 -lcairo -lpango-1.0 -lfreetype -lfontconfig -lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lrt -lglib-2.0 '
LIBXFCE4PANEL_REQUIRED_VERSION='4.3.99.2'
LIBXFCE4PANEL_VERSION='4.8.5'
LIBXFCE4UTIL_CFLAGS='-I/usr/include/xfce4 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include '
LIBXFCE4UTIL_LIBS='-lxfce4util -lglib-2.0 '
LIBXFCE4UTIL_REQUIRED_VERSION='4.3.99.2'
LIBXFCE4UTIL_VERSION='4.8.1'
LIPO=''
LN_S='ln -s'
LTLIBOBJS=''
MAINT='#'
MAINTAINER_MODE_FALSE=''
MAINTAINER_MODE_TRUE='#'
MAKEINFO='${SHELL} /home/jente/packages/arch/xfce4-indicator-plugin/src/xfce4-indicator-plugin-0.3.1/missing --run makeinfo'
MANIFEST_TOOL=':'
MKDIR_P='/bin/mkdir -p'
MKINSTALLDIRS='./mkinstalldirs'
MSGFMT='/usr/bin/msgfmt'
MSGFMT_OPTS='-c'
MSGMERGE='/usr/bin/msgmerge'
NM='/usr/bin/nm -B'
NMEDIT=''
OBJDUMP='objdump'
OBJEXT='o'
OTOOL64=''
OTOOL=''
PACKAGE='xfce4-indicator-plugin'
PACKAGE_BUGREPORT='http://bugzilla.xfce.org/'
PACKAGE_NAME='xfce4-indicator-plugin'
PACKAGE_STRING='xfce4-indicator-plugin 0.3.1'
PACKAGE_TARNAME='xfce4-indicator-plugin'
PACKAGE_URL=''
PACKAGE_VERSION='0.3.1'
PATH_SEPARATOR=':'
PKG_CONFIG='/usr/bin/pkg-config'
PLATFORM_CFLAGS=''
PLATFORM_CPPFLAGS=''
PLATFORM_LDFLAGS=''
POFILES=' da.po de.po eu.po fr.po hr.po id.po it.po nl.po pl.po pt_BR.po ro.po ru.po ug.po uk.po zh_CN.po'
POSUB='po'
PO_IN_DATADIR_FALSE=''
PO_IN_DATADIR_TRUE=''
RANLIB='ranlib'
SED='/bin/sed'
SET_MAKE=''
SHELL='/bin/sh'
STRIP='strip'
USE_NLS='yes'
VERSION='0.3.1'
XGETTEXT='/usr/bin/xgettext'
XGETTEXT_ARGS='--keyword=Q_ --from-code=UTF-8'
XMKMF=''
X_CFLAGS=''
X_EXTRA_LIBS=''
X_LIBS=''
X_PRE_LIBS=' -lSM -lICE'
ac_ct_AR='ar'
ac_ct_CC='gcc'
ac_ct_DUMPBIN=''
am__EXEEXT_FALSE=''
am__EXEEXT_TRUE=''
am__fastdepCC_FALSE='#'
am__fastdepCC_TRUE=''
am__include='include'
am__isrc=''
am__leading_dot='.'
am__quote=''
am__tar='tar --format=ustar -chf - "$$tardir"'
am__untar='tar -xf -'
bindir='${exec_prefix}/bin'
build='x86_64-unknown-linux-gnu'
build_alias=''
build_cpu='x86_64'
build_os='linux-gnu'
build_vendor='unknown'
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host='x86_64-unknown-linux-gnu'
host_alias=''
host_cpu='x86_64'
host_os='linux-gnu'
host_vendor='unknown'
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${datarootdir}/info'
install_sh='${SHELL} /home/jente/packages/arch/xfce4-indicator-plugin/src/xfce4-indicator-plugin-0.3.1/install-sh'
libdir='${exec_prefix}/lib'
libexecdir='/usr/lib'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${datarootdir}/man'
mkdir_p='/bin/mkdir -p'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target='x86_64-unknown-linux-gnu'
target_alias=''
target_cpu='x86_64'
target_os='linux-gnu'
target_vendor='unknown'
## confdefs.h. ##
/* confdefs.h */
#define PACKAGE_NAME "xfce4-indicator-plugin"
#define PACKAGE_TARNAME "xfce4-indicator-plugin"
#define PACKAGE_VERSION "0.3.1"
#define PACKAGE_STRING "xfce4-indicator-plugin 0.3.1"
#define PACKAGE_BUGREPORT "http://bugzilla.xfce.org/"
#define PACKAGE_URL ""
#define PACKAGE "xfce4-indicator-plugin"
#define VERSION "0.3.1"
#define STDC_HEADERS 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STRINGS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_STDINT_H 1
#define HAVE_UNISTD_H 1
#define HAVE_DLFCN_H 1
#define LT_OBJDIR ".libs/"
#define HAVE_MATH_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRING_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_SYS_TIME_H 1
#define HAVE_TIME_H 1
#define GETTEXT_PACKAGE "xfce4-indicator-plugin"
#define HAVE_LOCALE_H 1
#define HAVE_LC_MESSAGES 1
#define HAVE_BIND_TEXTDOMAIN_CODESET 1
#define HAVE_GETTEXT 1
#define HAVE_DCGETTEXT 1
#define ENABLE_NLS 1
#define HAVE_LIBX11 1
configure: exit 1

BPEL develop methodology

Anybody who can provide the methodology or experience on How to build a new system by using bpel technology? Note that the new system no need to integrate other applications. So, it is a question about building a new system in SOA(Service Oriented Architecture).
Best Regards,
Sean

Hi Sean,
Please have a look at "http://www.oracle.com/technology/products/ias/bpel/index.html". This will give you a good start. After going through this URL, if you have any question feel free to ask.

XI Development methodologies

All - Is there a good doc or an URL that I can review to start looking at this ?
Thanks much !
Madhu

Here's a link.
http://media.sdn.sap.com/html/submitted_docs/Implementation_Roadmap_XI/index.htm
If the answer is satisfied, please assign points and close the thread.
regards
Shravan

The development methodology of scenarios in Discovery system

Dear Experts,
I am new to the Discovery System(DS) and I have done all the scenarios of DS in my environment.
I would like to know following things regarding the scenarios:
1. How are the designing of the scenarios done?
When I have to design the scenario, what are the basic things I should bear in mind to make a business application for a client?
( Making simple WebDynpros and Visual composers are not that difficult, but I would like to know how the designing is done at first?
2. What are the basics to decide whether we will use the guided procedure or Visual composer to make a business workflow?
I am really looking forward to hearing from you.
Thanks in advance
sudeep

Hi Sudeep,
1) typically you'd start with a definition of the scenario (business process) you'd like to cover. This could be done using any tool. Here https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5d84c39c-0d01-0010-da89-f91b698cdfcd is an example how to do it for the Procurement Process that is on the Discovery System. After having the scenario 'on paper' you can have a look at the different steps and activities and map these to technology.
2) the main differentiator: GP would be used to tie different steps of a scenario together. VC would be used to design the user facing part. VC screens can be then integrated into the larger context of a GP.
Hope that helps,
rAimund

New version of the LabHSM Toolkit for Complex Event-Driven Development is Now Available!

A new version of the unique toolkit is now available for download. As announced earlier, LabHSM makes it possible to easily create and then maintain complex event-driven applications in LabVIEW as a collection of HSM-driven active object VIs using a higher level of abstraction and agile software development methodologies. These active object VIs are created based on a universal Hierarchical State Machine ( HSM or statechart ) template. Therefore, all your code looks similar regardless of its functionality!
So, what’s new in version 1.1?
• "No hands" block diagram modifications! Version 1.1 actually creates, renames, and removes actions on the block diagram as you define, rename, and remove them in the editor! (No, it can't fill in all the details for you, but it can do some, if you think ahead, by replicating similar actions.)
• Two new screens, Events Usage and Actions Usage, (available in licensed copies only) clearly show where (in which state(s)/transition(s)) and how (is it an entry action, exit action or event handling action?) a particular event or action is used. Moreover, if after selecting an instance on the list, the Go To button is pressed, it makes the main screen jump to respective location in the HSM structure. In the case of Actions Usage screen, the respective action is also displayed on the block diagram. Thus, these screens provide two more different cross-sections of the HSM data set and two additional ways to navigate it – now along the Actions and Events dimensions too instead of just the state tree in the first version.
• Version 1.1 can duplicate events or actions, which helps when you've got several that are similar. Changes in the events and actions lists are reflected immediately on the main screen and on the block diagram (which solves the previous problem of deleting a renamed event or action when it's still in use).
• The Events and Actions List Editors are no longer modal and neither are the Events and Actions Usage screens, so you can have all the panels and the block diagram visible and move freely among them as you build your HSM (a good argument for an even larger monitor).
• When you save an HSM file, version 1.1 automatically adds the .hsm extension if you leave it out and it remembers the last directory you used.
• The Loaded VIs utility now can open and close block diagrams (if they are not protected with a password) and display only VIs with modal front panels, if desired—useful for quickly finding and closing accidentally opened (e.g., from the hierarchy window) modal VIs. Make a modal version of this utility and keep it on the Desktop for this purpose.
• A new example of a simple hierarchical state machine and two more excellent tutorials from Paul F. Sullivan (SULLutions.com) are included into the package. The tutorials are also available online. The overview article has also been extended.
As before, the LabHSM toolkit is available for UNLIMITED PERIOD trial. Please visit http://www.labhsm.com for details and download. The site also contains references which you may want to check to learn more about hierarchical state machines and active object computing.
Stanislav Rumega
NI Certified LabVIEW Developer
H View Labs
http://www.labhsm.com
[email protected]
US Toll-Free Phone/Fax: 877-570-8684

I am not really sure if Azure support this but its worth to make your configuration file to support .NET 4.0
$PShome\PowerShell_ISE.CONFIG and $PSHOME\PowerShell.exe.config will be not existing.
So you can make an entry in configuration to support .NET framework 4.0
like shown below
$config_text = @"
<?xml version="1.0"?>
<configuration>
<startup useLegacyV2RuntimeActivationPolicy="true">
<supportedRuntime version="v4.0.30319"/>
<supportedRuntime version="v2.0.50727"/>
</startup>
</configuration>
$config_text| Out-File $pshome\powershell.exe.config
$config_text| Out-File $pshome\powershell_ise.exe.config
Close PowerShell Console and open as administrator.
Try loading the modules back and let me know.
Regards Chen V [MCTS SharePoint 2010]

From Dedicated Technologies, Inc. seeking a LiveCycle Developer

Dedicated Technologies, Inc. (DTI) is a regional IT consulting firm based in Columbus, Ohio. We have a three-month plus engagement available for an Adobe Livecycle Forms Developer in the Columbus, OH area. Are any forum members available for this engagement? If so, please read on.
Qualified candidates will have the following skills and experience:
Our client has an immediate need to obtain the services of an external resource to define and implement an Electronic Forms (eForms) process that fully utilizes Adobe LiveCycle software(i.e. Designer, Reader Extension, Barcode, Form Manager). The external resource will guide, instruct and assist client personnel in the implementation of eForms by first defining a process to be used, assisting in the recommendation for infrastructure, selection of forms, templates, libraries and defining roles and responsibilities for client employees.
Requirements:
Candidates must have the following skills and experience:.
Process:
*Implementing similar or greater process for an organization with more than 200 forms
*Implementing Web Services as a front end for eSubmit
*Software Development Methodology
Adobe LiveCycle Software:
*LiveCycle Designer
*LiveCycle Form Manager
*LiveCycle Reader Extension
*LiveCycle Workflow (Not required but a plus)
Project Skills:
*Developing complex processes
*Troubleshooting and problem solving
*Interpreting results
*Excellent communication skills
*Performance tuning and stress testing
*Team leadership and instruction
Client Environment:
*Experience with any Source Configuration Management tool preferably Serena Changeman
Environment:
The client maintains hundreds of taxpayer forms. Its forms division uses Adobe PageMaker to create the forms for printing. They are also responsible for PDF, Fill-in PDF, MS Word, Excel, all of which are posted to our web site and IVR Fax Back forms. Today the fill-in forms do not contain calculations or barcodes. The client envisions the new environment to include:
*Fewer forms types that the client must maintain
*Calculations performed within the form
*Data electronically sent to the client securely
*Allow the taxpayer to save the data on his/her personal computer
*Ease of maintenance and enhancement of forms
The client uses WSAD 5.1.1, Webpshere Application Server 6.0 on AIX, Windows 2000 Professional, Java (J2EE and J2SE) and Serena Changeman for application development.
Resource Deliverables:
*Documented eForms Process
*Documented Architecture
*Documented Staffing Recommendations
*Library Elements
*Form Templates
*Two pilot forms implemented successfully using this process
*2D barcode specification schemas
*Documentation and skills transfer to all client personnel related to all processes and software utilization.
About DTI:
DTI has a unique business model which allows us to hire the best professionals in our business. We have three practices: Project Delivery, Enterprise Support, and Development services, each of which is managed by a DTI consultant. Our consultants select who joins our team, and as a result, they only choose people with whom they would want to work after the candidates have undergone a rigorous interview process. Our employees are rewarded with interesting engagements and a very supportive work environment at DTI.
DTI offers a competitive benefits package that includes a 401k plan with an employer match, health, life, dental, and vision insurance, a long-term disability plan, employee and marketing referral bonuses, a paid time off plan, parking reimbursement, discounted legal and financial services, and discounted health club memberships.
For more information about DTI, please visit our web site at:
www.dedicatedtech.com
For immediate consideration, please submit your resume to: [email protected]

I am not a developer. I am an aspiring author
researching the lives of Java developers for a
fiction project. One of the characters I am
developing IS a Java developer - NOT a MS/.Net
developer. I would greatly appreciate info about
being a Java (and/or related technology) developer.What's there to say? It sucks.
The content can be very technical but should have
some "leisure time" posts. I work around these
technologies from the marcom perspective, so I
understand a certain level of what is being
discussed. I am really inspired by the wit, spirit,
passion (and sometimes 'disgruntledness') inherent to
the world of Java developers.Eh?

Urgent Requirement : Java Web Developer with Websphere Portal : CA

The Strategic Technologies Software Engineer - Advanced
Job Title Software Engineer - Advanced
Location : CA
Description:
     This Advanced Web Developer position will be a development team that is enhancing the feature set on the corporate intranet, IBM portal based system.
     Responsible for designing, developing and unit test components in a highly iterative and agile manner.
     Responsible for Design and Development of JSR168 portlets, servlets, JSPs and deploying the same to IBM WebSphere Environment. Ability to understand Themes, Personalization, SSO and integrate portlets.
     Responsible for writing Data access components using plain Java/JDBC and as well as using technologies like Spring and Hibernate
     Ability to quickly learn and come up to speed in a new environment and follow standards.
     Aside from solid web development skills, the candidate filling this position must have experience with test driven develop (TDD) techniques and have the demeanor and communication skills required for pair programming.
     Responsible for coordinating with team members to achieve desired results and possible mentoring of Junior programmers whenever there is a need.
     Proactively identifying issues in the development and bring up the same to the attention of tech lead or management attention at the very early stages. Ability to learn from team mates and solving issues quickly with the help of more knowledgeable team mates in that technology
     Strong experience in JSR 168 compliant, portlet design and development, preferably in a IBM portal environment 2 to 4 years
     Strong experience with Java, J2EE web application design, development of servlets, jsps, JSTL and good understanding of MVC framework minimum 4 years
     Strong experience in coding unit tests with JUNIT
     Experience with Javascript , html, XML and CSS in support of web application development
     Experience with design and development of data access component in Java with SQL knowledge
     Experience using IDEs like Eclipse , RAD and application servers like IBM Websphere Application Server
     Must have good communication skills both verbally and in written form and the ability to work independently with minimal guidance and as a member of a team. Education: A computer science college degree or equivalent experience.
Must have:
     8 years Java web development skills and excellent understanding of object-oriented analysis / design / programming.
5 years:
     Deep understanding of web application design / web security
     Good understanding of Model-View controller distributed architectures.
     Experience with Websphere Studio Application Developer (Eclipse)
     Experience with Service Oriented Architecture (SOA)
     OO Analysis and Design experience.
     Experience with the scrum agile development methodology, including TDD and JUNIT.
Hands-on experience with IBM's Websphere Portal is required.
If it interest you, please send your updated resume with your contact details ASAP at [email protected].
Regards,
Ejaz
Symphony Enterprises LLC
412-250-7227 (Tel) | 412-774-9230 (Fax)
IT Staffing | Training |
VERTICALS | Banking, Finance, Insurance | Healthcare | Manufacturing | Retail & Distribution
[email protected] | www.symphonyenterprises.com
WMBE & NWBE Certified Company
A Member of Women's Business Enterprise National Council (WBENC)
and National Association of Women Business Owners (NAWBO)

I'm getting the same error on WebSphere 6.1.5. Is there any solution for this?

[Solved] Development "methodology"

Similar Messages

Maybe you are looking for