Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
LOFAR
Manage
Activity
Members
Labels
Plan
Issues
Wiki
Jira issues
Open Jira
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
RadioObservatory
LOFAR
Commits
a22967aa
Commit
a22967aa
authored
3 years ago
by
Jorrit Schaap
Browse files
Options
Downloads
Patches
Plain Diff
SW-966
: use git to clone psrdada instead of old and flaky cvs
parent
9bb34767
No related branches found
No related tags found
3 merge requests
!634
WIP: COBALT commissioning delta
,
!501
SW-966: build lofar-pulp in gitlab CI
,
!481
Draft: SW-971 SW-973 SW-975: Various fixes to build LOFAR correctly.
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
Docker/pulp-base/Dockerfile
+1
-1
1 addition, 1 deletion
Docker/pulp-base/Dockerfile
with
1 addition
and
1 deletion
Docker/pulp-base/Dockerfile
+
1
−
1
View file @
a22967aa
...
...
@@ -289,7 +289,7 @@ RUN cd ${PRESTO}/src && sudo make PRESTO=${PRESTO} prep && \
# PSRDADA
# *******************
#
RUN
cd
${
INSTALLDIR
}
/src
&&
sudo
cvs
-z3
-d
:pserver:anonymous@psrdada.cvs.sourceforge.net:/cvsroot
/psrdada
co
-P
psrdada
&&
\
RUN
cd
${
INSTALLDIR
}
/src
&&
sudo
git clone git://git.code.sf.net/p
/psrdada
/
co
de
psrdada
&&
\
cd
psrdada
&&
sudo sed
-i
's/mopsr\ //'
Makefile.am
&&
sudo
./bootstrap
&&
\
sudo
./configure
--prefix
=
${
INSTALLDIR
}
--enable-shared
--with-x
&&
sudo
make
&&
sudo
make
install
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment